J784S4XEVM: Try to boot a HLOS+RTOS appimage using SBL

Hi Bruce,

Bruce Rosier said:

Have I done something wrong ?

Please refer to the procedure below,Let us know if this is helpful.

************** Optimized Boot Flow **********

Step 1:
Download tisdk-default-image-<board_name>.wic.xz from the below links
for j784s4 : http://lcpd.itg.ti.com/builds/arago-kirkstone/prod/j784s4-evm/latest/images/

step 2:
Flash the above image to the SD card using balena etcher too. You can download the same from https://www.balena.io/etcher/


step 3:
Remove all images from the boot partition of SD card using rm command

    Open terminal in boot partition of SD card
    sudo rm -rf *

step 4:
Insert SD card into the evm

step 5:
	
Build sbl_ospi_img_hlos_mcu1_0_release.tiimage by using the following command

make BOARD=<board_name> sbl_ospi_img_hlos -sj

step 6:
Change the boot switch settings to UART bootmode.

step 7:
Flash uart flash programmer (below commands are suitable for linux PC)

    sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <path to uniflash tool>/uniflash_8.0.0/processors/FlashWriter/<board_name>/uart_<board_name>_flash_programmer_release.tiimage -i 0
    
step 8:
Flash sbl_ospi_img_hlos_mcu1_0_release.tiimage at 0x0

    sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/boot/sbl/binary/<board_name>/ospi/bin/sbl_ospi_img_hlos_mcu1_0_release.tiimage -d 3 -o 0
    
step 9:
Flash tifs.bin at 0x80000

    for j784s4 : sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/drv/sciclient/soc/V6/tifs.bin -d 3 -o 80000
    
    
step 10:
Flash combined_opt.appimage at 0x100000

sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/boot/sbl/tools/combined_appimage/bin/<board_name>/combined_opt.appimage -d 3 -o 100000

Regards,

Karthik

Hi,

I've followed your procedure. Startup in OSPI mode. No output on UART8, MCU_UART0 or WKUP_UART0.

Regards,

Bruce

Hi Bruce,

When testing with driver examples, do you receive a UART logs?

Regards,

Karthik

Hi,

I have no logs. Even sbl doesn't give me logs, it's like it's not running.

Best regards,

Bruce

Hi Bruce,

Bruce Rosier said:

I have no logs. Even sbl doesn't give me logs, it's like it's not running.

1.Is it TI EVM ? if yes, It work with basic driver example (like: GPIO_Baremetal_LedBlink_TestApp), and which sdk driver example used here?

2.Are you using a GP board, HS-FS, or HS-SE device?

Regards,

Karthik

Hi,

1. Yes, this is the TI EVM J784S4. I tried to run GPIO_Baremetal_LedBlink_TestApp:

- make -s -j sbl_mmcsd_img BOARD=j784s4_evm

- make -s -j GPIO_Baremetal_LedBlink_TestApp BOARD=j784s4_evm

- cp drv/sciclient/soc/V6/tifs.bin on SD card FAT32 partition

- cp boot/sbl/binary/j784s4_evm/mmcsd/bin/sbl_mmcsd_img_mcu1_0_release.tiimage as tiboot3.bin to SD CARD FAT32 partition

- cp binary/GPIO_Baremetal_LedBlink_TestApp/bin/j784s4_evm/GPIO_Baremetal_LedBlink_TestApp_mcu1_0_release.appimage as app on the FAT32 partition of the SD card.

I have no logs. Even sbl doesn't give me logs, it's like it's not working. No blinking LED.

2. I am using a GP board.

Regards,

Bruce

Hi Bruce,

Bruce Rosier said:

I have no logs. Even sbl doesn't give me logs, it's like it's not working. No blinking LED.

I apologize for any inconvenience, but it seems to be a hardware issue. i have looped into our hardware expert to provide inputs to your issue.

please expect some delay in response.

Regards,

Karthik

Hi Bruce,

Bruce Rosier said:

I have no logs. Even sbl doesn't give me logs, it's like it's not working. No blinking LED.

Would you please confirm that the device is in SD boot mode? 

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/10_01_00_04/exports/docs/psdk_rtos/docs/user_guide/evm_setup_j784s4.html#sd-boot-mode 

Regards,

Karthik

Hi,

I confirm that the device is in SD MODE.

I can start the EVM with the SPL boot stream specified in the Linux SDK : 3.1.1.1. General Information — Processor SDK Linux for J784s4 Documentation

Regards,

Bruce

Hi,

Sorry, I was wrong. The problem is not solved.

At first, I tried to start with OSPI with sbl_ospi_img_hlos.

But I tried to run GPIO_Baremetal_LedBlink_TestApp_mcu1_0_release.appimage. In this case, I use the SD card boot.

Regards,

Bruce

Bruce,

Can you fill in the table?

I am a hardware apps guy so take this next comment with a grain of salt -- I am a little concerned about the name of the OSPI application that is booting. The "mmcsd" would have suggested to me a different boot media but that guess on my part could easily be wrong.

Kevin

Hi Kevin,

I made a mistake in my previous post. It's “At first, I tried to start with OSPI with sbl_ospi_img_hlos”. Sorry for the mistake. Here is the completed table  :

                                          Expected Boot Media          Bootmode pins                                                                                          Success

sbl_mmcsd_img_hlos       SD CARD                               SW7 : 0000 0000   SW11: 1000 0010                                                         NO                  

sbl_ospi_img_hlos            OSPI                                      SW7 :  0110 0000   SW11: 0000 1010  SW2  : 0XXX XXXX                       NO

LedBlink                            SD CARD                              SW7 :  0000 0000  SW11:  1000 0010                                                         NO

Regards,

Bruce

I agree with the SD CARD bootmode pins.
I do not understand the OSPI bootmode pins. Here's how I understand this:

Arbitrarily assigning POST to 00, I'd expect SW7[1-8] = 0100_0000
and setting the BACKUP MODE and CONFIG to 0 (matching what you have), I'd expect SW11[1-8] = 0000_0000. I agree that SW2.1 = 0

Certainly, I could be making a mistake here, and this is why I have but so many explicit columns in the table. Can you see if the change in BOOTMODE settings effects your OSPI results?

Kevin

I tried SW7[1-8] = 0100_0000 SW11[1-8] = 0000_0000 and SW2.1 = 0 => not more successful.

I retrieved the switch configuration from the ti doc:

6. EVM Setup for J784S4 — Processor SDK RTOS J784S4

Bruce

Bruce,

Do you have anything that works? Can we start from some solid point ?

Kevin

Hi Kevin,

I've already managed to boot into the SPL boot flow with the SD card and OSPI. (3.1.1.1. General Information — Processor SDK Linux for J784s4 Documentation). No worries, it works just fine.

But I never success with HLOS+RTOS appimage using SBL : not logs at all. I've already described the method I used to generate and install the various firmware on the evaluation board.

Regards,

Bruce

Hi Bruce,

Bruce Rosier said:

But I never success with HLOS+RTOS appimage using SBL : not logs at all. I've already described the method I used to generate and install the various firmware on the evaluation board

Could you kindly confirm that you are using the same EVM for HLOS+RTOS and SPL boot flow?

Bruce Rosier said:

- cp binary/GPIO_Baremetal_LedBlink_TestApp/bin/j784s4_evm/GPIO_Baremetal_LedBlink_TestApp_mcu1_0_release.appimage as app on the FAT32 partition of the SD card.

I have no logs. Even sbl doesn't give me logs, it's like it's not working. No blinking LED.

Do you still have the same problem?

Regards,

Karthik

Hi Karthik,

I am using the same EVM for HLOS+RTOS and SBL boot flow :

And, yes, I still have the same problem of the LED not blinking with the GPIO_Baremetal_LedBlink_TestApp application.

Best regards,

Bruce

Hi Bruce,

Bruce Rosier said:

And, yes, I still have the same problem of the LED not blinking with the GPIO_Baremetal_LedBlink_TestApp application.

Could you please try this test in no boot mode?
https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/10_01_00_04/exports/docs/psdk_rtos/docs/user_guide/evm_setup_j784s4.html#no-boot-mode

Regards,

Karthik