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

LP-AM243: flashing the SOC initialization binary

Jeffrey McLean
Prodigy 130 points
Part Number: LP-AM243
Other Parts Discussed in Thread: UNIFLASH

Hi, I'm having trouble flashing the SOC initialization binary to the AM243xLP. I am at this step

software-dl.ti.com/.../EVM_SETUP_PAGE.html

There are 2 parts to the uart_uniflash.py execution the fist part is successful, the second part always fails. I have power cycled the LP several times. I have power cycled the PC. The file exists at the specified location. I have all of the tools installed and every step and check before this step works correctly. I have two boards, both behave exactly the same. I looked in the forum but didn't see this reported. Can anybody help with this issue?

Thanks

C:\ti\mcu_plus_sdk_am243x_08_06_00_43\tools\boot>python uart_uniflash.py -p COM12 --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 294983 bytes in 29.28s.

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/258822 [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/258822 [00:02<145:53:29,  2.03s/bytes]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

  • 0
    TI__Guru 55965 points

    Hi Jeffery,

    Since you are using the LP(E3), the SoC on the LP is the HS-FS device. The ROM bootloader will check the signed SBL_NULL(OSPI) at flash location 0x0.

    In order to make bootloading process work properly, you will not only need the HS-FS version of the SBL_NULL or SBL_OSPI, but the signed appImage (HS-FS version)

    sbl_null.release.tiimage --> sbl_null.release.hs_fs.tiimage

    sbl_ospi.release.tiimage --> sbl_ospi.release.hs_fs.tiimage

    hello_world_am243x-evm_r5fss0-0_nortos_ti-arm-clang.appimage --> hello_world_am243x-evm_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs

    Best regards,

    Ming

  • 0
    Prodigy 130 points

    Thank you Ming. 

    I edited the .cfg file as seen below. I changed sbl_null.release.tiimage to sbl_null.release.hs_fs.tiimage but I get the same error. Is this config file correct now?

    Thanks Jeff

    # First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
--flash-writer=sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.tiimage

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
--file=sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage --operation=flash --flash-offset=0x0

  • +1 in reply to Jeffrey McLean
    TI__Guru 55965 points

    Hi Jeffery,

    I forgot one more change needed:

    sbl_uart.release.tiimage --> sbl_uart.release.hs_fs.tiimage.

    Best regards,

    Ming