• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 303 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: CDDIpc usage about sending data.

HONGRUN ZHAO
Intellectual 555 points
Part Number: TDA4VM

In v7.03 RTOS+QNX software plantform.  

Our project apply CDD IPC to communication between MPU(vision_apps) and mcu1_0(mcusw). 

1 . If Ipc function be designed as below?  Ipc with a pair endpiont works as in half duplex mode, only send date in one 

direction at a time.

2 . To release IPC works in full duplex mode.  If two pair endpoints should be created to build two channels?

Data can be send in two direction at a time as below:

  • 0
    TI__Guru* 89985 points

    Hi Hongrun,

    The Linux IPC uses the concept of rpmsg endpoints. You have a local end-point (on MPU) and a remote end-point (MCU1_0) which are used for receiving messages.

    The typical usage model is that of a Server (on remoteproc) and Client (on Linux). The remote end-point is published to the Linux using the RPMessage_announce API() and the MPU local end-point is created dynamically when you open the corresponding rpmsg-char device. Any message sent to the remote-endpoint will include the local end-point addr in the rpmsg header, so you can use that to respond to MPU. You can have two different instances on Linux communicate with the same remote end-point.

    A pair of end-points should be enough for you to achieve duplex communication. You can always use uni-directional logical channels as well if you desire.

    regards

    Suman