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.

TDA2EVM5777: IPC is not working between IPU1 and EVE while running A15 in Linux

Part Number: TDA2EVM5777
Other Parts Discussed in Thread: SYSBIOS

Hello,

Our team is working on a POC development using TDA2x (i.e)porting our algorithm stack into Tda2x.
To achieve real time, our algorithm demands more computing power, therefore we are planning to use A15, 2DSP and 4EVES available in DRA7xx-EVM(TDA2X).

Following are the environmental setup used at our end
1. Running Linux in A15 and Sysbios in all the other processors.
2. File system generated using yocto setup.

Understanding from the visionSDK linux user guide is that
A15 + Linux loads IPU and IPU intern loads each of the EVEs. Eve loading is successful and we were able to attach and debug the EVE firmware using a laughterbach jtag debugger.
But currently we are facing an issue in establishing a communication(IPC using MessageQ) between IPU1 and EVE processor.
As a first step just tried to do ipc_attach() in the EVE firmware, the EVE firmware is loaded properly by the IPU1(using SBL) but crashes in the Ipc_attach() call.
We are suspecting that EVE is not able to access the shared region. Is this an MMU related issue?

We don't find any ipc related examples for Linux(running in A15) between IPU1 and EVE.Please enlighten us with some documentation or examples to address this issue ASAP.

Kindly let me know if you are looking for more information.

Note:
IPC using MessageQ is working fine across.
A15(Linux) <-> DSP
A15(Linux) <-> IPU1
DSP(Linux) <-> IPU1