TDA4VM: Inquiry Regarding TDA4VM Security Proxy and TISCI Communication

Hi

Can you please elaborate on why you need to use TISCI protocol to establish communication between A72 and R5F? The TISCI protocol is not for generic message exchange but for very specific power, resource, security related requests and response. For generic communication between A72 and R5F we use TI IPC i.e. TI's Inter Processor Communication.

For IPC there are demos in the SDK, are you running Linux on A72 and FreeRTOS on R5F?

Regards

Karan

Yep, could you please provide the method doc and demo of TI IPC? Maybe my previous understanding was wrong. I've run Linux on A72, RTOS on MCU R5, tried rpmsg_char, but the driver didn't work very well, starting the kernel times error: pcie: Failed to init phy. Link: README « examples - rpmsg/ti-rpmsg-char - Unnamed repository; edit this file 'description' to name the repository.

The booting log:

[ 4.050246] j721e-pcie 2910000.pcie: host bridge /bus@100000/pcie@2910000 ranges:
[ 4.057728] j721e-pcie 2910000.pcie: IO 0x0018001000..0x0018010fff -> 0x0018001000
[ 4.065805] j721e-pcie 2910000.pcie: MEM 0x0018011000..0x001fffffff -> 0x0018011000
[ 4.073883] j721e-pcie 2910000.pcie: IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[ 4.082336] j721e-pcie 2910000.pcie: Failed to init phy

And the Terminal log when i insmod: 

root@j7-evm:/lib/modules/5.10.162-g76b3e88d56/kernel/drivers/remoteproc# insmod pru_rproc.ko
[ 1115.035854] pru_rproc: Unknown symbol pruss_cfg_update (err -2)
[ 1115.041799] pru_rproc: Unknown symbol pruss_cfg_read (err -2)
insmod: ERROR: could not insert module pru_rproC.ko: Unknown symbol in module
root@j7-evm:/lib/modules/5.10.162-g76b3e88d56/kerne1/drivers/remoteproc#

Sure, I will ask my colleague to point you to the IPC examples in the SDK.

Regards

Karan

It will be better if you can provide IPC docx related to the process: SBL-->tifs-->bootapp-->atf_optee-->dtb-->kernel-->filesystem. Waiting for your reply, thank you.

Hello,

You could see into URL https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/09_00_01_03/exports/docs/linux/Foundational_Components_IPC_J721E.html

Regards

Tarun Mukesh

Yeah~I have tested with reference to this document and  r0,r3~r8 is PASSED, but failed to test r1 and r2 using rpmsg_char_simple. The failure log looks like this:

root@j7-evm:/sys/bus/rpmsg# rpmsg_char_simple -r0 -n5
Created endpt device rpmsg-char-0-1360, fd = 3 port = 1024
Exchanging 5 messages with rpmsg device ti.ipc4.ping-pong on rproc id 0 ...

Sending message #0: hello there 0!
Receiving message #0: hello there 0!
Sending message #1: hello there 1!
Receiving message #1: hello there 1!
Sending message #2: hello there 2!
Receiving message #2: hello there 2!
Sending message #3: hello there 3!
Receiving message #3: hello there 3!
Sending message #4: hello there 4!
Receiving message #4: hello there 4!

Communicated 5 messages successfully on rpmsg-char-0-1360

TEST STATUS: PASSED

root@j7-evm:/sys/class/remoteproc# rpmsg_char_simple -r1 -n5
_rpmsg_char_find_rproc: 41400000.r5f is either not probed or not a remoteproc!
Can't create an endpoint device: No such file or directory

Why is this? I used the default installation package and didn't make any changes. Thanks.

 https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/09_00_01_03/exports/docs/linux/Foundational_Components_IPC_J721E.html

Hi Tarun, How do I set this up? Your help is my biggest motivation.

Hello,

Can you confirm whether you are using SBL or SPL boot flow ? 

and also may i know what is you use case here to use MCU R5F in split mode which usually is preferred to be lock step mode ?

Regards

Tarun Mukesh

Yep, Tarun,  My process is SBL boot flow, and I just wanted the two MCU R5Fs to be able to work independently, so SplitMode was what I wanted. Does LockSteps mean that the states of the two nuclei are exactly the same? Can it be interpreted as redundant design?

Hello,

In SBL, MCU1_0 will be in split mode itself I thought it was in SPL earlier. If you are using boot app then can you check whether your modified boot app loads any firmware on MCU1_1.

Ni Hua said:

_rpmsg_char_find_rproc: 41400000.r5f is either not probed or not a remoteproc!

This statement arises me doubt that no firmware is running on the core.Can you please check any firmware is loaded on MCU1_1 and running ? if so can you let me know which firmware is it running.

Please share me the log as well.

Regards

Tarun Mukesh

Hi, I have asked a new qustion and here is my test log: (1) TDA4VM: Do I need to add these ipc xer5f after BootApp? - Processors forum - Processors - TI E2E support forums

Hi, I have asked a new qustion and here is my test log: (1) TDA4VM: Do I need to add these ipc xer5f after BootApp? - Processors forum - Processors - TI E2E support forums

OK, thank you very much.