[Archive] TomTom v9 Firmware and Maps

[bihurkatu]

Originally Posted by dsa8310

...

Put all binaries on your $PATH (see ~/gcc-3.3.4_glibc-2.3.2/bin/ for arm-linux-gcc), make a working directory, say ~/p4, start p4d from inside it, move into ~/p4, untar ...

That envy!
I would like to manage Linux as your ...

[dsa8310]

I have just combined kernel v8 (#301792) with NC v9.430, and, yes, NO issue with the CF card at all!
The on/off button is not working, as expected, but other than that, CF or a full fledged SSD, both are supported fully.

So now, somebody, please tell me where the issue is... anybody? TT?

Oh yes, I could use the Suspend TomTom software button instead of on/off! And even the wake-up is instantaneous (the on button works).

But, it would be nice to eliminate the CF/SSD bug at kernel level, while preserving the new v9 features.

Either an expert or TT could fix it easily. I am browsing through golinux-tt301792.diff and golinux-tt547200.diff, but no luck yet.

[keessie74]

Could not start p4d. Even after making p4 and p4d executable. What am I doing wrong?

[dsa8310]

Originally Posted by keessie74

Could not start p4d. Even after making p4 and p4d executable. What am I doing wrong?

You should choose the right binary for your platform.

[dsa8310]

So far, the bad part is... the Samsung S3C2450 Mobile Processor code.
A kernel built with CONFIG_CPU_S3C2450 undefined (plus some extra trimming) is again fully compatible with an SSD or CF card.

I'm zooming in?!

[dsa8310]

S3C2410 RTC, (c) 2004 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling

This was the bug!

It appears that in the 25 (x30) mode, ironically my default mode, the RTC driver is not initialized. This upsets the SSD/CF...
In other modes, like self, 24, or with older kernels (not knowing about the S3C2450 cpu type), the RTC is started OK.

All the above is valid only with kernel v9.205, other kernels like v9.170, don't work at all.

I will try to fix the MB kernels - or I could use mode 24 (+ kernel v9.205) instead of 25...

[dsa8310]

It's not the mode, it's just the kernel...

[dsa8310]

Link to dsa-14August2012.zip:

dsa-14August2012.zip

New: CF/SSD improved support.


There is only one v9 MB kernel (v9.205) left (and it has the wake-up feature enabled).

[dsa8310]

I give up... there is only one magic v9 kernel and its name is v9.205 (#547200) ...for now

[Downunder35m]

Just started to play with the new DSA and got a weird error that I never had before:

sed: cannot rename etc//sedSKmhqj: Permission denied

Is that a problem on my PC or a "bug" in the tool?
The previous version does not show that error.
Using the 9.430 and CF+MB if that is imoprtant.

[dsa8310]

I'm afraid it's your PC... ignore it.
(it's similar to the "rm:..." error; under Windows I use an older Cygwin set of tools, supposedly working on all flavors of Windows - I wouldn't dare updating that part with the latest Cygwin which might not support, say, XP, that I no longer could check out before release, for lack of XP machines)

[Downunder35m]

Just weird that I never had that error before, but if you say I can ignore than I simply do so
Everything else seems to work just fine.

[keessie74]

I have a problem updating a XL LIVE IQ Routes Edition device with an active LIVE subscription using a TT accountname: LIVE only works when updating the Navcore with TTHOME and fails with DSA.

I both tested it with the original two-year-old map.
In DSA, I just selected the 9.430 LE Navcore with only SLF skin and no extra options activated (so no MB thus using the default 842337 kernel).

The only remarkable difference I could find is in the generated ttgo.bif. Something goes wrong in patching the ttsystem?

Next two images after update via TTHOME:

[keessie74]

Next two images after update via DSA.

Any ideas?

[Downunder35m]

Live services need a subscription, so if you update your device using Home to a working state and simply overwrite all with your DSA version, the files for the Live services should stay valid and active.