TDA4VM: Early CAN response demo can not boot using sbl_cust_img

Liu Zhigang

Part Number: TDA4VM

Hi TI experts,

I am trying to boot the “Early CAN response” demo(can_profile_app config for tx only mode) using the sbl_cust_img OSPI boot mode，but it failed。

Follows are my step：

1、modify the CUST_SBL_TEST_FLAGS in the file (SDK Install Directory)/pdk_jacinto_07.x.x/packages/ti/boot/sbl/sbl_component.mk

2、make the sbl_cust_img

3、make the app

4、I copied the sbl_cust_img_mcu1_0_release.tiimage and download to the OSPI flash at 0x0

dslite.bat --mode processors -c COM17 -f C:\ti\DownloadFile\prebuild\sbl_cust_img_mcu1_0_release.tiimage -d 3 -o 0

5、I download the tifs.bin to 0x80000

dslite.bat --mode processors -c COM17 -f C:\ti\DownloadFile\prebuild\tifs.bin -d 3 -o 80000

6、I copied the can_profile_app_mcu1_0_release.appimage and download to the OSPI flash at 0x100000

dslite.bat --mode processors -c COM17 -f C:\ti\DownloadFile\prebuild\can_profile_app_mcu1_0_release.appimage -d 3 -o 100000

But there is no CAN message transmitted.

Then, I change the sbl image from "sbl_cust_img_mcu1_0_release.bin" to the pre-build image "sbl_ospi_img_mcu1_0_release.tiimage " , the demo works ,I can see the CAN message transmitted.

So,

1, Can you help me check why the sbl_cust_img can not work.?

2, And what is the BE stand for in can_profile_app_mcu1_0_debug_BE.appimage, when should I use this image?

over 3 years ago

0 Karan Saxena over 3 years ago

TI__Guru* 77194 points

Hi,

1. Can you please mention the exact SDK version you are using.

2. Also do mention the flags you have enabled in mcusw/mcuss_demos/boot_app_mcu_rtos/makefile?

Liu Zhigang said:
I am trying to boot the “Early CAN response” demo(can_profile_app config for tx only mode) using the sbl_cust_img OSPI boot mode，but it failed。

3. Please send the link you are referring to for the documentation, the above mentioned link is broken.

Regards

Karan

0 Liu Zhigang over 3 years ago in reply to Karan Saxena

Prodigy 60 points

1、the SDK version is 0703

2、I have done the steps as follows guide:

3、the linked file you can find in "ti-processor-sdk-rtos-j721e-evm-07_03_00_07-docs_only/mcusw/mcal_drv/docs/drv_docs/demo_can_profile_top.html#demo_can_profile_early_can_res_top"

0 Karan Saxena over 3 years ago in reply to Liu Zhigang

TI__Guru* 77194 points

Hi,

Are you running this on the EVM or a custom board? If this is the EVM, I can try replicate this on my side.

Regards

Karan

0 Liu Zhigang over 3 years ago in reply to Karan Saxena

Prodigy 60 points

Yes

0 Karan Saxena over 3 years ago in reply to Liu Zhigang

TI__Guru* 77194 points

Hi,

Karan Saxena said:
Are you running this on the EVM or a custom board? If this is the EVM, I can try replicate this on my side.

Sorry, from your response, I couldn't understand are you using a custom board or EVM, can you please clarify?

Regards

Karan

0 Liu Zhigang over 3 years ago in reply to Karan Saxena

Prodigy 60 points

EVM.

0 Karan Saxena over 3 years ago in reply to Liu Zhigang

TI__Guru* 77194 points

Hi,

I just realised that you are using the can_profile_app instead of the can_boot_app_mcu_rtos for this test. The below documentation you are referring to is for can_boot_app_mcu_rtos:

http://downloads.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_boot_app_mcu_rtos_top.html

I also see a bug in the documentation where there are instructions on how to measure CAN response, step 4 in the below link mentions the wrong name.

http://downloads.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_can_profile_top.html#demo_can_profile_early_can_res_j721e_j7200

Can you use the cust sbl with the can_boot_app_mcu_rtos_mcu1_0_release.appimage and see if that works for you?

Use the below flashing steps:

flash.txt

sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/karan/ti/uniflash_6.1.0/processors/FlashWriter/j721e_evm/uart_j721e_evm_flash_programmer_release.tiimage -i 0
sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/karan/sdk7_3/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/boot/sbl/binary/j721e_evm/cust/bin/sbl_cust_img_mcu1_0_release.tiimage -d 3 -o 0
sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/karan/sdk7_3/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/drv/sciclient/soc/V1/tifs.bin -d 3 -o 80000
sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/karan/sdk7_3/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/mcusw/binary/can_boot_app_mcu_rtos/bin/j721e_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage -d 3 -o 100000
sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/karan/sdk7_3/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/board/src/flash/nor/ospi/nor_spi_patterns.bin -d 3 -o 3FE0000

I am also attaching sample images from my setup, only change I have is that SBL_LOG_LEVEL=3 to enable more logs.

images.zip

Regards

Karan

Processors

Processors forum

TDA4VM: Early CAN response demo can not boot using sbl_cust_img