I have read this thread at least three times and will read it again if needed. I apologize for the trouble but I do want to understand this. My purpose for understanding this is
to be able to mod the firmware myself.
So are you saying I need to mod boot.bin to see if the mods will work or am I totally lost and over my head on this ?
No, you can test your fw_all.bin mods yourself. For example, like here:
1) Patch fw_al.bin as you want
2) Save it by clicking File->Produce File->Create EXE file...
3) Optionally pack this fw_all.bin with gfwpack utility (for more details read [Only registered and activated users can see links. ]).
You could use the following command line:
4) Run RGN_Tool and drag fw_all.bin onto RGN_Tool's window. Make sure it prints "Section: 0800", it's uber-important.
Save the resulting GCD file and you're done.
Also there are two caveats:
1) If you don't pack fw_all.bin in step 3 then it would probably be too large (normal boot.bin is only 72 KB), and it won't be able to run as boot.bin.
2) RGN_Tool doesn't allow manually specifying the "Section: xxxx" option, instead it detects this option automatically.
And if you don't pack fw_all.bin then RGN_Tool would print "Section: BD02", which is not what you need.
Aslo I tried to make a quick and dirty nag screen patch. Can you please test it? Hopefully it would remove the nag screen. [Only registered and activated users can see links. ]
Ran the new gudate but no luck. Nag screen was blank with a x in the uper left corner. waited and the nag timed out to the audio screen. Loaded the maps bak in
and the Nag screen was back to normal and timed out to audio screen.
More than just clearing up any misunderstandings or misconceptions, i suspect that the info in post #272 is revolutionary [it is to me but i'm a fw pre-schooler at best]. Is this something you have done before, using fw_all.bin as boot.bin for safe testing and is it likely to be a universal tool or at least widely useful for other units?
'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned. Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam. [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
I was using fw_all.bin instead of boot.bin for quick and safe testing for a long time. For example, I was flashing RGN files with fw_all.bin used as boot.bin.
The same ideas works with GCD files.
And also this trick only works if the base addresses of fw_all.bin and boot.bin are equal. It's true for almost all nuvi devices (I can't remember any exception), but it's not true for some devices, like eTrex-10/20/30, GPSmap 60CSx, and many others.
And it's only useful if you are not sure that the device have a reliable pre-boot mode implemented in the bootloader. For example, it's useful for GVN53.
have followed your instructions in post 272. I am about to run my first test and wanted to make sure that after following those instructions the new gupdate.gcd I created it will run from the memory card ?