• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 180 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.

AM6422: RPMSG

Elbon ba
Prodigy 90 points

Part Number: AM6422

Tool/software:

Hello,

I'm using mcu_plus_sdk_am64x_10_01_00_32 to try the RPMsg example, but when I debug the code, the compiler blocks as shown in the screenshot below. I just have the debug log in the ipc_rpmsg_echo_main function, and it doesn't show correctly all debugs.

  • 0
    TI__Mastermind 40580 points

    Hi Elbon, I already replied in the other thread, but let me copy as well here in case it helps someone else.

    I think I know the reason. In CCS you should "Load Symbols" instead of "Load program"

    From academy we have:

    Debug the remote core through CCS: dev.ti.com/.../node

    "After connecting CCS to the remote core, DO NOT reset the remote core! Instead, select Load > Load Symbols, and select the firmware binary that is currently running on the remote core.

    You DO NOT want to reset the remote core, because if RPMsg code is running on the remote core, it will wait for Linux to re-supply the information that Linux wrote into the resource table when Linux first initialized the core. Since Linux already wrote that information once, and Linux is not aware that CCS reset the core, the remote core will hang until the entire processor is rebooted."

    Also, if you want to step through one of the cores, you need to add a while() loop as explained there as well

    thank you,

    Paula