> Our POC confirms that this restriction applies to SPL only. Once SPL is > running from OCRAM, it can load U-Boot proper from FAT32 without issue. > This reduces OCRAM usage, simplifies the MMC layout, and preserves FAT32 > benefits.
Hi T.F. Can you confirm or recap a bit. First I had no issue since the new update from mixed seek to three individual seek methods, TYPE, PAR#, OFFSET. But what my best guest Jan is trying to fix does not exist from the beginning. There are no need to follow old days combined splx4+uboot to A2 but simply spl on A2 and uboot in FAT. To confirm ---> For u-boot-with-spl.sfp simply dd using old method aka early like 2025.05 or before will not require the uboot to exist in FAT32 and simply all combined and flashed to A2. But using such will only stop at SPL and the U BOOT phase never completes. <--- Simply follow old boot or flash flow and blindly run make board_defconfig and no sync or update results in fails. So what my comment is just a very bad naming on latest u-boot generated file "u-boot-with-spl.sfp" ? Thanks, Brian
