• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 351 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.

TMDSCNCD263: MCU+ SDK for AM263x self compiled SBL not working

Fabian Barth
Prodigy 55 points

Part Number: TMDSCNCD263
Other Parts Discussed in Thread: UNIFLASH

Hi,

my goal is to make changes in the QSPI SBL of the standard SBL which comes with the MCU+ SDK for AM263x (mcu_plus_sdk_am263x_08_03_01_06).

Things working:

- Flash gpio_led_blink example (C:\ti\mcu_plus_sdk_am263x_08_03_01_06\examples\drivers\gpio\gpio_led_blink\am263x-cc\r5fss0-0_nortos\ti-arm-clang) with precompiled QSPI SBL (sbl_prebuilt/am263x-cc/sbl_qspi.release.tiimage) using python uart_uniflash.py on windows

- Flash gpio_led_blink example (C:\ti\mcu_plus_sdk_am263x_08_03_01_06\examples\drivers\gpio\gpio_led_blink\am263x-cc\r5fss0-0_nortos\ti-arm-clang) with precompiled QSPI SBL from example folder (C:\ti\mcu_plus_sdk_am263x_08_03_01_06\examples\drivers\boot\sbl_qspi\am263x-cc\r5fss0-0_nortos\ti-arm-clang\sbl_qspi.release.tiimage) using python uart_uniflash.py on windows

- Clean QSPI SBL example project: gmake -s -C examples\drivers\boot\sbl_qspi\am263x-cc\r5fss0-0_nortos\ti-arm-clang all PROFILE=release clean 

- Make QSPI SBL example project: gmake -s -C examples\drivers\boot\sbl_qspi\am263x-cc\r5fss0-0_nortos\ti-arm-clang all PROFILE=release             The file "sbl_qspi.release.tiimage" is generated.

Things NOT working:

- Flash gpio_led_blink example (C:\ti\mcu_plus_sdk_am263x_08_03_01_06\examples\drivers\gpio\gpio_led_blink\am263x-cc\r5fss0-0_nortos\ti-arm-clang) with self compiled QSPI SBL (sbl_qspi.release.tiimage) from example folder with no changes applied to main.c (C:\ti\mcu_plus_sdk_am263x_08_03_01_06\examples\drivers\boot\sbl_qspi\am263x-cc\r5fss0-0_nortos\ti-arm-clang\sbl_qspi.release.tiimage) using python uart_uniflash.py on windows. Flashing the custom SBL along with the application as described is successful. When the board is switched back to QSPI boot mode using SW3 dip switches it prints out "random" numbers and prints the character C every 2-3 minutes which indicates the board is in UART boot mode and not in QSPI boot mode. I am not able to see the expected SBL debug messages. The application is not started.

Any suggestions what I am missing?

  • +1
    TI__Mastermind 26165 points

    Hi Fabian Barth,

    If I understand the question correctly, when you say "custom flash", do you mean its just rebuilt and it does not have any changes in the software ? As you mentioned that it prints "random numbers" and then prints "C" which is XMODEM prints by ROM which indicates that even in QSPI boot mode your .tiimage (x509 image verification failed) was not valid and hence ROM went into device recovery by UART mode.

    My suggestion would be to check if you are using OpenSSL Version 1.1.1 for the same. This is the OpenSSL version supported by MCU_PLUS_SDK. Steps to do that in Windows are mentioned here - AM263x MCU+ SDK: Download, Install and Setup SDK and Tools (ti.com)

    This is just a first suggestion that I believe. Can you share more information about your setup so I can support better ?

    Best Regards,
    Aakash 

  • 0 in reply to Aakash Kedia
    TI__Prodigy 55 points

    Hi Aakash,

    You have understood me exactly right. The problem was indeed that you have to use exact OpenSSL version 1.1.1 and not a newer version as described in the MCU+ SDK documentation.

    I downloaded OpenSSL version OpenSSL 1.1.1q  5 Jul 2022 which works fine.

    Best Regards,

    Fabian