PROCESSOR-SDK-J7200: SBL boot mode with OSPI

Zishuo Wang

Hi,

I have been trying to achieve SBL boot mode with OSPI using SDK 7.3, following the guide here:

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#demo_boot_app_mcu_rtos_prep_dep

Howerver I am unable to boot with the setup. There is no serial output showing at all, from MCU UART first port and second port. So I assume the SBL bootloader failed to start for some reason.

Here are some detailed steps I tried:

Build:

cd INSTALLDIR/pdk_j7200_07_03_00_29//packages/ti/build

make BOARD=j7200_evm CORE=mcu1_0 BUILD_PROFILE=release pdk_libs

#Tried both

make BOARD=j7200_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_cust_img

make BOARD=j7200_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_ospi_img

cd INSTALLDIR/mcusw/build

make can_boot_app_mcu_rtos HLOSBOOT=linux BOOTMODE=ospi BOARD=j7200_evm SOC=j7200 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=tirtos

cd INSTALLDIR/mcusw/mcuss_demos/boot_app_mcu_rtos/main_domain_apps/scripts

./makemulticore.sh j7200_evm

change the file /ti-processor-sdk-linux-j7200-evm-7.3/board-support/linux-5.4.106+gitAUTOINC+023faefa70-g023faefa70/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts

added bootargs = "console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait"

then use the /constructappimageshlos.sh j7200_evm to generate the atf_optee.appimage, tikernelimage_linux.appimage and tidtb_linux.appimage files.

Then:

the following files are transferred into the ${loadaddr} using tftp during uboot

using the command : tftp ${loadaddr} sbl_ospi_img_mcu1_0_release.tiimage

Then I used:

sf probe

sf erase 0x0 0x40000

sf write $loadaddr 0x0 $filesize to write the sbl into the flash.

as well as the tifs.bin file into location 0x80000

However, as I powered off the board, adjust the pin switches to OSPI mode, no response in the serial ports.

The current switches settings for me are:

SW3: 0100001010

SW8: 00000000

SW9: 01000000

I have also tried ：

SW8: 00000110

SW9: 01000000

according to the document below

Could you please tell me what am I missing or what am I doing wrong?

Best Regards,

Kelvin Wang

over 4 years ago

0 Karan Saxena over 4 years ago

TI__Guru* 78015 points

Hi Kelvin,

Zishuo Wang said:
sf write $loadaddr 0x0 $filesize to write the sbl into the flash.

as well as the tifs.bin file into location 0x80000

Do you flash all the relevant files here as mentioned below? (use the CUST version of SBL).

Zishuo Wang said:
the following files are transferred into the ${loadaddr} using tftp during uboot

Another thing, can you use the xSPI boot mode as mentioned here: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j7200/07_03_00_07/exports/docs/psdk_rtos/docs/user_guide/evm_setup_j7200.html#xspi-boot-mode

Regards

Karan

0 Zishuo Wang over 4 years ago in reply to Karan Saxena

Intellectual 260 points

Hi Karan,

Yes, I flashed all the files mentioned. I tried the CUST version as well.

I also tried the xSPI switch settings, but it shows the same result.

Best Regards,

Kelvin

0 Zishuo Wang over 4 years ago in reply to Zishuo Wang

Intellectual 260 points

Update on the issue, with the the pin switch settings below, some Early CAN outputs were printed to the second port of MCU UART。

SW8: 10000010
SW9: 00110000
SW3: 0111001010

However, SBL boot logs are still missing, and Linux still failed to boot.

Here are the logs printed:

0 Karan Saxena over 4 years ago in reply to Zishuo Wang

TI__Guru* 78015 points

Hi,

1. Can you send the logs you see for Linux failed boot?

2. SBL prints will not come with CUST SBL, but it is running as you are able to see the CAN application booted. IF you want more SBL logs then you will need to modify the SBL_LOG_LEVEL to 3 in the CUST_SBL_TEST_FLAGS in sbl_component.mk.

Regards

Karan

0 Zishuo Wang over 4 years ago in reply to Karan Saxena

Intellectual 260 points

1. As I mentioned in the thread, there is no response when I tried to boot after writes all the files into the OSPI. So there is absolutely no log showing in the serial terminals.

2. I have never not altered the sbl_component.mk file when switching from mmcsd boot to cust boot SBL. the SBL logs are displayed normally when booting with mmcsd. Does it switch off the log when I change the target from sbl_mmcsd_img to sbl_cust_img ?

0 Zishuo Wang over 4 years ago in reply to Zishuo Wang

Intellectual 260 points

Updates, I changed the -DSBL_LOG_LEVEL value to 3 as above. Then, I executed the make command:

make BOARD=j7200_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_cust_img

flashed the sbl_ospi_img_mcu1_0_release.tiimage file into OSPI.

But no effect was observed, it still only prints the CAN Response logs in the second terminal of MCU UART port.

What am I missing?

0 Karan Saxena over 4 years ago in reply to Zishuo Wang

TI__Guru* 78015 points

Hi,

Zishuo Wang said:
make BOARD=j7200_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_cust_img

flashed the sbl_ospi_img_mcu1_0_release.tiimage file into OSPI.

Here you are re-building the sbl_cust_img but using the sbl_ospi_img when flashing, that is why the additional logs are not coming.

Use sbl_cust_img_mcu1_0_release.tiimage.

If things still don't work, I will need to replicate on my side, but in all cases you all SBL is executing fine as you see prints from application.

Regards

Karan

0 Zishuo Wang over 4 years ago in reply to Karan Saxena

Intellectual 260 points

Hi, Karan,

Karan Saxena said:
make BOARD=j7200_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_cust_img

flashed the sbl_ospi_img_mcu1_0_release.tiimage file into OSPI.

Sorry, this was a typo. I meant that I flashed the sbl_cust_image_mcu1_0_release.tiimage into OSPI

How is the replication going?

Best Regrads,

Kelvin Wang

0 Karan Saxena over 4 years ago in reply to Zishuo Wang

TI__Guru* 78015 points

Hi Kelvin Wang,

Sorry for the delayed response here, I tried setting log level to 3 and was able to see prints from the SBL as well.

1. Change -DSBL_LOG_LEVEL value to 3, please make sure that you are making change to the relevant flag which builds for your target.

2. make sbl_cust_img_clean

3. make sbl_lib_cust_clean

4. make sbl_lib_cust

5. make sbl_cust_img

Regards

Karan

Processors

Processors forum

PROCESSOR-SDK-J7200: SBL boot mode with OSPI