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.

AM2432: SBL error via UART

Part Number: AM2432
Other Parts Discussed in Thread: UNIFLASH

Hi team,

My customer has issue on SBL burning via UART. Below is the debug info. Could you have a look on this issue?

PS C:\ti\mcu_plus_sdk_am243x_08_05_00_24\tools\boot> python uart_uniflash.py -p COM3 --cfg=sbl_prebuilt/am243x-lp/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/am243x-lp/sbl_uart_uniflash.release.tiimage

Sent flashwriter sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.tiimage of size 294772 bytes in 27.38s. 

 

Executing command 2 of 2 ...

Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_null.release.tiimage --operation=flash --flash-offset=0x0

Sending sbl_prebuilt/am243x-lp/sbl_null.release.tiimage:   0%|                           | 0/258683 [00:00<?, ?bytes/s]send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'2'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'0'

send error: expected NAK, CRC, EOT or CAN; got b'1'

send error: expected NAK, CRC, EOT or CAN; got b'1'

Sending sbl_prebuilt/am243x-lp/sbl_null.release.tiimage:   0%|               | 2/258683 [00:01<143:34:46,  2.00s/bytes]

[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,

Power cycle EVM and run this script again !!!

PS C:\ti\mcu_plus_sdk_am243x_08_05_00_24\tools\boot>

BR

Sirui

  • Hi Sirui,

    Can you try power cycling the device just before executing the python script. Let me know if this works for you.

    Br
    Nilabh A.

  • Hello Sirui,

    Can you check if the customer is using a version of the AM243X-LP with an E3B sticker on it?

    If so, that version of the EVM includes 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.

    If they are have such a LaunchPad please help provide them the following information:

    The most important resource that we can provide is 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 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 element for your specific use case is the Application boot using SBL (SBL OSPI, SBL NULL, SBL UART, SBL SD etc.) I've copy pasted that section here for your immediate reference:

    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.

    With this revised process, you should be able to successfully use the SBL.

    Best Regards,

    Ralph Jacobi

  • Hi Ralph, Nilabbh,

    Thanks for your reply. I'll check with customer and feedback to you guys.

    BR

    Sirui