Likes: 
@ddabcd277
Wow! We were talking about same thingsPersonally I don't like flashing filesystem headers. It seems unreliable to me, unless you perfectly understand what those headers contain. Otherwise you have to flash entire filesystem, which will take too long time. Also you have to dump it first which will also take a while. As opposite, patching firmwares is something that I understand
I think flash is never mapped to RAM. So first commands executed by processor after reset have to be somewhere else. Also I've seen x-loader at address 0xA0000000 on nuvi 13xx. Some board config values are taken from this address. And it doesn't look like RAM address, because:Originally Posted by ddabcd277
1)RAM is usually continuous on garmins (even after MMU configuration)
2)RAM addressess are quite different on 13xx.
Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 37
Thread: Garmin Nuvi 265W dead
Hybrid View
-
1st October 2011, 05:02 PM #1Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 440
Last edited by kunix; 1st October 2011 at 05:13 PM.
-
1st October 2011, 05:23 PM #2Master
- Join Date
- Feb 2011
- Location
- Sofia
- Age
- 40
- Posts
- 727
- Rep Power
- 223
Yes, we are talking about the same thing. Just different approaches. Originally Posted by kunix
@ddabcd277
Wow! We were talking about same things Personally I don't like flashing filesystem headers. It seems unreliable to me, unless you perfectly understand what those headers contain. Otherwise you have to flash entire filesystem, which will take too long time. Also you have to dump it first which will also take a while. As opposite, patching firmwares is something that I understand And it also helps, at least for old nuvis. I abbsolutely agree with you - flashing filesystem is unreliable and dumps are too big. But I have noticed that if the so called "cure" firmwares (changing files extensions and 0:/, 1:/ (neadrenalin's method)) don't give access to the memory this is maybe the only way for fixing. (except if you don't know how to jtag a nuvi). Of course nothing to be loosed if patched firmware with disabled Open file function (kunix method) is used. Which is much clever way.
About the x-loader...Sorry I really don't know.
Edited.
-
1st October 2011, 05:42 PM #3Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 440
Here I was talking about configuring Memory Management Unit by firmware. FW remaps some peripheral registers, makes interrupt vectors, bootloader and fw addressess readonly and so on... I didn't investigate deep in this process because lack of time and knowlegde. Have to read ARM Architecture Reference Manual first Originally Posted by ddabcd277
BTW What is "MMU configuration"?
Reply With Quote
Bookmarks