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.

AM6442: PROCESSOR-SDK-AM64X compatibility matrix

Part Number: AM6442

Tool/software:

Hi,

we try to implement a inter-processor communication (IPC) especially shared ethernet between R5 (FreeRTOS) and A53 (Linux) core.

I want to know which MCU PLUS SDK and Industrial SDK version on the FreeRTOS side matches the processor sdk linux on the linux side that the IPC communication should work.

Thank you

  • Hello Martin,

    Can you give us a bit more information about your usecase?

    For example:

    1) Do you want to use a specific Ethernet protocol, or just "generic Ethernet"?

    2) How much data are you trying to pass between cores? Are there any latency needs?

    3) Anything else we should be aware of?

    Regards,

    Nick

  • Hi Nick,

    1) "generic Ethernet" should be fine

    2) we have no realtime constrains. Just best effort.

    3) right now we use mcu plus sdk 09.01.00 in our application. We want to extend the application with a new linux core setup. In the near future we plan to migrate to the latest mcu plus sdk version. Now we are asking if we have to start with processor sdk linux 9 or can we just pick the latest to minimize migrations?

    Best Regards,

    Martin

  • Hello Martin,

    Are you on the same project as Dominik & Luka?

    They are looking into the EthernetIP tunneling example to share Ethernet frames between Linux and R5F:
    TMDS64EVM: EthernetIP Adapter Tunneling not working on evalboard
    AM6442: AM64x Shared Ethernet between R0 (FreeRTOS) and A53 (Linux), RPMessage issue

    That same tunneling example should be able to be modified to work with "generic Ethernet" as well, though I am not sure if we have actually tried porting it to regular Ethernet at this point in time.

    If you do decide to modify that code for generic Ethernet, then I would suggest starting with SDK 11.x for all software components. Basically, let's get Luka's unmodified EthernetIP tunneling example working. Once that is working, then you can start looking at changing one part at a time to get the generic Ethernet working.

    Regards,

    Nick