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.

SK-AM64B: Flash SOC Initialization Binary Failed

Part Number: SK-AM64B


Hi,

I am trying to setup the Starter Kit for program execution and while trying to flash SOC initialization binary using UART BOOT MODE, I am encountering following errors.

When I used  AM64x MCU+ SDK  09.00.00.30 the EVM did not respond.

  

I switched to lower version, AM64x MCU+ SDK  08.06.00.43. I followed the steps suggested in below link.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1176407/tmds64evm-flash-the-soc-initialization-binary-to-the-evm-failed---error-xmodem-send-failed

Following error occurs

I am following the Guide:  https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/latest/exports/docs/api_guide_am64x/EVM_SETUP_PAGE.html

power cycling the device has not resolved the error in any case.

Also the Device Type is HS-FS.

Could you please help me resolve the error.

  • Hello Shruti,

    I have assigned your thread to another team member. Please note that responses may be delayed due to Diwali. Feel free to ping the thread if you do not have a response by the end of the week.

    Regards,

    Nick

  • Hello Shruti,

    I have looked at your steps, and all seem okay.

    I need the below details to further debug the issue.

    How did you confirm your HW is HS-FS?

    After keeping the HW in UART Boot mode and on the UART console, one string will print. Is it possible to share that string as well?

    Regards,

    S.Anil.

  • Hi,

    The confirmation of device type being HS-FS was done using SoC ID parser Python Script.



    Attaching the file which has string that gets printed on UART console.

    02000000011a0000616d3634780000000000000048534653000002000000020002a6000000000000b018658ad99dc903c8c9bfb27b12751099920a042ad1dfea7b7ba57369f15546de285edde6a7b39a8bdc40a27b237f8fb1e57f245e80b929c1e28b024aa2ecc6ad0bc40b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c3ca1ff115f9a6f1b70694d8d05101c25d58612d0f7bba3b8ae9986b2b83b1ed


    Regards,

    Shruti

  • Hello Shruti,

    As of now, I don't have any idea why this issue comes up on your HW, and you are doing all the right things.

    I can check your data one more time and will update the status by today evening.

    Regards,

    S.Anil.

  • Hello Shruti,

    Can you please try the same steps on another HW if you have a spare SK kit?

    Instead of using sbl_null, try using sbl_ospi boot mode.

    meantime, I can check any other possibilities to find out the root cause issue.

    Regards,

    S.Anil. 

  • Hello Shruti,

    Please try with latest binaries as well from the  below link .

    https://www.ti.com/tool/download/MCU-PLUS-SDK-AM64X/09.00.00.35

    Regards,

    S.Anil.

  • Hi,

    I have encountered another problem now, after POWER ON, the LED that glows after connecting UART to USB cable is not glowing anymore and One of the IC is getting heated up. 

    Are you suggesting to try the sbl_opsi boot mode in another SK kit?


    Regards,

    Shruti

  • I have encountered another problem now, after POWER ON, the LED that glows after connecting UART to USB cable is not glowing anymore and One of the IC is getting heated up. 

    Typically, the UART to USB LED should be ON after you connect a USB cable, and I am assuming that the IC that you pointed out that is heating up might belong to the UART to USB converter IC and might be gone.

    Check after configuring the HW in UART boot mode and see if you are able to get string data on the UART console.

    If this UART port works, try sbl_ospi  and sbl_null  boot modes on the issue board and on the new board with the latest binaries .

    When I used  AM64x MCU+ SDK  09.00.00.30 the EVM did not respond.

    May I know where you downloaded the 9.30 version since there are two versions, 9.31 and 9.35, in MCU+SDK, but I am checking with you that either you are using 9.30 or 9.31?

    Regards,

    S.Anil.

  • Hi,

    Here is the screenshot showing MCU+SDK version

    The UART port is not working.

    May I know what is the reason for such scenario? There we no changes done. The setup that was working yesterday has stopped working now.

    Currently we only have one board.

    Regards,

    Shruti

  • Hello Shruti,

    May I know what is the reason for such scenario? There we no changes done. The setup that was working yesterday has stopped working now.

    I am not the right person to comment on this since I am mostly an expert on the software side and not on the hardware side.

    But this type of issue mostly comes from ESD (touching directly IC's) , and any voltage spikes come when you plug and unplug cables.

    If the UART port LED is not ON and not printing any strings in the UART console, then the USB to UART converter IC might be gone.

    Here is the screenshot showing MCU+SDK version

    Ok, I can check with my team about these versions.

    Regards,

    S.Anil.