This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
工具与软件:
您好、TI 支持团队:
我使用的是 TI TDA4VH J784S4架构、想使用 IPC_BareMetal_echo_test 示例通过 A72内核与所有可用内核(R5F 和 C7x DSP)进行 IPC 通信。
我已经执行了以下文件中提到的步骤。
e2e.ti.com/.../CPU-Load-Baremental-binary-file-for-R5F-and-C7x-DSP-_2800_TDA4VH_2900_.docx
重新启动 EVM 板后。
我已经尝试了 rpmsg_char_sample 来传输 R5F 内核(j784s4-main-r5f0_0-FW 和 j784s4-main-r5f0_1-FW)。 显示误差。
请帮助以下查询:
为什么 RPMsg_char_sample 不适用于 IPC_BareMetal_echo_test 示例?
我还参考了: TDA4VH-Q1:C71在裸机上运行时是否支持 IPC?-处理器论坛-处理器- TI E2E 支持论坛 票证
而且 TT 解决方案是否仍然有效? 请刷新我们。
你好、lokesh、
是的、我在上面提到的主题中所说的都是正确的。 在 R5F 内核上、您可以从 MCU1_0独立运行裸机、因为它包含需要基于操作系统运行的 DM。
您可以参阅 https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1406023/j784s4xevm-build-ipc-echo-test-for-j784s4/5394120#5394120 以运行基于 FreeRTOS 的测试。
[quote userid="627247" url="~/support/processors-group/processors/f/processors-forum/1437422/processor-sdk-j784s4-tda4vh-request-for-baremetal-ipc-communication-sample-for-ti-tda4vh-j784s4-linux-environment 为什么 RPMsg_char_sample 对 IPC_BareMetal_echo_test 示例不起作用?它将适用于 R5F 内核、但您需要正确集成、请按照上述线程中的步骤操作、您可以使用 IPC_BareMetal_echo_test 为该内核执行复制。
此致
Tarun Mukesh
大家好、 Tarun Mukesh Puvvada、
现在、我已经使用 ti-processor-sdk-rtos-j784s4-evm-09_02_00_05.tar.gz 编译并尝试了 ipc_BareMetal_echo_test 示例。
它适用于 R5F 内核、但 SDK 10.00.00.05无法按照之前的通信正常工作。
我已附上工作 SDK 09.0200.05的结果如下。
lrwxrwxrwx 1 root root 75 Nov 13 14:18 j784s4-c71_0-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_freertos_c7x_1_release_strip.xe71 lrwxrwxrwx 1 root root 77 Mar 9 2018 j784s4-c71_0-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_1_release_strip.xe71.signed lrwxrwxrwx 1 root root 66 Nov 12 16:09 j784s4-c71_1-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_2_release_strip.xe71 lrwxrwxrwx 1 root root 77 Mar 9 2018 j784s4-c71_1-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_2_release_strip.xe71.signed lrwxrwxrwx 1 root root 66 Nov 12 16:10 j784s4-c71_2-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_3_release_strip.xe71 lrwxrwxrwx 1 root root 77 Mar 9 2018 j784s4-c71_2-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_3_release_strip.xe71.signed lrwxrwxrwx 1 root root 66 Nov 12 16:10 j784s4-c71_3-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_4_release_strip.xe71 lrwxrwxrwx 1 root root 77 Mar 9 2018 j784s4-c71_3-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_c7x_4_release_strip.xe71.signed lrwxrwxrwx 1 root root 71 Nov 13 10:11 j784s4-main-r5f0_0-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_freertos_mcu2_0_release.xer5f lrwxrwxrwx 1 root root 70 Nov 13 16:47 j784s4-main-r5f0_1-fw -> /lib/firmware/ti-ipc/j784s4/ipc_baremetal_echo_test_mcu2_1_debug.xer5f lrwxrwxrwx 1 root root 70 Nov 13 16:37 j784s4-main-r5f1_0-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_baremetal_test_mcu3_0_debug.xer5f lrwxrwxrwx 1 root root 68 Nov 12 16:10 j784s4-main-r5f1_1-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu3_1_release_strip.xer5f lrwxrwxrwx 1 root root 79 Mar 9 2018 j784s4-main-r5f1_1-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu3_1_release_strip.xer5f.signed lrwxrwxrwx 1 root root 70 Nov 13 14:31 j784s4-main-r5f2_0-fw -> /lib/firmware/ti-ipc/j784s4/ipc_baremetal_echo_test_mcu4_0_debug.xer5f lrwxrwxrwx 1 root root 79 Mar 9 2018 j784s4-main-r5f2_0-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu4_0_release_strip.xer5f.signed lrwxrwxrwx 1 root root 72 Nov 13 16:13 j784s4-main-r5f2_1-fw -> /lib/firmware/ti-ipc/j784s4/ipc_baremetal_echo_test_mcu4_1_release.xer5f lrwxrwxrwx 1 root root 79 Mar 9 2018 j784s4-main-r5f2_1-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu4_1_release_strip.xer5f.signed lrwxrwxrwx 1 root root 66 Nov 12 16:10 j784s4-mcu-r5f0_0-fw -> /lib/firmware/ti-eth/j784s4/app_remoteswitchcfg_server_strip.xer5f lrwxrwxrwx 1 root root 73 Nov 12 16:10 j784s4-mcu-r5f0_0-fw-sec -> /lib/firmware/ti-eth/j784s4/app_remoteswitchcfg_server_strip.xer5f.signed lrwxrwxrwx 1 root root 68 Nov 12 16:10 j784s4-mcu-r5f0_1-fw -> /lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu1_1_release_strip.xer5f lrwxrwxrwx 1 root root 79 Mar 9 2018 j784s4-mcu-r5f0_1-fw-sec -> /usr/lib/firmware/ti-ipc/j784s4/ipc_echo_test_mcu1_1_release_strip.xer5f.signed root@j784s4-evm:~# rpmsg_char_simple -r4 -n10 Created endpt device rpmsg-char-4-1220, fd = 4 port = 1025 Exchanging 10 messages with rpmsg device rpmsg-char-4-1220 on rproc id 4 ... Sending message #0: hello there 0! Received message #0: round trip delay(usecs) = 145430 hello there 0! Sending message #1: hello there 1! Received message #1: round trip delay(usecs) = 136995 hello there 1! Sending message #2: hello there 2! Received message #2: round trip delay(usecs) = 155685 hello there 2! Sending message #3: hello there 3! Received message #3: round trip delay(usecs) = 170040 hello there 3! Sending message #4: hello there 4! Received message #4: round trip delay(usecs) = 143890 hello there 4! Sending message #5: hello there 5! Received message #5: round trip delay(usecs) = 163920 hello there 5! Sending message #6: hello there 6! Received message #6: round trip delay(usecs) = 148725 hello there 6! Sending message #7: hello there 7! Received message #7: round trip delay(usecs) = 158015 hello there 7! Sending message #8: hello there 8! Received message #8: round trip delay(usecs) = 154100 hello there 8! Sending message #9: hello there 9! Received message #9: round trip delay(usecs) = 164950 hello there 9! Communicated 10 messages successfully on rpmsg-char-4-1220 TEST STATUS: PASSED
我执行了下面文件中提到的相同步骤、这与上面的查询中提到的步骤相同。
Lokesh 您好!
IPC echo 测试中的 SDK 9.2与10.0没有不同、您在 SDK 9.2中遵循的步骤对于 SDK 10.0也是相同的。 我认为可能存在加载问题,或者可能是生成的可执行文件有问题。 除此之外,我看不出任何问题.
此致
Tarun Mukesh
如您所述 "加载问题、也可能是生成的可执行文件有问题"。
您能帮助我们从最后调试和解决这个问题吗
我们的工作日程安排很紧。 请尽快为调试该问题提供帮助。