This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi experts,
My eMMC boot0 size is 2MB only. I can only burn tiboot3.bin and tispl.bin in boot0 based on the method mentioned in 3.1.1.4.5. in Processor SDK Linux for AM62x.
Then I partitioned the UDA into 4 parts and put the u-boot.img, env, kernel in each partition of my eMMC. The format is like below :
Boot mode is configured as "eMMC Boot".
Finally, it CAN boot from eMMC and enter rootfs.
(Boot sequence I realized from 3.1.1.1.4. Boot Flow is : tiboot3.bin -> tispl.bin -> u-boot.img)
I'd like to know HOW it works jumping from tispl.bin to u-boot.img. Is it reliable to use this boot method?
Hi,
I believe what you did is built tispl.bin, u-boot.img using one build, to boot from UDA. Then you built tiboot3.bin differently to boot from boot0. Sure this setup can work if you are sure you are booting the correct image and you do not have a u-boot.img in boot0 hardware partition.
~ Judith