TI中文支持网Part Number:TDA4VM
If different Linux processes call appCommonInit(), the RPMSG driver will report the following error, but IPC can communicate normally (A72<–>R5F). If only one process calls appCommonInit() and another process does not call it, that process's IPC cannot be used .
How to solve this driver error? Does it matter?
N/A N/A：
The version we used was SDK7.2
,
Cherry Zhou：
Hi we have received your question and feedback to the engineer, if there is any updates I will reach to you asap. Thanks.
,
Cherry Zhou：
This is really a very strange error. Are the processes being run in parallel, or run back to back in real quick succession?
appCommonInit() sets up the Rx and Tx end-points within thar process, so it definitely needs to be called for each process.
The error -28 stands for ENOSPC, suggesting there is no free idr to allocate which should not happen with the parameters being passed (RPMSG_ADDR_ANY).
