• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 343 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMDS64GPEVM: Cannot do QSPI boot

O.H
Mastermind 6720 points
Part Number: LP-AM243
Other Parts Discussed in Thread: UNIFLASH,

Hi experts,

My customer is evaluating using TMDS64GPEVM and is having problems.

Q:They doesn't see the Bootloader log on the UART terminal when set to OSPI BOOT MODE, could you give me an idea of what might be causing this?

They try "Step 6: Flash a Hello World example" procedure in "Getting Started". However, the preceding "Flash SOC Initialization Binary" in "Step 3: EVM Setup" was not successful.

They followed the procedure and Flash became "SUCCESS", but even though they set SW2 and SW3 to OSPI BOOT MODE, the log of Bootloader was not displayed on the UART terminal.(Tried SW2 with "11001110" and "1101000")

Fullscreen QSPI_Boot.Log.txt Download 
C:\ti\mcu_plus_sdk_am64x_08_04_00_17\tools\boot>python uart_uniflash.py -p COM5 --cfg=sbl_prebuilt/am64x-evm/default_sbl_null.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...
Found flash writer ... sending sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.tiimage
Sent flashwriter sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.tiimage of size 290532 bytes in 28.27s.

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am64x-evm/sbl_null.release.tiimage --operation=flash --flash-offset=0x0
Sent sbl_prebuilt/am64x-evm/sbl_null.release.tiimage of size 265908 bytes in 27.1s.
[STATUS] SUCCESS !!!
　
All commands from config file are executed !!!

We thought it might be related to Silicon Revision and SDK version, but it seems that "hs_fs" is not included in the file name as a log content.(The log is attached.)

[Detail]
H/W: TMDS64GPEVM(SR1.0)
S/W: AM64x MCU+ SDK 08.04.00(latest)
CCS:v12.0.0.00009 win64

By the way, "SOC Initialization Using SD BOOT" is working well. They executed the following command, but after changing SW2,3 to OSPI boot as well, nothing appears in the UART Terminal.
>python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/am64x-evm/default_sbl_ospi.cfg

Best reards,
O.H

  • 0
    TI__Mastermind 26145 points

    Hi ,

    Can you confirm which device is being used by you ? Is it a GP device or a HS-FS device ?

    You can refer the following FAQ for the same - https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1170785/faq-mcu-plus-sdk-am243x-how-to-identify-if-the-device-is-gp-device-or-hs-device

    This will be better support, knowing more details about your setup as well as device.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Mastermind 6720 points

    Hi Aakash,

    Thank you for your reply. And I'm Sorry. The Part Number in the thread title was wrong.

    The exact target device is the TMDS64GPEVM(not LP-AM243). So I am aware that it is a GP device.

    If possible, it would be helpful if you could change the title device and move it to Processor Forum.

    Best regards,
    O.H

  • 0 in reply to O.H
    TI__Mastermind 26145 points

    Hi ,

    Can you still do this experimentation ? I want to capture the logs on your end so that I can support better on this.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Mastermind 6720 points

    Hi

    I apologize. I don't have a TMDS64GPEVM on hand at the moment.

    O.H said:
    They executed the following command, but after changing SW2,3 to OSPI boot as well, nothing appears in the UART Terminal.
    >python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/am64x-evm/default_sbl_ospi.cfg

    I am attaching the log of the customer's execution of the above command. Is that not what you intended...?

    Fullscreen QSPI_Boot_default_sbl_ospi.cfg.txt Download 
    C:\ti\mcu_plus_sdk_am64x_08_04_00_17\tools\boot>python uart_uniflash.py -p COM5 --cfg=sbl_prebuilt/am64x-evm/default_sbl_ospi_TEST.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 5 command(s) !!!

Executing command 1 of 5 ...
Found flash writer ... sending sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.tiimage
Sent flashwriter sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.tiimage of size 290532 bytes in 27.49s.

Executing command 2 of 5 ...
Command arguments : --operation=flash-phy-tuning-data
Sent flash phy tuning data in 2.28s.
[STATUS] SUCCESS !!!

Executing command 3 of 5 ...
Command arguments : --file=sbl_prebuilt/am64x-evm/sbl_ospi.release.tiimage --operation=flash --flash-offset=0x0
Sent sbl_prebuilt/am64x-evm/sbl_ospi.release.tiimage of size 311644 bytes in 32.16s.
[STATUS] SUCCESS !!!

Executing command 4 of 5 ...
Command arguments : --file=../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang.appimage --operation=flash --flash-offset=0x80000
Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0 Sent ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang.appimage of size 56600 bytes in 8.24s.
[STATUS] SUCCESS !!!

Executing command 5 of 5 ...
Command arguments : --file=../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang.appimage_xip --operation=flash-xip
Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0Sending ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0 Sent ../../../workspace_v12/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Debug/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang.appimage_xip of size 52 bytes in 2.97s.
[STATUS] SUCCESS !!!

All commands from config file are executed !!!

    Best regards,
    O.H

  • 0 in reply to O.H
    TI__Mastermind 26145 points

    Hi ,

    If you see logs as SD card but not as OSPI boot, seems like your image is perfectly okay and correctly aligned with device type. Are you sure customer has set the correct boot mode from the same link ? - https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/08_04_00_17/exports/docs/api_guide_am64x/EVM_SETUP_PAGE.html

    If yes, then maybe we need to jump in the call with the customer.

    Please request the customer to use same sbl_null.release.tiimage for both OSPI boot and SD boot.

    Best Regards,
    Aakash