TDA4VM: TDA4VM

Tanvi Gore

Part Number: TDA4VM

I found this reference https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_ipc_spi_master_slave_profile_top.html is it recommended for Inter core communication? and where can I find more details about which cores can communicate in this way?

over 2 years ago

0 Suman Anna over 2 years ago

TI__Guru* 80095 points

Hi Tanvi,

What OS would you be running on A72 Core?

There are multiple different IPC examples in the SDK. Are you looking for a MCAL compliant IPC example or just a base IPC example.

regards

Suman

0 Tanvi Gore over 2 years ago in reply to Suman Anna

Intellectual 722 points

Hi Suman,

SDK version:- Processor SDK RTOS J721E 07_03_00

1. OS running on A72 core is linux(SDK version ).

2.can you please tell me difference between MCAL compliant IP and base IPC and IPC using SPI

I referred

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_00_00_12/exports/docs/pdk_jacinto_08_00_00_37/docs/userguide/jacinto/modules/ipc.html#ipclld-design-details

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/ug_cdd_ipc_top.html

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_ipc_spi_master_slave_profile_top.html

is there anything else that can help me to differentiate between all three??

3. I want to communicate between MPU(A72 & R5) and MCU (R5F) ,as from ipc_spi_master_slave_profile can I change the cores for MPU and MCU as master and slave if yes where can I get api details to change it.

4. maximum data size that can be shared between two cores using Base IPC and MCAL compliant IPC.

Thanks & Regards,

Tanvi N. Gore

+1 Suman Anna over 2 years ago in reply to Tanvi Gore

TI__Guru* 80095 points

Hi Tanvi,

#2.

The links you referenced above are indeed the relevant ones.

The CDD IPC or the MCAL compliant IPC API is the base API to use for AutoSAR in Automotive usecases.

The PDK IPC is the base API to be used on remote processors (R5F, DSP etc) running an RTOS.

The A72 processor running Linux has its own interfaces owing to the userspace and kernel split and the remoteproc/rpmsg driver architecture.

All the above IPC form the traditional software IPC stack which just uses shared memory and some interrupts (Mailbox).

The IPC SPI demo with MCUSW is an example application show-casing communication using SPI peripheral. This example show-cases a master-slave SPI communication with master and slave on different processors running an RTOS (so not applicable to Linux).

#3. The IPC SPL demo is not designed to run the slave on A72 running Linux.

#4. The IPC uses the rpmsg transport, which is a processor-copy based transport. The maximum data payload for these is 496 bytes. If you want to share larger data, then it is preferable to use a separate shared memory and exchange pointers.

regards

Suman

Processors

Processors forum

TDA4VM: TDA4VM