On 10/15/2016 07:10 PM, Max Krummenacher wrote:
Synchronize CONFIG_SPL_PAD_TO (used at build time for u-boot-with-spl.imx) with CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR (used by SPL to read u-boot image).
Signed-off-by: Max Krummenacher max.krummenacher@toradex.com
include/configs/imx6_spl.h | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/include/configs/imx6_spl.h b/include/configs/imx6_spl.h index 76d1ca0..0b426bb 100644 --- a/include/configs/imx6_spl.h +++ b/include/configs/imx6_spl.h @@ -23,6 +23,8 @@
- which consists of a 4K header in front of us that contains the IVT, DCD
- and some padding thus 'our' max size is really 0x00908000 - 0x00918000
- or 64KB
- Padding between start of SPL(with IVT...) and U-Boot is 68KB, SPL starts
*/
- at 1KB, U-Boot at 69kB into the storage media.
#define CONFIG_SYS_THUMB_BUILD #define CONFIG_SPL_LDSCRIPT "arch/arm/cpu/armv7/omap-common/u-boot-spl.lds" @@ -38,6 +40,7 @@ /* MMC support */ #if defined(CONFIG_SPL_MMC_SUPPORT) #define CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR 138 /* offset 69KB */ +#define CONFIG_SPL_PAD_TO 0x11000 /* offset 68KB */
Does this mess up boards which can boot from both SD and other boot media (NAND, SPI NOR, PNOR...) ?
#define CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS 800 /* 400 KB */ #define CONFIG_SYS_MMCSD_FS_BOOT_PARTITION 1 #define CONFIG_SYS_MONITOR_LEN (CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS/2*1024)