This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

J784S4XEVM: Reliable boot sequence with J784S4 - SDK 9.2

Part Number: J784S4XEVM

Tool/software:

Dear TI experts,

I am currently studying a reliable boot sequence for J784S4 EVM with prebuilt image from SDK 9.2. The J784S4 EVM board configure and boot mode switches were configured as follow:

SW2.1 = 1 (OSPI NAND is used)

SW7[8:1] = 0000_0100 (QSPI NOR is main boot device)

SW11[8:1] = 0000_0110 (UART boot is backup boot mode)

  • QSPI NOR flash stores the following files: tiboot3.bin, tispl.bin and u-boot.img, and uEnv.txt with default QSPI NOR flash layout

          - 0x000000000000-0x000000080000 : "ospi.tiboot3"
          - 0x000000080000-0x000000280000 : "ospi.tispl"
          - 0x000000280000-0x000000680000 : "ospi.u-boot"
          - 0x000000680000-0x0000006c0000 : "ospi.env"
          - 0x0000006c0000-0x000000700000 : "ospi.env.backup"
          - 0x000000800000-0x000003fc0000 : "ospi.rootfs"
          - 0x000003ec0000-0x000003f00000 : "ospi.phypattern"

  • OSPI NAND stores tiny Linux root file system came with prebuilt SDK 9.2

After all files and rootfs were flashed in right place, the EVM was able to boot into tiny Linux OS without any problem. I started to experiment with UART boot backup mode by doing the following test:

1. Flip bits in first byte of ospi.tiboot3 partition in QSPI NOR, the EVM fallbacks to UART boot mode as expected

2. Flip bits in random byte of ospi.tiboot3 partition in QSPI NOR, the EVM fallbacks to UART boot mode as expected

3. Flip bits in first byte of ospi.tispl partition in QSPI NOR, the EVM does not fallback to UART boot mode.

I don't receive magic string 01000000011a00006a3761657000000000000000475020200008010000080100C from MCU_UART0.

It stucks at ### ERROR ### Please RESET the board ###. I powered cycle the board but the board does not fallback to backup UART boot mode. Below is boot log of tiboot3 obtained from MAIN_UART0:

U-Boot SPL 2023.04-gf9b966c674 (Aug 02 2024 - 13:10:43 +0000)
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
ti_i2c_eeprom_am6_get: Ignoring record id 255
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13488 bytes
Trying to boot from SPI
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Here are my questions:

1.  Does the tiboot3 support fallback to backup UART boot mode when something is wrong in tispl partition?

2. Does J784S4 boot ROM support multiple set of tiboot3.bin, tispi.bin and u-boot.img for reliable boot purpose?

3. Would you like to share the technical document about J784S4 boot ROM so that I can understand what are supported by the boot ROM?

Thanks

Minh

  • Hi,

    Does the tiboot3 support fallback to backup UART boot mode when something is wrong in tispl partition?

    The support is in ROM code. So the back up boot mode applies to tiboot3.bin. If that is bad then ROM detects that primary boot is not functional and switches to secondary boot mode.

    The bootloader aka tiboot3.bin only has primary boot mode support. So that has no logic to switch to UART boot mode.

    Does J784S4 boot ROM support multiple set of tiboot3.bin, tispi.bin and u-boot.img for reliable boot purpose?

    ROM's responsibility is only to  load tiboot3.bin. The other 2 do not support back up.

    3. Would you like to share the technical document about J784S4 boot ROM so that I can understand what are supported by the boot ROM?

    tiboot3.bin loading from primary/secondary is supported. Rest are all sequential & not support back up. They assume that Primary is the boot mode.

    - Keerthy

  • Thanks for your answers.