Hello all ,
- I'm exploring sample example for ARM A53 to ARM R5F communication (i.e Linux to RTOS Communication ) present in <TI-IPC-SDK>ipc_3_50_03_05/examples/AM65XX_linux_elf/ex02_messageq/host/bin/release
- I'm using Processor SDK Linux 6_00_00_07 , TI IPC SDK version ipc_3_50_03_05
- I've verified that I'm able to see remoteproc entries for both core of R5F as follows :
root@am65xx-evm:~# grep -Isr r5f /sys/kernel/debug/remoteproc/
/sys/kernel/debug/remoteproc/remoteproc1/resource_table: Name trace:r5f1
/sys/kernel/debug/remoteproc/remoteproc1/name:41400000.r5f
/sys/kernel/debug/remoteproc/remoteproc0/resource_table: Name trace:r5f0
/sys/kernel/debug/remoteproc/remoteproc0/name:41000000.r5
I have loaded R5F firmware (respective to R5F core ) required to run following example .I'm able to run following example for core 0 as follows
root@am65xx-evm:~/mr5f/Build_Output/Build_01/AM65XX_linux_elf/ex02_messageq/host/bin/release# ./app_host R5F-0 --> main: --> Main_main: --> App_create: App_create: Host is ready <-- App_create: --> App_exec: App_exec: sending message 1 App_exec: sending message 2 App_exec: sending message 3 App_exec: message received, sending message 4 App_exec: message received, sending message 5 App_exec: message received, sending message 6 App_exec: message received, sending message 7 App_exec: message received, sending message 8 App_exec: message received, sending message 9 App_exec: message received, sending message 10 App_exec: message received, sending message 11 App_exec: message received, sending message 12 App_exec: message received, sending message 13 App_exec: message received, sending message 14 App_exec: message received, sending message 15 App_exec: message received App_exec: message received App_exec: message received <-- App_exec: 0 --> App_delete: <-- App_delete: <-- Main_main: <-- main:
5.Running same example for core 1 ,Program halts and we need to manually terminate program to exit as follows .
root@am65xx-evm:~/mr5f/Build_Output/Build_01/AM65XX_linux_elf/ex02_messageq/host/bin/release# ./app_host R5F-1 --> main: --> Main_main: --> App_create:
In above case I have verified that R5F firmware for core1 is in running state
#cat /sys/class/remoteproc/remoteproc1/firmware am65x-mcu-r5f0_1-fw # cat /sys/class/remoteproc/remoteproc1/state running
Another observation is after restarting same R5F core 0 firmware again ECM console hangs .Need to Power Cycle Development board .
# echo stop > /sys/class/remoteproc/remoteproc1/state [ 1776.879902] remoteproc remoteproc1: stopped remote processor 41400000.r5f # echo start > /sys/class/remoteproc/remoteproc1/state [ 1784.811170] remoteproc remoteproc1: powering up 41400000.r5f [ 1784.821918] remoteproc remoteproc1: Booting fw image am65x-mcu-r5f0_1-fw, size 3797568 .... .... After this , Need to Power cycle EVM .
Queries :
- wanted to understand Linux user space application halted for Core 1..? I'm I missing any steps..?
- Why EVM console is halted after restarting firmware specific to core 1
Regards ,
Manish
