TDA4VM: RPMsg Communication Between R5F and A72 on TDA4VM

Danilo A.

Part Number: TDA4VM

Hi Team,

Posting on behalf of our customer.

We are currently working on the TDA4VM platform, and the user application rpmsg_char_simple runs as expected when initiated from the A72 side.

However, we are facing an issue while trying to initiate communication from R5F to A72 using RPMsg drivers. We are using RTOS SDK version 7.01.00.45, but the communication is not working as intended.

Setup Details:

Default RPMsg channel endpoints are not created.
We are using the char_simple application to create the endpoints manually.

Use Case:

R5F will send the data, and A72 will listen or read the data.

Implementation on R5F side:

IPC initialized and RPMsg parameters created:

bufMem = &pSendTaskBuf[rpmsgDataSize * arg1];

RPMessageParams_init(&params);

params.requestedEndpt = ENDPT_PING;

params.buf = bufMem;

params.bufSize = rpmsgDataSize;

handle = RPMessage_create(&params, &myEndPt);

if (!handle) {

    System_printf("STREAM: RPMessage_create failed\n");

    return;

}

status = RPMessage_getRemoteEndPt(dstProc,

                                   SERVICE_PING,

                                   &remoteProcId,

                                   &remoteEndPt,

                                   BIOS_WAIT_FOREVER);

if (status == IPC_SOK)

    break;

Task_sleep(100);

}

status = RPMessage_send(handle,

                         remoteProcId,

                         remoteEndPt,

                         myEndPt,

                         msg,

                         len);

On A72 side:
- We open the RPMsg channel and read the data.
Could you kindly provide suggestions or guidance on how to resolve this issue? Are there any additional steps or configurations required for RPMsg endpoints or communication flow? Any insights or recommended steps would be greatly appreciated.