TDA4VH-Q1: IPC examples for J784S4

Tony Tang

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VM, AM69

Hello,

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/09_01_00_06/exports/docs/pdk_j784s4_09_01_00_22/docs/userguide/j784s4/modules/ipc.html

in the table 4.8.7. Running the IPCLLD examples

J784S4 is not in the supported device list.

But in the Linux user guide remote core booting section, there is IPC example.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_01_00_06/exports/docs/linux/Foundational_Components_IPC_J784S4.html#booting-remote-cores-from-linux-console-user-space

Which is right?

I need a simple IPC exmple of C71x.

over 1 year ago

0 Tarun Mukesh Puvvada over 1 year ago

TI__Mastermind 48446 points

Hello,

You can ipc_echo_test on J784s4 as well , it may not be mentioned in the document .Can you please run the test and let me know if you face any problems.

ipc_echo_test

This is the most generic application where mpu1_0 is running Linux, and all other cores are running BIOS. All cores talk to each other bi-directionally. Each core will send a ping message and remote end will respond with a pong message.
There are 10000 ping/pong messages exchanged between each core pair.
The messaging with Linux is initiated from Linux using rpmsg-client-sample.

Regards

Tarun Mukesh

0 Tony Tang over 1 year ago in reply to Tarun Mukesh Puvvada

TI__Mastermind 28912 points

run on TDA4VM with prebuilt image, follow the guide to execute command, but no output.

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

root@j721e-evm:~# ls -l /lib/firmware
total 25356
-rw-r--r-- 1 root root    2040 Mar  9  2018 LICENCE.ibt_firmware
-rw-r--r-- 1 root root    2046 Mar  9  2018 LICENCE.iwlwifi_firmware
-rw-r--r-- 1 root root  478552 Mar  9  2018 bl32.bin
-rw-r--r-- 1 root root 4295864 Mar  9  2018 bl32.elf
drwxr-xr-x 2 root root    4096 Mar  9  2018 cadence
drwxr-xr-x 2 root root    4096 Mar  9  2018 intel
-rw-r--r-- 1 root root  918268 Mar  9  2018 iwlwifi-3160-17.ucode
-rw-r--r-- 1 root root 2448976 Mar  9  2018 iwlwifi-8000C-34.ucode
-rw-r--r-- 1 root root 2428004 Mar  9  2018 iwlwifi-8000C-36.ucode
-rw-r--r-- 1 root root 2440780 Mar  9  2018 iwlwifi-8265-34.ucode
-rw-r--r-- 1 root root 2436632 Mar  9  2018 iwlwifi-8265-36.ucode
-rw-r--r-- 1 root root 2678092 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-34.ucode
-rw-r--r-- 1 root root 2521412 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-38.ucode
-rw-r--r-- 1 root root 1489652 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-46.ucode
lrwxrwxrwx 1 root root      69 Mar  9  2018 j7-c66_0-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_c66xdsp_1_release_strip.xe66
lrwxrwxrwx 1 root root      76 Mar  9  2018 j7-c66_0-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_c66xdsp_1_release_strip.xe66.signed
lrwxrwxrwx 1 root root      69 Mar  9  2018 j7-c66_1-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_c66xdsp_2_release_strip.xe66
lrwxrwxrwx 1 root root      76 Mar  9  2018 j7-c66_1-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_c66xdsp_2_release_strip.xe66.signed
lrwxrwxrwx 1 root root      65 Mar  9  2018 j7-c71_0-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_c7x_1_release_strip.xe71
lrwxrwxrwx 1 root root      72 Mar  9  2018 j7-c71_0-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_c7x_1_release_strip.xe71.signed
lrwxrwxrwx 1 root root      67 Mar  9  2018 j7-main-r5f0_0-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu2_0_release_strip.xer5f
lrwxrwxrwx 1 root root      74 Mar  9  2018 j7-main-r5f0_0-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu2_0_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      67 Mar  9  2018 j7-main-r5f0_1-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu2_1_release_strip.xer5f
lrwxrwxrwx 1 root root      74 Mar  9  2018 j7-main-r5f0_1-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu2_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      67 Mar  9  2018 j7-main-r5f1_0-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu3_0_release_strip.xer5f
lrwxrwxrwx 1 root root      74 Mar  9  2018 j7-main-r5f1_0-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu3_0_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      67 Mar  9  2018 j7-main-r5f1_1-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu3_1_release_strip.xer5f
lrwxrwxrwx 1 root root      74 Mar  9  2018 j7-main-r5f1_1-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu3_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      67 Mar  9  2018 j7-mcu-r5f0_1-fw -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu1_1_release_strip.xer5f
lrwxrwxrwx 1 root root      74 Mar  9  2018 j7-mcu-r5f0_1-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu1_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru0_0-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt0_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru0_1-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt0_1.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru1_0-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt1_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru1_1-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt1_1.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu0_0-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt0_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu0_1-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt0_1.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu1_0-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt1_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu1_1-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt1_1.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru0_0-fw -> /lib/firmware/pru/TX_PRU_Halt_0.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru0_1-fw -> /lib/firmware/pru/TX_PRU_Halt_1.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru1_0-fw -> /lib/firmware/pru/TX_PRU_Halt_0.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru1_1-fw -> /lib/firmware/pru/TX_PRU_Halt_1.out
drwxr-xr-x 2 root root    4096 Mar  9  2018 pru
-rw-r--r-- 1 root root  247469 Mar  9  2018 pvdec_full_bin.fw
-rw-r--r-- 1 root root    4728 Mar  9  2018 regulatory.db
-rw-r--r-- 1 root root    1182 Mar  9  2018 regulatory.db.p7s
-rw-r--r-- 1 root root  131072 Mar  9  2018 rgx.fw.22.104.208.318
-rw-r--r-- 1 root root  131072 Mar  9  2018 rgx.fw.22.104.208.318.64k
-rw-r--r-- 1 root root  382744 Mar  9  2018 rgx.sh.22.104.208.318
-rw-r--r-- 1 root root      28 Mar  9  2018 tee-header_v2.bin
-rw-r--r-- 1 root root       0 Mar  9  2018 tee-pageable_v2.bin
-rw-r--r-- 1 root root  478552 Mar  9  2018 tee-pager_v2.bin
-rw-r--r-- 1 root root  478552 Mar  9  2018 tee-raw.bin
-rw-r--r-- 1 root root  478580 Mar  9  2018 tee.bin
-rw-r--r-- 1 root root 4295864 Mar  9  2018 tee.elf
drwxr-xr-x 2 root root    4096 Mar  9  2018 ti-connectivity
drwxr-xr-x 3 root root    4096 Mar  9  2018 ti-eth
drwxr-xr-x 3 root root    4096 Mar  9  2018 ti-ipc
root@j721e-evm:~#

==> /sys/class/remoteproc/remoteproc0/name <==
4d80800000.dsp

==> /sys/class/remoteproc/remoteproc1/name <==
4d81800000.dsp

==> /sys/class/remoteproc/remoteproc10/name <==
b004000.rtu

==> /sys/class/remoteproc/remoteproc11/name <==
b00a000.txpru

==> /sys/class/remoteproc/remoteproc12/name <==
b038000.pru

==> /sys/class/remoteproc/remoteproc13/name <==
b006000.rtu

==> /sys/class/remoteproc/remoteproc14/name <==
b00c000.txpru

==> /sys/class/remoteproc/remoteproc15/name <==
b134000.pru

==> /sys/class/remoteproc/remoteproc16/name <==
b104000.rtu

==> /sys/class/remoteproc/remoteproc17/name <==
b10a000.txpru

==> /sys/class/remoteproc/remoteproc18/name <==
b138000.pru

==> /sys/class/remoteproc/remoteproc19/name <==
b106000.rtu

==> /sys/class/remoteproc/remoteproc2/name <==
64800000.dsp

==> /sys/class/remoteproc/remoteproc20/name <==
b10c000.txpru

==> /sys/class/remoteproc/remoteproc3/name <==
41000000.r5f

==> /sys/class/remoteproc/remoteproc4/name <==
41400000.r5f

==> /sys/class/remoteproc/remoteproc5/name <==

root@j721e-evm:~# root@j721e-evm:~# echo stop > /sys/class/remoteproc/remoteproc4/state
-sh: root@j721e-evm:~#: command not found
root@j721e-evm:~# root@j721e-evm:~# echo start > /sys/class/remoteproc/remoteproc4/state
-sh: root@j721e-evm:~#: command not found
root@j721e-evm:~#
root@j721e-evm:~# echo start > /sys/class/remoteproc/remoteproc4/state
root@j721e-evm:~# echo stop > /sys/class/remoteproc/remoteproc4/state
root@j721e-evm:~# echo stop > /sys/class/remoteproc/remoteproc2/state
-sh: echo: write error: Invalid argument
root@j721e-evm:~# echo start > /sys/class/remoteproc/remoteproc2/state
root@j721e-evm:~# echo stop > /sys/class/remoteproc/remoteproc2/state
root@j721e-evm:~#

Same on AM69-SK:

root@am69a-sk:/opt/edgeai-gst-apps# ls -l /lib/firmware/
total 14928
-rw-r--r-- 1 root root    2040 Mar  9  2018 LICENCE.ibt_firmware
-rw-r--r-- 1 root root    2046 Mar  9  2018 LICENCE.iwlwifi_firmware
drwxr-xr-x 2 root root    4096 Mar  9  2018 cadence
drwxr-xr-x 2 root root    4096 Mar  9  2018 cnm
drwxr-xr-x 2 root root    4096 Mar  9  2018 intel
-rw-r--r-- 1 root root  918268 Mar  9  2018 iwlwifi-3160-17.ucode
-rw-r--r-- 1 root root 2448976 Mar  9  2018 iwlwifi-8000C-34.ucode
-rw-r--r-- 1 root root 2428004 Mar  9  2018 iwlwifi-8000C-36.ucode
-rw-r--r-- 1 root root 2440780 Mar  9  2018 iwlwifi-8265-34.ucode
-rw-r--r-- 1 root root 2436632 Mar  9  2018 iwlwifi-8265-36.ucode
-rw-r--r-- 1 root root 2678092 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-34.ucode
-rw-r--r-- 1 root root 2521412 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-38.ucode
-rw-r--r-- 1 root root 1489652 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-46.ucode
lrwxrwxrwx 1 root root      58 Mar  9  2018 j784s4-c71_0-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_c7x_1.out
lrwxrwxrwx 1 root root      73 Mar  9  2018 j784s4-c71_0-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_1_release_strip.xe71.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j784s4-c71_1-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_c7x_2.out
lrwxrwxrwx 1 root root      73 Mar  9  2018 j784s4-c71_1-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_2_release_strip.xe71.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j784s4-c71_2-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_c7x_3.out
lrwxrwxrwx 1 root root      73 Mar  9  2018 j784s4-c71_2-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_3_release_strip.xe71.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j784s4-c71_3-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_c7x_4.out
lrwxrwxrwx 1 root root      73 Mar  9  2018 j784s4-c71_3-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_4_release_strip.xe71.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-main-r5f0_0-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu2_0.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-main-r5f0_0-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu2_0_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-main-r5f0_1-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu2_1.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-main-r5f0_1-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu2_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-main-r5f1_0-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu3_0.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-main-r5f1_0-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu3_0_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-main-r5f1_1-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu3_1.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-main-r5f1_1-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu3_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-main-r5f2_0-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu4_0.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-main-r5f2_0-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu4_0_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-main-r5f2_1-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu4_1.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-main-r5f2_1-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu4_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      66 Mar  9  2018 j784s4-mcu-r5f0_0-fw -> /lib/firmware/ti-eth/j784s4/app_remoteswitchcfg_server_strip.xer5f
lrwxrwxrwx 1 root root      73 Mar  9  2018 j784s4-mcu-r5f0_0-fw-sec -> /lib/firmware/ti-eth/j784s4/app_remoteswitchcfg_server_strip.xer5f.signed
lrwxrwxrwx 1 root root      59 Mar  9  2018 j784s4-mcu-r5f0_1-fw -> /lib/firmware/vision_apps_eaik/vx_app_rtos_linux_mcu1_1.out
lrwxrwxrwx 1 root root      75 Mar  9  2018 j784s4-mcu-r5f0_1-fw-sec -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu1_1_release_strip.xer5f.signed
-rw-r--r-- 1 root root    4676 Mar  9  2018 regulatory.db
-rw-r--r-- 1 root root    1182 Mar  9  2018 regulatory.db.p7s
-rw-r--r-- 1 root root  151552 Mar  9  2018 rgx.fw.36.53.104.796
-rw-r--r-- 1 root root  383136 Mar  9  2018 rgx.sh.36.53.104.796
drwxr-xr-x 2 root root    4096 Mar  9  2018 ti-connectivity
drwxr-xr-x 3 root root    4096 Mar  9  2018 ti-eth
drwxr-xr-x 3 root root    4096 Mar  9  2018 ti-ipc
drwxr-xr-x 2 root root    4096 Mar  9  2018 vision_apps_eaik
lrwxrwxrwx 1 root root      39 Mar  9  2018 wave521c_codec_fw.bin -> /lib/firmware/cnm/wave521c_codec_fw.bin
root@am69a-sk:/opt/edgeai-gst-apps#
root@am69a-sk:/opt/edgeai-gst-apps# head /sys/class/remoteproc/remoteproc*/name
==> /sys/class/remoteproc/remoteproc0/name <==
64800000.dsp

==> /sys/class/remoteproc/remoteproc1/name <==
41000000.r5f

==> /sys/class/remoteproc/remoteproc10/name <==
67800000.dsp

==> /sys/class/remoteproc/remoteproc2/name <==
5c00000.r5f

==> /sys/class/remoteproc/remoteproc3/name <==
5d00000.r5f

==> /sys/class/remoteproc/remoteproc4/name <==
5e00000.r5f

==> /sys/class/remoteproc/remoteproc5/name <==
5f00000.r5f

==> /sys/class/remoteproc/remoteproc6/name <==
5900000.r5f

==> /sys/class/remoteproc/remoteproc7/name <==
5a00000.r5f

==> /sys/class/remoteproc/remoteproc8/name <==
65800000.dsp

==> /sys/class/remoteproc/remoteproc9/name <==
66800000.dsp
root@am69a-sk:/opt/edgeai-gst-apps#  echo stop > /sys/class/remoteproc/remoteproc5/state
-sh: echo: write error: Invalid argument
root@am69a-sk:/opt/edgeai-gst-apps#  echo start > /sys/class/remoteproc/remoteproc5/state
root@am69a-sk:/opt/edgeai-gst-apps#  echo stop > /sys/class/remoteproc/remoteproc5/state
root@am69a-sk:/opt/edgeai-gst-apps# cd /lib/firmware/

update with new build ipc image, also no output.

root@am69a-sk:/lib/firmware# ln -sf ipc_echo_test_freertos_c7x_1_release.xe71 j784s4-c71_0-fw
root@am69a-sk:/lib/firmware#
root@am69a-sk:/lib/firmware# echo start > /sys/class/remoteproc/remoteproc5/state
root@am69a-sk:/lib/firmware# echo stop > /sys/class/remoteproc/remoteproc5/state
root@am69a-sk:/lib/firmware# ln -sf ipc_echo_testb_freertos_c7x_1_release.xe71 j784s4-c71_0-fw
root@am69a-sk:/lib/firmware# echo stop > /sys/class/remoteproc/remoteproc5/state
-sh: echo: write error: Invalid argument
root@am69a-sk:/lib/firmware# echo start > /sys/class/remoteproc/remoteproc5/state
root@am69a-sk:/lib/firmware# echo stop > /sys/class/remoteproc/remoteproc5/state
root@am69a-sk:/lib/firmware# echo stop > /sys/class/remoteproc/remoteproc10/state
-sh: echo: write error: Invalid argument
root@am69a-sk:/lib/firmware# echo start > /sys/class/remoteproc/remoteproc10/state
root@am69a-sk:/lib/firmware# echo stop > /sys/class/remoteproc/remoteproc10/state
root@am69a-sk:/lib/firmware# echo stop > /sys/class/remoteproc/remoteproc0/state
-sh: echo: write error: Invalid argument
root@am69a-sk:/lib/firmware# echo start > /sys/class/remoteproc/remoteproc0/state
root@am69a-sk:/lib/firmware#

As there is not any output after start, I am not sure whether loaded and run the target core successfully.

0 Tarun Mukesh Puvvada over 1 year ago in reply to Tony Tang

TI__Mastermind 48446 points

Hello,

You mentioned the description as J784S4 but why again are you using J721E ? Can you please elaborate ?

Regards

Tarun Mukesh

0 Tony Tang over 1 year ago in reply to Tarun Mukesh Puvvada

TI__Mastermind 28912 points

Tarun,

I tried it on TDA4VM and AM69-SK board, none of it works.

Can you try it on your side.

0 Tarun Mukesh Puvvada over 1 year ago in reply to Tony Tang

TI__Mastermind 48446 points

Hello,

I tried it on TDA4VM and its successful,

Instead of using the default executable in ti-ipc folder , can you please compile it and then flash and check ?

Regards

Tarun Mukesh

0 Tony Tang over 1 year ago in reply to Tarun Mukesh Puvvada

TI__Mastermind 28912 points

Hello Tarun,

Thanks, with rpmsg* command as yours, it works.

but follow the section: 3.5.3. Booting Remote Cores from Linux console/User space

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

#1. It did not prompt as below, When I do it on AM62x, there is prompt. would you please elabrate it?

root@j721e-evm:~# echo start > /sys/class/remoteproc/remoteproc4/state
[  311.633427] remoteproc remoteproc4: powering up 5c00000.r5f
[  311.639692] remoteproc remoteproc4: Booting fw image j7-main-r5f0_0-fw, size 691508
[  311.655007] rproc-virtio rproc-virtio.16.auto: assigned reserved memory node r5f-dma-memory@a2000000
[  311.664718] virtio_rpmsg_bus virtio4: rpmsg host is online
[  311.672389] rproc-virtio rproc-virtio.16.auto: registered virtio4 (type 7)
[  311.680397] remoteproc remoteproc4: remote processor 5c00000.r5f is now up

#2. Is the MCU and DSP booted/loaded during Kernle lauching up? rpmsg just do communication test?

0 Tarun Mukesh Puvvada over 1 year ago in reply to Tony Tang

TI__Mastermind 48446 points

Hello,

Before SDK 9.0 we have ipc_echo_test linked by default as firmware's and now we have vision apps executable from 9.0.If you want to check working of rpmsg* commands .Please build the ipc_echo_test firmwares newly from sdk and then flash and check.

AM62x device is sitara and AM69 is jacinto , there shall be lot of differences.

Tony Tang said:
#2. Is the MCU and DSP booted/loaded during Kernle lauching up? rpmsg just do communication test?

yes its true. You can see the boot flow in the link you mentioned above.

Regards

Tarun Mukesh

Processors

Processors forum

TDA4VH-Q1: IPC examples for J784S4