• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 29 subscribers
  • Views 1666 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.

[FAQ] AM2434: Error with using SBL with AM243 EVMs (LP-AM243 / TMDS243EVM)

Ralph Jacobi
Guru*** 135355 points
Part Number: LP-AM243
Other Parts Discussed in Thread: UNIFLASH, TMDS243EVM, AM2434, , MCU-PLUS-SDK-AM243X

Problem Statement: When trying to load a firmware image with a SBL process such as uart_uniflash.py with default_sbl_null.cfg, the python script aborts part way through the procedure. The issue occurs even after power cycling the board and attempting to load the image immediately after.

Boards impacted: TMDS243EVM or LP-AM243 LaunchPad's with AM2434 Silicon Revision B/2.0 or later. All LaunchPad's with stickers to indicate Board Revision E3B or later will be populated with Silicon Revision B/2.0 or later.

  • +1
    TI__Guru*** 135355 points

    Root Cause: The impacted boards are populated with our latest High-Security Field-Securable (HS-FS) silicon. With that change, there is a different process for boot loading required for HS-FS devices which has been documented.

    • For LP-AM243, verifying the Silicon Revision of the device is the best method to determine if a board is impacted. HS-FS devices will have a B (or higher) for the Device Revision per the Standard Package Symbolization documented in the Device Datasheet.
      • Note: The LP-AM243 LaunchPad's that have an E3B or later sticker on the board will use Revision B/2.0 or later silicon.
    • The TMDS243EVM is a newer version of the originally released TMS243GPEVM, and this version only comes with Revision B/2.0 or later silicon.

    Solution: 

    There is a different process required to properly boot load a HS-FS device, and these steps have been documented in the following migration guide page: https://dev.ti.com/tirex/content/mcu_plus_sdk_am243x_08_05_00_24/docs/api_guide_am243x/HSFS_MIGRATION_GUIDE.html

    This migration guide walks through the differences between GP and HS-FS devices, what images are required to load into the board, and what the recommended flow is for doing so.

    The key details to resolve SBL-related issues are provided in the section Application boot using SBL (SBL OSPI, SBL NULL, SBL UART, SBL SD etc.) and states the following:

    Since most of the differences in HS-FS is related to image signing, once the SBL and application image is correctly built, rest of the flow is the same as GP for application boot. Take care that the right images are used. For example, to use SBL NULL for your application boot, flash the sbl_null.release.hs_fs.tiimage image. Same goes for other SBLs.

    Important Note: The earliest MCU-PLUS-SDK-AM243X version that supports building applications with HS-FS is Version 8.04.00. If using an earlier version of the SDK, please download at minimum Version 8.04.00 before trying to program the EVM.

    By following this procedure, boards with HS-FS silicon can be programmed through the use of all supported SBL processes.

    Best Regards,

    Ralph Jacobi