Hi Albert, Thanks for the great information.
Albert ARIBAUD (U-Boot) wrote
Baaad, bad. The first time you change something in your code, your relocation offset might change and this will make U-Boot crash and burn in interesting ways.
Just define CONFIG_SYS_TEXT_BASE to some low address and let relocation happen. You can find your actual relocation address in the global data structure.
If I set CONFIG_SYS_TEXT_BASE to a low address then I can't run a memory test starting at the lowest address because that's where the U-Boot code will be.
I think the best thing would be to run a memory test on the full 2GB before relocation happens. Is that possible?
Albert ARIBAUD (U-Boot) wrote
How do you know the lowest address used by your stack during your memory test?
I know the address of the stack pointer from DEBUG message...
I erroneously thought that was the beginning of the stack. The stack expands down form that address, but how much? I don't see a global data stack size variable.
Before, we have #define CONFIG_STACKSIZE (128 * 1024) set in the header file.
Basically what is the best way to run the memory test? If I can run it before relocation then it would make things very simple.
-- View this message in context: http://u-boot.10912.n7.nabble.com/Memory-test-post-relocation-tp196088p19618... Sent from the U-Boot mailing list archive at Nabble.com.