omap3: Reduce logic/overo SPL max image size
While the OMAP3 has 64KiB of SRAM, per the TRM the download area is only from 0x40200000 to 0x4020F000 and exceeding that will cause failure to boot. Further, we need to make sure that we don't run into SRAM_SCRATCH_SPACE_ADDR as once SPL is running we will write values there and would corrupt our running image. Cc: Adam Ford <aford173@gmail.com> Cc: Steve Sakoman <sakoman@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
parent
e25b369c04
commit
2489a7e9f3
@ -34,7 +34,7 @@
|
||||
#undef CONFIG_SPL_TEXT_BASE
|
||||
#undef CONFIG_SPL_MAX_SIZE
|
||||
#define CONFIG_SPL_TEXT_BASE 0x40200000
|
||||
#define CONFIG_SPL_MAX_SIZE (64 * 1024)
|
||||
#define CONFIG_SPL_MAX_SIZE (SRAM_SCRATCH_SPACE_ADDR - CONFIG_SPL_TEXT_BASE)
|
||||
|
||||
/* Display CPU and Board information */
|
||||
|
||||
|
@ -12,9 +12,9 @@
|
||||
|
||||
#include <configs/ti_omap3_common.h>
|
||||
#undef CONFIG_SPL_MAX_SIZE
|
||||
#define CONFIG_SPL_MAX_SIZE (64*1024)
|
||||
#undef CONFIG_SPL_TEXT_BASE
|
||||
#define CONFIG_SPL_TEXT_BASE 0x40200000
|
||||
#define CONFIG_SPL_MAX_SIZE (SRAM_SCRATCH_SPACE_ADDR - CONFIG_SPL_TEXT_BASE)
|
||||
|
||||
#define CONFIG_BCH
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user