[Archive] TomTom v9 Firmware and Maps

[ahkp3]

Originally Posted by dsa8310

Link to dsa-12June2012.zip: ....
There is no more PNDNavigator.clean and the location of scan.arm has been changed to the bin directory. After a sound patching, file scan.arm is deleted anyway.

Is there still a fast way with DSA 12June2012 to switch from normal emulated sound to hardwired-to-self-sound AFTER the Navcore has been created, like the renaming of the PNDNavigator etc.?

Thanks again for all your efforts, DSA8310! You really make these old 32MB devices rock!

[dsa8310]

The short answer is no, because it makes not much sense, and a reboot would be required (a menu entry could be added to execute scan.arm against PNDNavigator, with $slfid exported maybe or stored in a file, followed by reboot).

But testing could be done quickly as described in post #3582 (now with PNDNavigator instead of PNDNavigator.clean).

---
Switching to HS is done anyway on-the-fly, at first device start-up (with scan.arm run on device during init).

[jtbili]

For old TomTom One XL 32MB RAM (ID: 4S00.000) I have created DSA Navcore, based on 9.061.xl2009_plus.CAB-navcore-ONE_XL.cab. MB option was selected, also BL was upgraded to 5.5277.
Two maps were activated: WCE and DACH-EE (890.4222), located on 4GB SDHC class 10 card. Free memory varies from 15 to 5 MB. Skin 35-XL was selected.
No problems. Thanks for your job, DSA8310.
Maybe in future the additional option could be added: optional installation of Extras.

[dsa8310]

Well, the extras could be hidden, except for the toggle button, skin chooser, quickgpsfix and a software restart.
Removing all unwanted items could be done by hand easily (delete *.cap from SdkRegistry, even the entire directory).

[jtbili]

Additional info to the One XL 1GB 32 MB RAM : I made the test with two locations of Navcore with MB option: on SDHC and in the internal memory. Map DACH-EE was active, route was from point to point then back. SDHC worked without problems, ca 10 MB memory was free.
Internal memory - NC started, tried to find satellites, found them, then suddenly was frozen and after couple of seconds TT restarted. It was endless loop.
When NC was prepared without MB for internal memory, it worked as usual, ca. 5.7...6 MB memory free.
Actually I have NC without MB in the internal memory and with MB on the SDHC.

[jtbili]

Looking through the official navore list in this thread, as file in the DSA tool ("official version of the software") I discovered, that some NCs have the same number but different letters:
Example:
9.103.ghj.CAB-navcore-XL.cab
9.103.ggi.CAB-navcore-XL.cab
9.103.gk.CAB-navcore-XL.cab

What is the difference among ghj, ggi and gk? Are they significant? Which NC is recommended?
Which version has less bugs (if any)?

[dsa8310]

Check the internal storage for errors; make sure there are 16MB of free contiguous space - eventually backup, format, restore. It's also possible that 12 MB of swap is too much - edit file skins/skins.sh and replace string 12 * 8 with 10 * 8 or even 8 * 8 .
Do install with dsa only (do not copy).

In principle, there is no difference between cabinets of same version number - at PNDNavigator level.

[ahkp3]

Quick question: on one of the devices in my testgroup the PNDNavigator.clean got renamed by itself to PNDNavigator. The users swears he didn't touch it.

Is this normal and when does this occur? Device is a TT ONE (v3).

[dsa8310]

This was normal for dsa before 6/12/12.

The sound patching of the PNDNavigator works like that:

- there is an ARM program called scan.arm (with source scan.c) which alters a PNDNavigator-like file - given as first parameter (path to it), and takes also a second numeric parameter which is the device actual self id (or even any device id).
- at dsa run I don't know the self id, but during init, this info is available, hence the decision to make the sound patching on device.

Before 6/12/12, I was generating PNDNavigator.clean, applying scan.arm to it, followed by renaming to PNDNavigator; at next init the process was not repeated because PNDNavigator.clean did no longer exist.

Now I make just PNDNavigator, apply scan.arm to it, then I erase scan.arm; at next init, scan.arm is gone, so it's not executed (and it's already deleted). This sequence is inserted into init only if HS is selected at dsa run.

Please use only the current dsa-12June2012.
I am not able to erase the previous versions from zippyshare, but they are no longer actual.

[dsa8310]

BTW, applying scan.arm again to an already patched file is harmless - it simply fails, but it is a waste of time. That is why I erase scan.arm, patching should happen only once anyway.

[ahkp3]

Originally Posted by dsa8310

This was normal for dsa before 6/12/12. ...
Before 6/12/12, I was generating PNDNavigator.clean, applying scan.arm to it, followed by renaming to PNDNavigator; at next init the process was not repeated because PNDNavigator.clean did no longer exist.

Ok, then I can confirm that this process seemed to have totally failed on my TomTom One (V2), as the PNDNavigator.clean survived several cold boots until it was finally renamed by me, thus suddenly enabling TTS without further tampering. But I will investigate this thoroughly another time and get back to you.

I received word from one of the guys in my testgroup running a custom experimental skins.sh with a 16 MB swapfile on a 32 device. Previously, my experience showed, that this config is doomed to crash upon first boot, but it might be a way to further offload mempages to the swapfile and improving performance. I also looked into using a divisor of 3 instead of 2 when calculating the size of the kickboxing file, therefore not shaking the system too much.

Do you have any indication on minimal memory usage of a 9.430LE Navcore or a similar 9.xxxLE on a 64MB TomTom? This would be a hint for me on how much memory is generally consumed when running a 9.xxx Navcore?

[dsa8310]

Without PNDNavigator TT does not run.
Let's use only dsa-12June for all tests, for now. It could be that hardwiring sound to self has no influence on LoquendoTTS; if so, I might get rid of HS... I cannot use my go910 for testing, because it has loquendo in its self mode. If there is such device which gets loquendo only without HS (and looses loquendo with HS) then the HS checkbox will be preserved.

On my go910, with BT Console, I can see almost all 16 MB of swap used.
The system is probably rebooting when overallocation happens. I will test a new size for file /tmp/boost which will hopefully eliminate it, at the expense of a bigger swap file. With the new scheme, both 32 & 64 MB devices will have same swap size, since the unused portion of the NC should be the same - or so I hope.

[fifinio]

Hi all. I just want QuickGPSfix extra, eliminate the rest What files should I delete to leave only QuickGPSfix?.
To QuickGPSfix, files are not deleted from the folders, skins, extras and SdkRegistry?.
I like the emulation only 24 GO.

Thanks and regards to all ..

[dsa8310]

Erase all files with extension *.cap from folder Sdkregistry but TTquickgpsfix.cap (keep it).

[dsa8310]

And select only 24 during dsa install.

...
But don't you fear the revenge of the sith?!