I refer to this URL link to optimize the boot time of RBL/SBL.
I use the tifs8..5+SDK8.6 to try.
1.I use the AM2634 in HS-SE mode(write some keys), so I shall complie tifs8.5 to generate new HSM(hsmRtImg.h).
2.Second, I modfiy SDK8.6 as shown in figure, and complie it (command:gmake libs-clean -s || gmake libs -s)
3.modify the flash chip ID in SBL_QSPI example, complie SBL_QSPI and sign it:
gmake -s -C ./examples/drivers/boot/sbl_qspi/am263x-cc/r5fss0-0_nortos/ti-arm-clang/ syscfg-gui
python mcu_rom_image_gen.py --image-bin sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.bin --core R5 --swrv 1 --loadaddr 0x70002000 --sign-key mcu_custMpk.pem --out-image sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.release.hs.tiimage --debug DBG_PUBLIC_ENABLE
gmake -C examples/drivers/boot/sbl_qspi/am263x-cc/r5fss0-0_nortos/ti-arm-clang/ all -s
4.complie the example of hello word(App). And burn SBL and helloword by uart.
5.power on the device again and start from the qspi, the reasult is that it successfully jumped from SBL to App.
Nextly, I want to separate SBL and HSM firmware(SBL without incorporated HSMRt firmware):
1.Use a patch file from TI E2E platform to change the SDK in order to optimize the boot time of RBL/SBL
git apply boot_5F00_time_5F00_1.diff
2.complie SDK8.6(command:gmake libs-clean -s||gmake libs -s)
3.complie SBL_QSPI and sign it:
python mcu_rom_image_gen.py --image-bin sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.bin --core R5 --swrv 1 --loadaddr 0x70002000 --sign-key mcu_custMpk.pem --out-image sbl_qspi_am263x-cc_r5fss0-0_nortos_ti-arm-clang.release.hs.tiimage --debug DBG_PUBLIC_ENABLE
gmake -C examples/drivers/boot/sbl_qspi/am263x-cc/r5fss0-0_nortos/ti-arm-clang/ all -s
11.use array2bin.c, Convert the hsmRtImg.h file to hsmRtImg.bin
12.burn them by uart (SBL+HSM+helloword),HSM is in 0xA0000
13.power on the device again and start from the qspi, the reasult is that it failurely jumped from SBL to App.
In addition, the same attempt was made in tifs8.6+sdk9.0.0.13 and the same results were obtained. (Every attempt is in HS-SE mode, not do same attempt in HS-FS mode, maybe it is a useful information)