TDA4VEN-Q1: SBL HLOS boot failed

xie jc

Part Number: TDA4VEN-Q1

Tool/software:

Hi TI experts,

We are testing sbl+hlos boot on TDA4EN evm board which sdk version is SDK9.2.But it is block because of app file verify failed(Bootloader_verifyMulticoreImage() return failed ).

There are some steps I do the test.

gennerated tiboot3.bin:

1)Execute "make sbl“ int the psdkra/mcu_plus_sdk_j722s_09_02_00_41/ path;

2)Copy psdkra/mcu_plus_sdk_j722s_09_02_00_41/examples/drivers/boot/sbl_sd_hlos/j722s-evm/wkup-r5fss0-0_nortos/ti-arm-clang/tiboot3.bin to sd BOOT partition.

generated app file:

1)Execute ”make vx_app_rtos_linux_mcu1_0“ in the psdkra/vision_apps/ path;

2)Execute "node elf2rprc.js ../../../../vision_apps/out/J722S/R5F/FREERTOS/release/vx_app_rtos_linux_mcu1_0.out" in the psdkra/mcu_plus_sdk_j722s_09_02_00_41/tools/boot/out2rpr/ path;

3)Execute "node multicoreImageGen.js --devID 55 --out sbl_hlos.appimage ../out2rprc/vx_app_rtos_linux_mcu1_0.rprc@0" in the psdkra/mcu_plus_sdk_j722s_09_02_00_41/tools/boot/multicoreImageGen/ path.

4)Execute "cp sbl_hlos.appimage app" and cpoy app to sd BOOT partition.

After I replace all files what I generated,The uart output as shown in the following picture.Now I have some questions:

1)Did I take any wrong steps?

2)Why SBL boot failed and how to make it boot successfully?

Regards.

over 1 year ago

0 xie jc over 1 year ago

Expert 2170 points

Hi TI experts,

I follow the below link to execute more step to generate app file.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1316301/tmds64evm-how-to-create-one-hs_fs-file-from-ca53-and-cr5-out-files?tisearch=e2e-sitesearch&keymatch=.out%25252520.appimage.hs_fs#

execute command:

1)python3 appimage_x509_cert_gen.py --bin ../multicoreImageGen/sbl_hlos.appimage --authtype 1 --key rom_degenerateKey.pem --output sbl_hlos_rom.appimage.hs_fs

2)python3 appimage_x509_cert_gen.py --bin ../multicoreImageGen/sbl_hlos.appimage --authtype 1 --key mcu_custMpk.pem --output sbl_hlos_cust.appimage.hs_fs

I replaced the app file signed with a different PEM file,now the multi image verify step is pass(Bootloader_verifyMulticoreImage() return success),but sbl still run failed because of BOOTLOADER_META_HDR_MAGIC_STR compare failed.

Does this mean that the app file I generated is still incorrect?

Regards.

0 Biao Li over 1 year ago in reply to xie jc

TI__Expert 6420 points

Hi Nikhil,

can you help look into this case?

BR,

Biao

0 Nikhil Dasan over 1 year ago in reply to Biao Li

TI__Guru* 84726 points

Hi,

From the above explanation, you are trying to load "vx_app_rtos_linux_mcu1_0" vision_Apps binary using SBL bootloader wth SD Card bootflow?

Is my understanding correct?

Are you seeing the SBL and TIFS logs here?

Regards,

Nikhil

0 xie jc over 1 year ago in reply to Nikhil Dasan

Expert 2170 points

Hi Nikhil，

Nikhil Dasan said:
From the above explanation, you are trying to load "vx_app_rtos_linux_mcu1_0" vision_Apps binary using SBL bootloader wth SD Card bootflow?

Yes.

All the logs are below：

DMSC Firmware Version 9.0.6--w2023.01-j722s (Kool Koa
DMSC Firmware revision 0x9
DMSC ABI revision 3.1

[BOOTLOADER_PROFILE] zwz Boot Media : SD Card
[BOOTLOADER_PROFILE] Boot Image Size : 0 KB
[BOOTLOADER_PROFILE] Cores present :
[BOOTLOADER PROFILE] SBL main start : 932us
[BOOTLOADER PROFILE] zwz System_init : 35466us
[BOOTLOADER PROFILE] Drivers_open : 3507us
[BOOTLOADER PROFILE] Board_driversOpen : 0us
[BOOTLOADER PROFILE] Sciclient Get Version : 9944us
[BOOTLOADER_PROFILE] SBL Total Time Taken : 49849us

Image loading done, switching to application ...
Starting linux and RTOS/Baremetal applications

Regards.

0 xie jc over 1 year ago in reply to xie jc

Expert 2170 points

Hi Nikhil，

Is any update here?

Regards.

0 xie jc 11 months ago in reply to xie jc

Expert 2170 points

Hi Nikihl,

Now sbl boot can successfully load and run MCU r5f, wkup r5f, but the current problem is how to load and run ATF, Opt, Uboot, and kernel during sbl boot.