PROCESSOR-SDK-J784S4: SBL flashing over UART - change UART instance fails

Milena Milosevic

Expert 1115 points

Part Number: PROCESSOR-SDK-J784S4
Other Parts Discussed in Thread: TDA4VH,

Tool/software:

Hello TI,

We are working on the custom board based on the TDA4VH, and are using PROCESSOR-SDK-J784S4 v10.

On our HW, we do have connected UART MAIN 5, not UART MAIN 8.

We have following behavior:

When the BOARD_UART_INSTANCE is set to 8U (in pdk_j784s4_10_00_00_27/packages/ti/board/src/j784s4_evm/include/board_cfg.h )
- We can successfully use sbl - tiboot3.bin to load tifs and then app via UART on our custom board
  - logs are visible(MAIN5, MCU0)
- With this setup we do not see logs from for example this application enet_lwip_example_freertos (executed on the mcu2_1 core)
When the BOARD_UART_INSTANCE is set to 5U (in pdk_j784s4_10_00_00_27/packages/ti/board/src/j784s4_evm/include/board_cfg.h )
- We cannot successfully boot via UART (tiboot3 is transferred, no logs visible for Waiting for tifs... , and next binary transfer fails).
When we build the SBL (tiboot3.bin) with the UART instance 8, and app (enet_lwip_example_freertos ) with UART instance 5
- Flashing is OK and logs visible from SBL
- All logs are visible from app

Do you have some suggestions what might be wrong, why the SBL (tiboot3) does not load via UART when the UART instance is set to 5?

Additional info:

Command for sbl build:
- make BOARD=j784s4_evm CORE=mcu1_0 sbl_uart_img DISABLE_RECURSE_DEPS=no -sj6
Boot via UART - commands for MCU UART
- $ sx tiboot3.bin < /dev/ttyUSB<n> > /dev/ttyUSB<n>
- $ sx tifs.bin < /dev/ttyUSB<n> > /dev/ttyUSB<n>
- $ sx app < /dev/ttyUSB<n> > /dev/ttyUSB<n>

Best regards,

Milena

6 months ago

0 Neehar Sawant 6 months ago

TI__Mastermind 19370 points

Hi Milena,

Let me look into this further and get back to you in a soon.

Thanks,

Neehar

0 Neehar Sawant 6 months ago in reply to Neehar Sawant

TI__Mastermind 19370 points

Hi Milena,

Can you confirm you are booting from MCU UART but have trouble seeing logs of Main UART5?

Are you able to see the special string and pings of 'C's on the UART?

Thanks,

Neehar

0 Milena Milosevic 6 months ago in reply to Neehar Sawant

Expert 1115 points

Hello Neehar,

Please find attached logs for all three scenarios.

Scenario #1: Both: tiboot3 and enet app built with BOARD_UART_INSTANCE = 8U

/cfs-file/__key/communityserver-discussions-components-files/791/scenario1.txt

Scenario #2 tiboot3 built with BOARD_UART_INSTANCE = 8U, while enet app built with BOARD_UART_INSTANCE = 5U

/cfs-file/__key/communityserver-discussions-components-files/791/scenario2.txt

Scenario #3 Both tiboot3 and enet app built with BOARD_UART_INSTANCE = 5U

/cfs-file/__key/communityserver-discussions-components-files/791/scenario3.txt

For third scenario, we start boot via MCU UART (tiboot3.bin seems transferred), but then it is discutable if the tifs.bin is transferred, and app is definitely not transferred. Logs are not visible.

Best regards,

Milena

0 Neehar Sawant 5 months ago in reply to Milena Milosevic

TI__Mastermind 19370 points

Hi Milena,

Thanks for all the logs.

In scenario 2, are you manually changing the BOARD_UART_INSTANCE for building SBL and building the enet example? By default, both are using the BOARD_UART_INSTANCE from gBoardInitParams so they should have the same values when building

Additionally, SBL logs are shown on MCU_UART by default as seen in scenario 1 and 2.

Thanks,

Neehar

0 Milena Milosevic 5 months ago in reply to Neehar Sawant

Expert 1115 points

Hello Neehar,

Yes, in scenario 2,we are manually changing BOARD_UART_INSTANCE. Build the SBL with one value, and enet app with another.

Neehar Sawant said:
Additionally, SBL logs are shown on MCU_UART by default as seen in scenario 1 and 2.

Yes, and it is strange why the logs are not visible and SBL does not work, when we change instance to 5?

Regards,

Milena

0 Neehar Sawant 5 months ago in reply to Milena Milosevic

TI__Mastermind 19370 points

Hi Milena,

Yes it is strange. I will need to test this on my end and get back to you.

Thanks,

Neehar

0 Milena Milosevic 5 months ago in reply to Neehar Sawant

Expert 1115 points

Hi Neehar,

Any update regarding this?

Milena

0 Neehar Sawant 4 months ago in reply to Milena Milosevic

TI__Mastermind 19370 points

Hi Milena,

Is Main UART 5 the UART you want to boot with? Are you mainly using UART boot mode or SPI?

Within your custom board, do you know the UART port mapping to COM port similar to TI EVM below?

Thanks,

Neehar

0 Milena Milosevic 4 months ago in reply to Neehar Sawant

Expert 1115 points

Hi Neehar,

We are aiming same usecases as on the eval board - Meaning booting from MCU UART.

Difference is that we do not have UART8, but we have UART5.

Reagarding the UART port mapping to COM ports, we do have one to one UART to COM port mapping.

Meaning three physical UARTs, each with one COM port (WKUP, MCU, MAIN5).

Regards,

Milena

0 Milena Milosevic 4 months ago in reply to Milena Milosevic

Expert 1115 points

Hi Neehar,

We have found the root cause of the issue.(Issue was reproducible in the OSPI boot mode as well)

In the file: pdk_j784s4_10_00_00_27\packages\ti\drv\uart\soc\j784s4\UART_soc.c, uartInitCfg for the MCU build and UART5 was not defined, was 0.

#if defined (BUILD_MCU)
        0,
        0,
        0,
        0,
#endif

When we put the params for the e.g. MCU UART, we do see logs in the console - OSPI boot mode.

#if defined (BUILD_MCU)
        (uint32_t)CSL_MCU_UART0_BASE,   /* baseAddr */
        CSLR_MCU_R5FSS0_CORE0_INTR_MCU_UART0_USART_IRQ_0,   /* intNum */
        0,                              /* eventId, used only for C6x */
        UART_INPUT_CLK_96M,             /* frequency */
#endif

Best regards,

Milena

Processors

Processors forum

PROCESSOR-SDK-J784S4: SBL flashing over UART - change UART instance fails