• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 33 subscribers
  • Views 684 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:

LP-AM243: Cannot flash LwIP example

MCU-PLUS-SDK-AM263X: AM263x-CC: Error when flashing

Alexander Baehr
Intellectual 627 points
Other Parts Discussed in Thread: MCU-PLUS-SDK-AM263X, UNIFLASH

art Number: MCU-PLUS-SDK-AM263X

Hello experts,

I am trying to flash a multicore application for AM263x-CC using mcu_plus_sdk_am263x_08_04_00_17 and uart-uniflash.py. I get an error from the uniflash tool.

I cross-checked with the LED blink example, this one flashes and boots fine.

Please find below the output from the uniflash tool and my appimage

BR

Alexander

Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\pro\1900\system-tests\boot>flash_program.bat

C:\pro\1900\system-tests\boot>python C:\DevTools\TI\mcu_plus_sdk_am263x_08_04_00_17\tools\boot\uart_uniflash.py -p COM21 --cfg=program.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 6 command(s) !!!

Executing command 1 of 6 ...
Found flash writer ... sending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_uart_uniflash.debug.tiimage
Sending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_uart_uniflash.debug.tiimageSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_uart_uniflash.debug.tiimage Sent flashwriter C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_uart_uniflash.debug.tiimage of size 67398 bytes in 8.34s.

Executing command 2 of 6 ...
Command arguments : --operation=flash-phy-tuning-data
Sent flash phy tuning data in 3.59s.
[STATUS] SUCCESS !!!

Executing command 3 of 6 ...
Command arguments : --operation=erase --erase-size=0x200000 --flash-offset=0x0
Sent flash erase command.
[STATUS] SUCCESS !!!

Executing command 4 of 6 ...
Command arguments : --file=C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage --operation=flash --flash-offset=0x0
Sending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 182133bSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 182133bSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 183162bSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 183163bSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 183164bSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 183165bSending C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage: 183166b Sent C:/DevTools/TI/mcu_plus_sdk_am263x_08_04_00_17/tools/boot/sbl_prebuilt/am263x-cc/sbl_qspi.debug.tiimage of size 181702 bytes in 19.71s.
[STATUS] SUCCESS !!!

Executing command 5 of 6 ...
Command arguments : --file=../D5-System/Debug/D5_system.appimage --operation=flash --flash-offset=0x80000
Sending ../D5-System/Debug/D5_system.appimage: 459965bytes [00:45, 10947.04bytes/s]recv error: getc timeout in start sequence
Sending ../D5-System/Debug/D5_system.appimage: 459967bytes [00:55, 10947.04bytes/s]expected sequence 2, got (seq1=1, seq2=1), receiving next block, will NAK.
recv error: purge, requesting retransmission (NAK)
Sending ../D5-System/Debug/D5_system.appimage: 459967bytes [01:00, 10947.04bytes/s]

(remains forever...)

7356.Debug.zipprogram.cfg

  • 0
    TI__Guru 55955 points

    Hi Alex,

    From the log it seems the last step of writing the application image is waiting forever. You also mentioned that when you use the LED blinking example, it works as expected. I think the size of the appImage may be the cause. Can you ask your customer to try with smaller appImage?

    The other alternative is to use the C:\ti\mcu_plus_sdk_am64x_08_04_00_17\examples\drivers\boot\sbl_jtag_uniflash to load and flash your appImage using JTAG.

    Please refer to AM263x MCU+ SDK: SBL JTAG Uniflash (ti.com) for details.

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Intellectual 627 points

    Hi Ming,

    first, you were right with the size. By just cutting the appimage, I found the limit is between 60000h and 68000h. Is this going to be fixed? Since the device has 2 MB of RAM, I would expect that an image of that size can be loaded.

    With the sbl_jtag_uniflash, I was able to flash and verity the files. The LED blinking example also starts from Flash, but the D5_System does not. Please note that

    - the appimage_xip was not loaded, however, it should be empty
    - The D5_System uses two cores, as opposed to the example

    Are you able to reproduce the issue? The D5_System.appimage should blink LD13 when it starts.

    best regards,

    Alex

  • 0 in reply to Alexander Baehr
    TI__Guru 55955 points

    Hi Alex,

    Thank you so much for your confirmation. totally agree with you on the appImage size should be bigger. I will report this issue with the software development team. Will get back to you as soon as I get the estimation of the schedule for fixing this issue.

    I do not think it is related to the multi-core appImage, because we have an IPC notify example which uses 5 cores (1 M4 and 4 R5Fs). I believe it is pure the appImage size issue. 

    C:\ti\mcu_plus_sdk_am263x_08_04_00_17\examples\drivers\ipc\ipc_notify_echo\am263x-cc

    Best regards,

    Ming

  • +1 in reply to Ming Wei
    TI__Guru 55955 points

    Hi Alex,

    I was able to flash your D5_System.appimage (447KB)

    and the D5_Systemappimage can be boot from QSPI flash, although the display is kind of weird:

    The only difference is that I used the modified default_sbl_qspi.cfg instead of using your program.cfg:

    default_sbl_qspi.cfg

    Best regards,

    Ming