• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 1455 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.

Original question:

SK-AM64: v8.00 MCU+ SDK compatibility

TMDS64EVM: flash the SOC initialization binary to the EVM Failed - [ERROR] XMODEM send failed

Andrea C
Prodigy 101 points
Part Number: TMDS64EVM
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG

Hi,

I'm trying to build and flash the R5F Hello world application on that EVM.

I'm following that guide:
https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/latest/exports/docs/api_guide_am64x/EVM_SETUP_PAGE.html

I encounter the following error:

C:\ti\mcu_plus_sdk_am64x_08_03_00_18\tools\boot> python uart_uniflash.py -p COM4 --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 286189 bytes in 28.62s.

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am64x-evm/sbl_null.release.tiimage --operation=flash --flash-offset=0x0
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   1%|▌                                                                        | 2058/264685 [00:02<12:05, 361.80bytes/s]send error: expected ACK; got b'\x18' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   1%|▊                                                                       | 3087/264685 [00:03<03:25, 1272.86bytes/s]send error: expected ACK; got b'\x18' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   2%|█                                                                       | 4116/264685 [00:03<03:24, 1272.86bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   2%|█▍                                                                      | 5145/264685 [00:03<03:23, 1272.86bytes/s]send error: expected ACK; got b'2' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   2%|█▋                                                                      | 6174/264685 [00:03<01:25, 3021.16bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   3%|█▉                                                                      | 7203/264685 [00:03<01:25, 3021.16bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   3%|██▏                                                                     | 8232/264685 [00:03<01:01, 4150.79bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   3%|██▌                                                                     | 9261/264685 [00:03<01:01, 4150.79bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   4%|██▊                                                                    | 10290/264685 [00:03<00:47, 5327.56bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   4%|███                                                                    | 11319/264685 [00:03<00:47, 5327.56bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   5%|███▎                                                                   | 12348/264685 [00:03<00:38, 6484.41bytes/s]send error: expected ACK; got b'0' for block 2
send error: NAK received 11 times, aborting.
Sending sbl_prebuilt/am64x-evm/sbl_null.release.tiimage:   5%|███▎                                                                   | 12350/264685 [00:03<00:38, 6484.41bytes/s]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

I try to power cycle the board and restart the serial connection but the problem remains.

Setup Details:

  • OS: win 10
  • CCS 12.1.0.00007
  • Python 3.11.0
  • MCU+ SDK: 8.3.0.18
  • SysConfig 1.14.0
  • XDCtools 3.62.1.16_core
  • TI Clang v2.1.2.LTS
  • GNU v7.2.1
  • PRU TI v2.3.3

Thanks

  • 0
    TI__Guru 50587 points

    Hello ,

    Can you please confirm you are using HS_FS or GPEVM version Hw's?

    If you want to flash R5F application on Hw then you need to use default sbl cfg file and based on above log I understand you are using sbl_null_image and you are doing SOC initializations.

    Regards,

    S.Anil.

  • 0
    Prodigy 101 points

    Hi Anil,

    I confirm I’m using the HS-FS eval bord, the latest revision available on to website that superseed the gpevm.

    Can you better explain which bootloader and which procedure I have to use? I think that can be useful for other users too since now the to website recommend to buy this eval.

    Thanks and Regards

    Andrea

  • +1 in reply to Andrea C
    TI__Guru 50587 points

    Hello ,

    You need to update default_sbl_ospi and default_sbl_null cfg files in your workspace for HS_FS Hw version and use 8.4 SDK version for HS_FS HW from below link .

    https://www.ti.com/tool/PROCESSOR-SDK-AM64X

    Please check below path and update default_sbl_ospi and default_sbl_null cfg files.

    Path : C:\ti\mcu_plus_sdk_am64x_08_04_00_17\tools\boot\sbl_prebuilt\am64x-sk

    default_sbl_null cfg:  This is a recommended one time step that needs to be done before you can load and run programs via CCS

    Pre conditions : 

    #First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files

    --flash-writer=sbl_prebuilt/am64x-sk/sbl_uart_uniflash.release.tiimage - > Update image file  to sbl_uart_uniflash.release.hs_fs.tiimage

    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
    --file=sbl_prebuilt/am64x-sk/sbl_null.release.tiimage --operation=flash --flash-offset=0x0 - > - Update image file  to sbl_null.release.hs_fs.tiimage

    Procedure :

    1. POWER OFF
    2. Put the board in UART BOOT MODE
    3. Open the following path and open a command prompt window, then you give the below command.

    C:\ti\mcu_plus_sdk_am64x_08_04_00_17\tools\boot

    Command : python uart_uniflash.py -p COM8 --cfg=sbl_prebuilt/am64x-evm/default_sbl_null.cfg.

    Note : Pease change the com port number based on your USB port number.

    4. Wait for App image transfer via UART .

    5. Power OFF and put the board in OSPI BOOT MODE


    6. POWER ON

    7. Compile your applications and load applications directly from CCS

    default_sbl_ospi cfg: This step is necessary when you want to load programs into external memory

    # First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
    --flash-writer=sbl_prebuilt/am64x-sk/sbl_uart_uniflash.release.tiimage - > Update image file  to sbl_uart_uniflash.release.hs_fs.tiimage

    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
    --file=sbl_prebuilt/am64x-sk/sbl_ospi.release.tiimage --operation=flash --flash-offset=0x0 - > - Update image file  to sbl_ospi.release.hs_fs.tiimage


    Please let me know if this helps your query .


    Regards,
    S.Anil.
  • 0 in reply to Swargam Anil
    Prodigy 101 points

    Thanks!!! I attach the modified .cfg file
    default_sbl_null.hs_fs.cfg