PROCESSOR-SDK-AM64X: M4F Gets Stuck After Multiple IPC Transfers with Linux

Brycen Hillukka

Tool/software:

Hello TI Team,

I am encountering the same issue as the previous forum on the AM64x where the M4F seems to hang after multiple IPC message transfers. My IPC setup is between Linux and the M4F.
When this issue occurs, Linux displays the same error message "Try increasing MBOX_TX_QUEUE_LEN, failed to send mailbox message, status = -105", and the M4F seems to get stuck in the infinite loop behavior described in the previous forum.

I also see at the end of the forum that the bug fixes were applied to the MCU+ SDK 10.1 for the AM62x and not the AM64x. What MCU+ SDK version will have the fix for the IPC hang on the AM64x? When is this expected to release?

Previous forum: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1365362/processor-sdk-am62x-multicore-development-ipc-process-multiple-endpoints-reserved-memory-purpose

Thank you for your help,

Brycen

10 months ago

0 Nick Saulnier 10 months ago

TI__Guru** 103890 points

Hello Brycen,

Thanks for linking to the previous thread, that made it a lot easier for me to follow up on the internal tickets I filed.

I asked the team to get the fixes done for the next SDK 11.0 (probably releasing around March/April. But I have not gotten an official timeline yet so that MIGHT change). However, just today I got the notification that the work is getting pushed back to SDK 11.1 (time unknown, no earlier than summer 2025).

Are you able to make changes based on the AM62x code that I linked at the bottom of that thread? If so, are you able to fix the behavior on your end?
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1365362/processor-sdk-am62x-multicore-development-ipc-process-multiple-endpoints-reserved-memory-purpose/5532041#5532041

If you are able to do a bit of development and testing on your side, and then share your code with me, I can talk with the team on my side to see if we can use your efforts as a shortcut to pull the timing back in for SDK 11.0. But I will wait for confirmation from you before starting that discussion with the developers.

Eventually the goal is to get the github project into a space where customers can contribute directly. However, it does not look like the repo is ready for that quite yet. I can also check with the team to see what the timeframe is for that: https://github.com/TexasInstruments/mcupsdk-core

Regards,

Nick

Processors

Processors forum

PROCESSOR-SDK-AM64X: M4F Gets Stuck After Multiple IPC Transfers with Linux