I also noticed that someone on the forum already opened up his M5. Great, that means I can postpone voiding the warranty for just a few weeks more! ;-)
On 21 apr 2006, at 15:55, RaeNye wrote:
Yes. Load the binary from 0x1030 at address 0x10000; then follow the subroutine at 0x10010 that copies segments (~20 of them) from flash to IRAM & DRAM. Note that from address 0x170000 you have read-only data, mostly GUI related (menus, images, strings).
Hmmm. I got it to open, but don't know yet how to move those parts from the disasm'er.
I can send you my IDC to do that, but the Right Thing [TM] is to write a loader plugin for it...(Planned to do when I have some free time)
Can you send me the IDC as a start? :-)
The Right Thing [TM] is again to write a processor definition plugin, but there's so little to add over the original m68 code that it seems pointless to recode it w/o the original source.Hopefully DataRescue will add it soon then. So it's not possible to write plugins that are based on existing CPUs somehow? A shame... :-(
BTW,Is anyone else interested in X5 firmware disassembly? I saw a Wiki page on this, but it hasn't been updated since January.
Where's that page? Can't find it, could be interesting/useful.I added some links to the ColdFire wiki-page BTW, including a link to an introduction to m68k assembly. Might be interesting for people like me, who are only really familiar with x86 so far.
Wilmer van der Gaast. -- +-------- .''`. - -- ---+ + - -- --- ---- ----- ------+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---------------+ +------ ----- ---- --- -- - +
PGP.sig
Description: This is a digitally signed message part
