Honda Goldwing 2006-2008 Navi GPS Firmware Update Versions 4.60 & 4.70

**carlinux** · 8th May 2013, 07:49 AM

Originally Posted by Neil

Is it similar to the StreetPilot series fw do you think/know?

GoldWing navigation unit derives from Street Pilot 2610.

**Neil** · 8th May 2013, 11:05 AM

Yes, hardware is derived from 2610. If the similarity of the firmware is close then it may be possible to mod the 2610 fw to read NT maps also, which is my primary interest in these GW navis now. That possible relationship in fw is also why i offered the 2610 voice pack flash to kunix in [Only registered and activated users can see links. ] which is flashed to rgn 11 in SP 2610. I guess it's not relevent in this fw though unfortunately ....

**kunix** · 13th May 2013, 11:15 AM

carlinux
Another dumper. Please copy gfwdump.bin to CF:/gfwdump.bin, then flash the GCD, then send CF:/gfwdump.bin to me.
[Only registered and activated users can see links. ]

**carlinux** · 13th May 2013, 05:46 PM

Hello kunix,
[Only registered and activated users can see links. ] you can find the file

**kunix** · 13th May 2013, 06:06 PM

Oh, well. It dumps data. But it can't detect the sizes of regions. Can you make one more test please?
[Only registered and activated users can see links. ]

**carlinux** · 13th May 2013, 06:56 PM

This is the new test.
[Only registered and activated users can see links. ]
Do you think it's possible to dump the whole eprom via SW? How much could be large?

**kunix** · 13th May 2013, 07:29 PM

Nice, it was able to detect the sizes of almost all regions. One more test please.
[Only registered and activated users can see links. ]
I think the dumper works fine, almost fine. If the test above succeeds then I will publish the config utility for this dumper.

I can't dump the whole flash chip yet, because I haven't found a function for reading raw blocks of the chip. Instead, I've found a function for reading regions of the chip, which are defined in the firmware. And I think this is enough, as firmware usually accesses the chip via region functions, so we can access all the info that firmware is able to access.

**carlinux** · 13th May 2013, 07:40 PM

This is the #0.26.
[Only registered and activated users can see links. ]
Just a note: we are now doing tests using an USA model because this is my bike, but this isn't so usefull for bikers. When the tool will be ready we need to do another "fine tuning" of the tool using v.2.60 firmware. That I am sure it will be only a tuning.

**kunix** · 13th May 2013, 08:02 PM

Ok, the last test was finally successful. Here are the dumps of the first 256 bytes of the regions that exist (i.e. their size is not zero). You can find map data there (regions 0x03 and 0x15), audio data (0x11), logo (0x10), main unit firmware (0x0E), NV memory (0x0D), GCD file (0x0A), bootloader (0x05), and something I don't know what it is(0x22, 0x13, 0x0F).
[Only registered and activated users can see links. ]

I will publish the control utility tomorrow, as I'm too tired and drunk this evening.
Can you give me a link to v2.60 gupdate.gcd?

Now let's make complete dumps of regions 0x05, 0x0E, 0x0F, 0x22. Try using the previous gupdate.gcd and the new gfwdump.bin. Also please compress gfwdump.bin before posting, as it's going to be relatively large.
[Only registered and activated users can see links. ]