-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: > On Wednesday 19 March 2008 17:28, Andy Green wrote: >>> To my opinion if you are willing to spend more than 4 hours writing a >>> bootloader bigger than 4k and with SD Card boot feature (vfat?) you >>> better switch to u-boot. It is more robust. It has all stuff we need >>> from a bootloader. >> What I would have done here is dump the registers for the CPU after >> U-Boot initialized them, and diff them against a dump after my >> bootloader had started Linux. > It sounds simple: just a diff of registers. > What about the memory controller, NAND controller, serial ports > or other registers memory based? In that case you will miss them.
They're all memory mapped, clock, NAND, memory controller, UART, GPIO the lot. You can dump them from U-Boot with the memory dump commands and add some code to your bootloader to dump them from there: if this made the problem you should find it. If the problem is somehow somewhere else (not sure where since not much else is inherited by Linux that isn't the kernel image in memory, or in the peripheral / CPU register settings) you at least get to rule register settings out as the problem :-) - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFH4UYSOjLpvpq7dMoRAnpAAKCLNt2QMxLmI3UoAKAEiEePhpm6UQCbBYiP 4d3oKeOEbFrk7NlULW7Hz40= =nLu0 -----END PGP SIGNATURE-----
