u-boot always configured and compiled "as is" for at91rm9200dk
You are aware that you cannot use the same configuration for your tests?
I am doing the same, what is the difference between these command sequence to generate u-boot using 1.1.2 and 1.1.3 without doing any further setting? # make at91rm9200dk_config # make Should be the exactly the same
u-boot-1.1.3
- running in ram : DOES NOT BOOT
- stored in flash with boot.bin as pre-loader and then u-boot as bootloader : DOES NOT BOOT
- stored in flash as unique bootloader : OK BUT FAILS KERNEL UNCOMPRESSION
Your message is not helpful as it is totally unclear if you change the configuration (i. e. with or without CONFIG_SKIP_LOWLEVEL_INIT and/or CONFIG_SKIP_RELOCATE_UBOOT #defined in your cofiguration which is *essential*. Please make sure to read the documentation (README).
A quick watch to lowlevel_init.S shows that something low level is done here too ;-) However CONFIG_SKIP_LOWLEVEL_INIT and/or CONFIG_SKIP_RELOCATE_UBOOT are not set as default for at91-dk, so why version 1.1.3 (and only this version) doesn't run in ram? P.S. Manual read ;-) http://www.denx.de/twiki/bin/view/DULG/CanUBootBeConfiguredSuchThatItCanBeSt...