LINUXSDK-OMAPL138: IS the IPC version locked to Linux from particular SDK version?

When the comms between DSP and Arm starts this is the warning I get:

Apr 17 14:38:09 F280Series-10-8-0-49 kernel: virtio_rpmsg_bus virtio0: msg received with no recipient

Hello Mitesh,

Setting support expectations up front: 

For OMAP-L138, I can point to the SDK's IPC documentation, but that is all the assistance I will be able to provide.

Linux SDK: https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/linux/Foundational_Components_IPC.html 

TI-RTOS SDK: https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_Foundational_Components.html#ipc 

ok, what kind of design support can I expect on OMAP-L138 at this point?

For the moment, our team can continue offering design support for hardware questions on OMAP-L138.

OMAP-L138 software design support is in a bit of a weird state. The last version of Linux SDK that we released for OMAP-L138 (Linux processor SDK 6.3) was released 4 years ago, which means that we are no longer able to provide full design support on the code. In general, you can think about this as "kind of supported". We can still assign your threads to engineers who might be able to help debug by referencing later code running on newer processors.

On the other hand, we can no longer provide any design support for the TI-RTOS code, as discussed here
https://www.ti.com/tool/PROCESSOR-SDK-OMAPL138
and here
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1071334/notice-regarding-processor-sdk-ti-rtos-for-am335x-am437x-omap-l13x-c674x-k2g-devices

I am not able to provide additional design support for IPC because

1) I cannot support the TI-RTOS half of the code, and

2) SDK 6.3 was the last time we used IPC3.x, so I can't even support the Linux half of the IPC code by referencing later code running on other processors.

Hopefully the SDK documentation is helpful for you,

Nick

Thanks for your reply Nick.

I will have a look at the various links.

I hope you will be able to help me with this: I am getting following error when running IPC example.

Apr 15 16:12:01 F280Series-10-8-254-254 kernel: virtio_rpmsg_bus virtio0: msg received with no recipient
Apr 15 16:12:21 F280Series-10-8-254-254 kernel: virtio_rpmsg_bus virtio0: inbound msg too big: (512, 504)

If the buffer size is 512 then what is the error? th3e buffer I have created for message Q is 504.

Thanks 

HI Nick, yes it works all well with 496 bytes. 

The issue we have is 504 bytes data we were sending using IPC 3.46 but now moving to IPC 3.50 we get this issue. Probably this is because the header packet length is increased by 8 bytes.

Thanks 

Hello Mitesh,

Glad to hear things are working for you now! If additional questions come up, feel free to post a new thread - even with our limited support, we may be able to help out.

Regards,

Nick

Will do, Thanks Nick.

Cheers.