TDA4VM: TD4VM MCU2_1 and MCU1_0 use Cddipc with A72

Hello,

lixiaodong said:

  I can communicate with A72 using cddipc on MCU1_0 and MCU2_1 respectively. Now I can communicate with A72 using Cddipc on both MCU1_0 and MCU2_1, but the program is stuck at Ipc_isRemoteReady on MCU2_1.

You are able to communicate A72 to MCU1_0 but not with MCU2_1 ? is that your question ?

Sorry i didn't understand correctly, could you please tell me more clearly?

Regards

Tarun Mukesh

I now MCU1_0 can communicate with A72, but MCU2_1 can't communicate with A72.I want both MCU2_1 and MCU1_0 to communicate with A72 using CddIpc.

Hello,

We have an example which communicates MCU2_1 with A72 linux , 

ti-processor-sdk-rtos-j721e-evm-08_06_00_12/mcusw/mcal_drv/mcal/examples/CddIpcRProcLinux/soc/j721e/mcu2_1/CddIpcAppStartup.c

You can try using this application to understand ,why your application is halting.

Regards

Tarun Mukesh

When I first started, I debugged MCU2_1 communication with A72, and after MCU2_1 was able to communicate with A72, I began debugging MCU1_0 communication with A72. After MCU1_0 was able to communicate with A72, I found that MCU2_1 could not communicate with A72, and the MCU2_1 program was stuck at Ipc_isRemoteReady. Now, what I want is for MCU2_1 and MCU1_0 to communicate with A72 using Cddipc separately. Is it not currently supported for MCU2_1 and MCU1_0 to communicate with A72 using Cddipc separately?

Hello,

Have you reloaded the application on MCU2_1 ? How are testing the communication with A72 ?

Are you running custom applications on MCU2_1 ?

Regards

Tarun Mukesh