Hi, André
From: u-boot-bounces@lists.denx.de [u-boot-bounces@lists.denx.de] on
behalf of André >Schaller [an.schall@googlemail.com]
Sent: Wednesday, September 04, 2013 10:09 AM To: u-boot@lists.denx.de Subject: [U-Boot] SPL binary too large for OMAP4460 OCM
Hi everybody,
I need to add functionality to the SPL code. I tried to implement in a memory-saving way, however, the SPL is about 45 kB after compilation. To get compilation working, I had to set CONFIG_SPL_MAX_SIZE to (45 * 1024). Now, the SPL as well as u-boot won't boot. After the device' (PandaBoard ES - OMAP4460) reset, nothing happens regarding it's output on terminal.
My question: is it theoretically possible to to establish a successfully booting SPL with ~45 kB in size for this device? The device' on-chip-memory is 56kB so it could fit in there. If so, what needs to be configured / tuned to get it working? Are there any other features I could omit from the binary to make it smaller?
Thanks a lot, André _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
We can use the area 0x40300000 - 0x4030bfff for downloading the SPL image. If the image exceed this - it leads to corrupting the ROM code stack and the device hangs up. See my patch [U-Boot] [RFC PATCH] armv7:omap4-common: Correct check of the SPL image size. (It's not in mainline. I'll do some corrections and send v2 soon.) For HS devices the SPL image is loaded from the address 0x40304350. So we have 0x4030bfff - 0x40304350 = 0x7CAF = 31,919 bytes for SPL. The area from 0x40300000 till 0x40304350 in HS devices is used for security data. If you have GP device you can use the whole 0x40300000 - 0x4030bfff space i.e. 49,152 bytes, just change #define CONFIG_SPL_TEXT_BASE from 0x40304350 to 0x40300000.
Best regards, Oleg http://www.globallogic.com/email_disclaimer.txt http://www.globallogic.com/email_disclaimer.txt