Thread: Enable 3790 features on your 3750/60

Originally Posted by kunix

@lolypop000
These settings are placed in a part of flash memory that is not related to NVM. This was the message.

I could not post earlier, but I thought it was another figure of speech as there is only one flash component in the GPS... One could say that even the boot loader and the firmware are in the NVM... LOL!

kunix, would you claim that the enable generated by the xml statements are stored in a different flash region than the other parameters that are in the NVM?

Yes,but where is this part of flash memory

I spend 20 houers to figure out how and where to place oem.xml but wont work,no luck.
I dont know what i doing wrong.

Originally Posted by lolypop000

Yes,but where is this part of flash memory

I spend 20 houers to figure out how and where to place oem.xml but wont work,no luck.
I dont know what i doing wrong.

Welcome to testing my friend! Now you feel my pain... I am spending a few hours every day and much more on the weekends. If I had a 13xx, I would try to test with you. Sometimes, just a little missing detail makes it not work.

@turboccc
Yes, I claim. There are a few small regions that contain OEM settings. This is true at least for nuvi 13xx/14xx, 37xx, 2xxx. They are too small to hold NVM settings.
Also I don't think NVM is in the flash at all, because in this case the writing speed would be slow and the flash would die too soon. I don't believe Garmin made such a bad decision. I think there is some kind of energy-independent memory inside ARM processor that contains NVM.

@lolypop000
What encoding did you use for OEM.xml? Make sure you save it with one-byte characters. I can't think up another reason why your perfect XML fails.

@kunix: region number, please? I scanned up to 80. I'm a bit lazy to go to 255... I'm interested in dumps, but not that much...

Originally Posted by turboccc

I'm a bit lazy to go to 255...

IMHO it works like this:
You share the info, many people try and discover next valuable information. In short time you receive results.
You hide information for yourself then you have to do it alone. You are easyly outdone by Garmin and when you reach to any conclusion, your results are outdated and nobody cares, because Garmin releases new firmwares, nuvi models etc.

0x8B, 0x8C, 0x8D, 0x8E, 0x8F
All of them are being written just after XML is parsed on 37xx.

Originally Posted by kunix

0x8B, 0x8C, 0x8D, 0x8E, 0x8F
All of them are being written just after XML is parsed on 37xx.

Thanks. Yes, I can see that my regions 139 & 140 (decimal) were modified. The other 2 (141 & 142) are still at FF for now. Remember that I have a 3750.

Here's my region 139:

Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F

00000000 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000020 00 00 30 00 31 00 00 00 00 00 00 00 00 00 00 00 ..0.1...........
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Here' my region 140:

Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F

00000000 20 00 00 00 00 00 00 00 00 01 01 01 01 01 01 01 ...............
00000010 01 01 01 01 01 01 01 01 01 01 00 00 01 01 01 00 ................
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

You can see the bunch of 01 enabling some of the features.

If someone has a 3790, I would like to see the sames bytes, please! I would guess that without using the .xml statements you would have non-zero data in those 2 regions.

This number is also for 13xx?

@turboccc
This was a reply for this post:

Originally Posted by lolypop000

This number is also for 13xx?