On Tue, 28 Jun 2022 at 14:19, Tom Rini trini@konsulko.com wrote:
On Mon, Jun 27, 2022 at 05:28:10PM +0930, Joel Stanley wrote:
For the u-boot-with-spl.bin target to be useful for the AST2600, set the maximum SPL size which also sets the padding length.
The normal way of loading u-boot is as a FIT, so configure u-boot.img as the SPL playload.
With this the following simple steps can be used to build and boot a system:
make u-boot-with-spl.bin truncate -s 64M u-boot-with-spl.bin qemu-system-arm -nographic -M ast2600-evb \ -drive file=u-boot-with-spl.bin,if=mtd,format=raw
Signed-off-by: Joel Stanley joel@jms.id.au Reviewed-by: Chia-Wei Wang chiawei_wang@aspeedtech.com Reviewed-by: Cédric Le Goater clg@kaod.org
This doesn't quite apply correct now as CONFIG_SPL_MAX_SIZE is in Kconfig. I migrated that manually but now CI doesn't run: https://source.denx.de/u-boot/u-boot/-/jobs/457298 so I wonder if I migrated it wrong, or something else.
Thanks for trying! I've recently worked out that development is happening on the next branch, whereas my patches last week were sent against master. I've rebased this series on next and have sent them out.
To be clear, I have applied https://patchwork.ozlabs.org/project/uboot/patch/20220628042725.217333-1-joe... first.
The linker script fix is required, but I accidentally introduced a new bug in that one. It was masked because in my testing I also had the image/fit stack allocation fix in my tree, which avoids the issue with writing to the bss.
http://patchwork.ozlabs.org/project/uboot/patch/20220620070117.3443066-1-joe...
I included a linker script fix for the new bug in v2 of the series:
https://lore.kernel.org/u-boot/20220629070525.575426-1-joel@jms.id.au/
Cheers,
Joel