[Archive] TomTom v9 Firmware and Maps

[keessie74]

Do you see my Location? Then you presumably know what time it is here........

1. Post #3853 --> Nope (freeze).
2. Post #3854 --> Created a new PNDNavigator to make sure. Nope (freeze).

What could it be? It should be something.
I could try the other 9.430 cabinet (for GO devices). That cabinet doesn't contain a PNDNavigator file by default.

[dsa8310]

OK, let's stop here. Tomorrow is another day.

I can confirm that I got similar kernel panics with my CF card - until I used the K50 kernel. And all went OK since.

[keessie74]

Thanks for now. I really need to get some sleep but it really frustrating me that this doesn't work (I don't blame you of course and otherwise, you really don't matter I suppose ). Pretty nice, embedded software development.

[dsa8310]

Anyone (but go 910 owners!) willing to check out the "ttn" script from post #3824 could do it with an original ttsystem - NOT patched with dsa, taken from the NC cabinet.
It would get a device in the self mode, with parameters fmtransmitter, loquendo and gpsephemeris set as if patched with dsa (computer voices would work).

Moving the entire dsa patching to "ttn" is unfortunately not possible: go 910 devices cannot mount their (HDD) storage (hence ttn is inaccessible), and an MB/K50 kernel cannot be set (unless inside ttsystem).

[dsa8310]

Here is a different ttn.zip:

ttn.zip

It contains a simplified dsa.ko module, the v9.430 LE ttsystem (with external PNDNavigator) which could be used by go 910 devices too, and a ttn script with some logging which could be extended.

---
There is no point in continuing the issue further.
I might just release a new dsa with the simplified dsa.ko module (+ an accordingly modified file init.patch), but it really makes no difference at all...

[dsa8310]

Link to dsa-21August2012.zip:

dsa-21August2012.zip

New: slightly simplified dsa.ko module.


I'm done...

[keessie74]

I'll give up with this device. It won't work and still freezes at boot.
But, I will continue testing other devices (XL IQ Routes and another XL LIVE IQ Routes). Hopefully it's only this device which causes these problems. Who knows.....

Thanks again for all your effort!

[dsa8310]

Who knows, maybe it's a faulty card (to be formatted?)

[keessie74]

Just to ley you know:
Using dsa-21August2012 and cabinet 9.058.xl2009_live_2048.navcore-XL_LIVE.cab:
Same problem with LIVE-subscription.

[omolino]

The last DSA is not working properly:


Windows
13 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
1042821 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
3617829 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
4764255 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
5781051 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
7798246 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
11814979 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
19836684 [main] bash 436 child_copy: linked dll data write copy failed, 0x287000..0x28703C, done 0, windows pid 436, Win32 error 87
/cygdrive/C/Program Files/dsa.app/Contents/Resources/Java/Windows/dsa-cabpatch: fork: Resource temporarily unavailable

[omolino]

after install the new DSA i think my computer have problems...

now i restart the computer and DSA is working well again...

Thanks, and sorry.

[dsa8310]

I am about to release a clean, better dsa.ko module.
This update is important.

Thanks to it, I was able to pinpoint three and only three cases when the modelid parameter is read by the NC (ttn).
First reading is skin related.
One of the other two may or may not be related to sound settings.
If there is an owner of a tt device who uses the HS switch to make sound work, and willing to test out this two cases, to see whether sound would work properly without HS, please let me know.
Note that there are only two simple tests to be performed, requiring very little effort and time.

Anyway, stay tuned for the very next dsa...

[dsa8310]

Link to dsa-22August2012.zip:

dsa-22August2012.zip

New: a better dsa.ko module, important.


Though apparently undetectable, this upgrade is recommended (initialization happens entirely inside module, entries in the /proc/barcelona filesystem remain unique, and the source - dsa.c - contains already code for further testing, albeit commented out).

If interested in the testing described in post #3867 above, please let me know.

[dsa8310]

This ttn.zip:

ttn.zip

to be unzipped to the root of device would allow simple testing of sound - for devices that otherwise need HS.

Do NOT use a dsa generated ttsystem. Get an original ttsystem from the corresponding cabinet (e.g. v9.430, LE, with external PNDNavigator, easily map-patchable).

Do two tests:

1) it's already set, just check the sound out.

2) edit file ttn, make line reading:

insmod /tmp/foo.ko sound=2

into:

insmod /tmp/foo.ko sound=3

(even Windows notepad would work).

That's all, if neither 2, nor 3 work as parameters, we give up...

And, if unhappy with the preset 25 mode, change lines:

echo "25" >/proc/barcelona/modelid
export hw_modelid="25"

to any other convenient mode for testing instead of 25.

HS is quite powerful as it is now. But controlling things via dsa.ko would be nicer. I wouldn't hold my breath though...

[dsa8310]

Mode (25) should be different from the Self mode, otherwise tests are irrelevant!