• 状态
  • 已锁定 已锁定
  • 个回复 3 个回复
  • 名订阅用户 15 名订阅用户
  • 次查看 744 次查看
  • 用户 0 名在线用户
选项
选项
相关

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.

TDA4VM: The rpmsg_chrdev driver reported an error when IPC was used by different Linux processes

N/A N/A
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?

  • 0

    • The version we used was SDK7.2

  • 0
    TI__Guru* 81380 points

    Hi we have received your question and feedback to the engineer, if there is any updates I will reach to you asap. Thanks.

  • 0 回复 Cherry Zhou
    TI__Guru* 81380 points

    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).

x 出现错误。请重试或与管理员联系。