TDA4VH-Q1: SBL boot issue with Board flashOpen

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

As use the default boot image from OSPI SBL image from SDK10.1, after boot up the read flash cannot work

  

Change the device ID to 

BOARD_FLASH_ID_S28HS512T, still same issue. 
  • Can you tell if this is on the TI EVM or custom board?

  • TI standard EVM

  • Hi,

    As use the default boot image from OSPI SBL image from SDK10.1, after boot up the read flash cannot work

    Which ospi example and boot flow are you using here, and does it working with default code?

    Regards,

    Karthik

  • the default sbl_ospi_img is used, it is only for sbl. with default code.  Tanmay Patil had a session with me. he knew that. 

  • Hi,

    default sbl_ospi_img is used, it is only for sbl. with default code

    When testing with the OSPI SBL default boot image, we receive no errors. which boot flow are you using.

    Log:
    SBL Revision: 01.00.10.01 (Dec  9 2024 - 05:16:11)
    TIFS  ver: 10.1.6--v10.01.06 (Fiery Fox)
    

    Regards,

    Karthik

  • we used the SDK10.01 to build the ospi sbl default boot image, with debug profile, then start XSPI boot mode to power up. we got error. 

    sbl_ospi_img_mcu1_0_debug.tiimage 

    the EVM flash is used XSPI mode according to the sdk implementation, the read ID returns not ok, so that the handle is reset to NULL

    if we direct use prebuilt image from SDK10.1 sbl_ospi_img_mcu1_0_release.tiimage , will come followed error

    SBL Revision: 01.00.10.01 (Dec 9 2024 - 05:16:11)
    TIFS ver: 10.1.6--v10.01.06 (Fiery Fox)
    Invalid magic number in Single image header

  • Hi,

    Invalid magic number in Single image header

    For this test, are you using HS-SE devices?

    Regards,

    Karthik

  • no, it is normal GP device as it is EVM. but XSPI looks like some issue. we can have debug session to identify again.

  • Hi,

    Change the device ID to 

    BOARD_FLASH_ID_S28HS512T,

    Apart from these modifications, did you make any other changes?

    it is normal GP device as it is EVM. but XSPI looks like some issue. we can have debug session to identify again.

    It should work with TI EVM, Could you confirm that you ran this test by following the OSPI procedure below? if no please refer this.

    path:
    /home/karthikeyansaravanan/ti/uniflash_8.7.0/
    
    step 1:
      sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f  /home/ti/uniflash_8.7.0/processors/FlashWriter/j784s4_evm/uart_j784s4_evm_flash_programmer_release.tiimage -i 0
    
    step 2:
    
    sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/ti/<pdk>/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release.tiimage -d 3 -o 0
    
    
    step 3:
    sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/ti/<pdk>/packages/ti/drv/sciclient/soc/V6/tifs.bin -d 3 -o 0x80000
    
    
    sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/ti/<pdk>/packages/ti/binary/GPIO_Baremetal_LedBlink_TestApp/bin/j784s4_evm/GPIO_Baremetal_LedBlink_TestApp_mcu1_0_release.appimage -d 3 -o 0x100000
    
    step 5:
    sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f /home/ti/uniflash_8.7.0/processors/FlashWriter/j784s4_evm/nor_spi_patterns.bin -d 3 -o 0x3FC0000
    

    Regards,

    Karthik 

  • so you suggested switch to UART mode, followed commands are used

    Microsoft Windows [Version 10.0.26100.2454]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\ti\uniflash_8.7.0>dslite.bat --mode processors -c COM30 -f C:\ti\uniflash_8.7.0\processors\FlashWriter\j784s4_evm\uart_j784s4_evm_flash_programmer_release.tiimage -i 0
    Executing the following command:
    > C:\ti\uniflash_8.7.0\processors\ProcessorSDKSerialFlash.exe -c COM30 -f C:\ti\uniflash_8.7.0\processors\FlashWriter\j784s4_evm\uart_j784s4_evm_flash_programmer_release.tiimage -i 0
    
    For more details and examples, please refer to the UniFlash Quick Start guide.
    
    
    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2023 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.10.0.0
    ----------------------------------------------------------------------------
    Downloading Flash Programmer..
    
    Transferring File of size 386145 bytes
    File Transfer complete!
    
    Enabling System firmware transfer!!!
    Header Transfer complete
    Transferring System Firmware..
    Transferring File of size 158635 bytes
    File Transfer complete!
    
    C:\ti\uniflash_8.7.0>dslite.bat --mode processors -c COM30 -f W:\home\xza2abt\ti\ti-processor-sdk-rtos-j784s4-evm-10_01_00_04\pdk_j784s4_10_01_00_25\packages\ti\boot\sbl\binary\j784s4_evm\ospi\bin\sbl_ospi_img_mcu1_0_release.tiimage -d 3 -o 0
    Executing the following command:
    > C:\ti\uniflash_8.7.0\processors\ProcessorSDKSerialFlash.exe -c COM30 -f W:\home\xza2abt\ti\ti-processor-sdk-rtos-j784s4-evm-10_01_00_04\pdk_j784s4_10_01_00_25\packages\ti\boot\sbl\binary\j784s4_evm\ospi\bin\sbl_ospi_img_mcu1_0_release.tiimage -d 3 -o 0
    
    For more details and examples, please refer to the UniFlash Quick Start guide.
    
    
    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2023 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.10.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..
    
    Transferring Header Information..
    Header Transfer Complete!
    
    Flashing Image of size 353455 bytes
    Flash Programming Success!
    
    C:\ti\uniflash_8.7.0>dslite.bat --mode processors -c COM30 -f W:\home\xza2abt\ti\ti-processor-sdk-rtos-j784s4-evm-10_01_00_04\pdk_j784s4_10_01_00_25\packages\ti\drv\sciclient\soc\V6\tifs.bin -d 3 -o 0x80000
    Executing the following command:
    > C:\ti\uniflash_8.7.0\processors\ProcessorSDKSerialFlash.exe -c COM30 -f W:\home\xza2abt\ti\ti-processor-sdk-rtos-j784s4-evm-10_01_00_04\pdk_j784s4_10_01_00_25\packages\ti\drv\sciclient\soc\V6\tifs.bin -d 3 -o 0x80000
    
    For more details and examples, please refer to the UniFlash Quick Start guide.
    
    
    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2023 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.10.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..
    
    Transferring Header Information..
    Header Transfer Complete!
    
    Flashing Image of size 158666 bytes
    Flash Programming Success!
    
    C:\ti\uniflash_8.7.0>dslite.bat --mode processors -c COM30 -f W:\home\xza2abt\ti\ti-processor-sdk-rtos-j784s4-evm-10_01_00_04\pdk_j784s4_10_01_00_25\packages\ti\binary\GPIO_Baremetal_LedBlink_TestApp\bin\j784s4_evm\GPIO_Baremetal_LedBlink_TestApp_mcu1_0_release.appimage -d 3 -o 0x100000
    Executing the following command:
    > C:\ti\uniflash_8.7.0\processors\ProcessorSDKSerialFlash.exe -c COM30 -f W:\home\xza2abt\ti\ti-processor-sdk-rtos-j784s4-evm-10_01_00_04\pdk_j784s4_10_01_00_25\packages\ti\binary\GPIO_Baremetal_LedBlink_TestApp\bin\j784s4_evm\GPIO_Baremetal_LedBlink_TestApp_mcu1_0_release.appimage -d 3 -o 0x100000
    
    For more details and examples, please refer to the UniFlash Quick Start guide.
    
    
    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2023 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.10.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..
    
    Transferring Header Information..
    Header Transfer Complete!
    
    Flashing Image of size 152436 bytes
    Flash Programming Success!
    
    C:\ti\uniflash_8.7.0>dslite.bat --mode processors -c COM30 -f C:\ti\uniflash_8.7.0\processors\FlashWriter\j721e_evm\nor_spi_patterns.bin -d 3 -o 0x03FC0000
    Executing the following command:
    > C:\ti\uniflash_8.7.0\processors\ProcessorSDKSerialFlash.exe -c COM30 -f C:\ti\uniflash_8.7.0\processors\FlashWriter\j721e_evm\nor_spi_patterns.bin -d 3 -o 0x03FC0000
    
    For more details and examples, please refer to the UniFlash Quick Start guide.
    
    
    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2023 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.10.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..
    
    Transferring Header Information..
    Header Transfer Complete!
    
    Flashing Image of size 128 bytes
    Flash Programming Success!
    
    C:\ti\uniflash_8.7.0>
    

    after that come back to XSPI mode 

    Output of MCU_UART is only with 

  • Hi,

    Output of MCU_UART is only with 

    Board flashopen seems to have been successful on your evm. Instead of using GPIO_Baremetal_LedBlink_TestApp, could you please use the UART_TestApp_freertos driver example?

    Regards,

    Karthik

  • Hi,

    i just tried with debug image of GPIO_Baremetal_LedBlink_TestApp, it prints out the test passed massage.  I think the 3rd party debug flashing script has issue.  Thnaks. 

    but still some question : uniflash version must be 8.7.0? 9.0.0 is not suitable?  How to erase the OSPI , have you some general commands for usage? 

  • Hi,

    uniflash version must be 8.7.0? 9.0.0 is not suitable?  How to erase the OSPI , have you some general commands for usage? 

    I am not sure about this .

    How to erase the OSPI

    Could you please refer this https://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_board.html#erasing-the-flash-device link let us know if this helps.

    Regards,

    Karthik