TDA4VE-Q1: MCUSW 11.01 Cdd IPC

Hello,

ipc echo test examples are present in MCUPLUS SDK of J722S which will do PING PONG with CDD IPC.

software-dl.ti.com/.../EXAMPLES_DRIVERS_IPC_RPMESSAGE_ECHO.html

Regards

Tarun Mukesh

Hello Tarun,

The examples that you refer use IpcNotyfication_Sync. All cores (main and remote) send sync message 

(above log for MCU core as Main in ipc_echo)

However, CddIpcAPP does not send Sync. This causes infinite waiting from remote echo core (timeout forever is configured...):

So I can not use those echo examples mixed with no modifications. Please, tet us know how to proceed.

BR

Hello,

Are you using the below steps

Regards

Tarun Mukesh

After your last comment, I tried loading from CCS. Before that, I was using SBL and multi-image flashed in OSPI. But with CCS, there are no positive results. Please, Tarun, I am pretty sure that some changes should be made in the code/configuration to make it work, but it is not clear. Let me ask some questions:

1.- IPC_echo is by default prepared to have WKUP as the main core and the rest of the cores as remote. In those examples, SYNC is sent to all, but the remote cores are the ones that would send echoes. This is defined here:

Correct?

2.-  WKUP should be an IPC_ECHO remote core (not MAIN) to have the chance to send echoes back to CddIpcApp, right?

3.- If 2 is true, the IPC_ECHO build cannot be used as provided in the SDK. It needs to be changed to set WKUP as remote, because MCUSW provides an example that runs on mcu0_0 and sends "ping" messages, acting as the MAIN core. Isn't that right?

4.-  If sysconfig is not changed, when building 11_01_00_04/mcu_plus_sdk_j722s_11_01_00_15/examples/drivers/ipc/ipc_rpmsg_echo/j722s-evm/system_freertos_nortos/makefile, I obtain a multi-image that has all 5 cores communicating. This can be loaded by SBL and runs fine. To have a multi-image with only two cores, where WKUP is REMOTE and MCU is MAIN, I should change sysconfig to disable communication between the rest of the cores and change gMainCoreId and gRemoteCoreId to:

Please could you confirm this? 

5.- However, if WKUP is moved to be a remote core, it will wait forever for SYNC (IPC_Notify), which is not sent by CddIpcApp in MCU, right?

6.- Should the Sync waiting (inside the "IpcNotify_syncAll" call) be removed? Or should PDK_DM_R5_TEST be used (I don't see any reference to this macro)?

I would appreciate your help to make it work. 

BR

Please, could you be much more concise with VRING address and size alignment?. As far as I know, these addresses are selected in Tresos for CddIpcApp and Sysncfg for PDK. Could you point out exactly what the values  to be used?. Thanks

Hello,

I remember that part is same. A5000000 will be the base address on both MCUPLUSSDK and MCUSW.

Regards

Tarun Mukesh

Hi Tarun Mukesh Puvvada 

Pablo has found the following problems during this development:

-The documentation is not aligned with CddIpc.

-CddIpcApp does not compile with CDD_IPC_REMOTE_CORE_WKUP_R5FSS0_0_USED due to incorrect usage of variables.

-The PDK_DM_R5_TEST macro is not documented in IPC_ECHO, and could be used to make somehow a handshake between the cores

Can we expect this to be fixed in SDK 11.2 (LTS) for April'26?

Also, can you confirm TDA4VEN-Q1: [MCUSW] Cdd_Ipc communication with all cores - Ficosa - CMS Jacinto Forum - Ficosa - EP - TI E2E support forums is already fixed. It should have been in in SDK 11.1 but we would need confirmation that this would be included in SDK 11.2 (LTS) for April '26 (In can't reply in the ticket as it is closed but confirmation could be related to this one)

Thanks

Mònica