Part Number: PROCESSOR-SDK-AM62X
Other Parts Discussed in Thread: UNIFLASH
Tool/software:
Hi
Could you provide information on AM62X fast boot? My colleague has communicated with TI FAE and there is currently a reference for implementation
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.
Part Number: PROCESSOR-SDK-AM62X
Other Parts Discussed in Thread: UNIFLASH
Tool/software:
Hi
Could you provide information on AM62X fast boot? My colleague has communicated with TI FAE and there is currently a reference for implementation
Hello,
but does this apply to SDK9.02 version?
Please find below the link for SDK v9.2
Regards,
Prashant
Hi
I must use uart_uniflash.py to flash image? Our hardware does not have a reserved uart boot mode
I used the following command to burn the image, refer to default_sbl_emmc_linux_hs_fs.cfg, and did not see the print information when booting from emmc
Am I doing something wrong?
root@AM62x:~# time dd if=sbl_emmc_linux_stage1_am62x-sk_r5fss0-0_nortos_ti-arm-clang.tiimage of=/dev/mmcblk0boot0 bs=1k seek=0
252+1 records in
252+1 records out
258338 bytes (258 kB, 252 KiB) copied, 0.0419568 s, 6.2 MB/s
real 0m 0.04s
user 0m 0.00s
sys 0m 0.00s
root@AM62x:~# time dd if=sbl_emmc_linux_stage2_am62x-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs of=/dev/mmcblk0boot0 bs=1k seek=512
109+1 records in
109+1 records out
112255 bytes (112 kB, 110 KiB) copied, 0.0185385 s, 6.1 MB/s
real 0m 0.02s
user 0m 0.00s
sys 0m 0.00s
root@AM62x:~# time dd if=sbl_emmc_linux_stage1_am62x-sk_r5fss0-0_nortos_ti-arm-clang.tiimage of=/dev/mmcblk0boot0 bs=1k seek=0
This is GP image. If you are using HSFS device type, you would have to flash the corresponding HSFS images identified by the extensions (*.hs_fs.tiimage, *.appimage.hs_fs) in the MCU+ SDK.
BR, Prashant
Hi
I just realized the problem. It is possible to boot using the hs image in prebuilt, but the following error message will be prompted
U-Boot SPL 2023.04-ga9edd29852 (Aug 01 2024 - 11:29:44 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 13408 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024 U-Boot SPL 2023.04-ga9edd29852 (Aug 01 2024 - 11:31:17 +0800) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)') SPL initial stack usage: 1856 bytes Trying to boot from MMC2 Authentication passed Authentication passed SYSFW Firmware Version 9.2.7--v09.02.07 (Kool Koala) SYSFW Firmware revision 0x9 SYSFW ABI revision 3.1 Some tests have failed!!
By the way, I would like to ask how to calculate the offset of linux.appimage.hs_fs --operation=flash-emmc --flash-offset=0xC00000?
/dev/mmcblk0boot0 = 4MB, /dev/mmcblk0boot1 = 4MB, so the 0xC00000 offset is burned in /dev/mmcblk0p1?
That Falcon boot is not validated for SBL EMMC.
Please see the following response:
While it could have validated with certain offset adjustments but with your 4MB boot partitions, the Falcon boot with SBL EMMC will not be possible at all since the Linux Falcon appimage is itself about 20MB.
You would have to use the SBL_OSPI for Falcon boot as suggested in the above E2E.
Regards,
Prashant
does it require at least 32MB to support this method?
As I mentioned, the FALCON Linux Appimage is about ~20MB in size so you would at least need 32MB space for leveraging the FALCON boot.