[参考译文] PROCESSOR-SDK-J7200：使用 SDK-LINUX-version 10.01.08.01 运行与 Linux 并行的 MCU-APP

您好：

根据上述说明、我了解到您希望构建自己的自定义 DM 二进制文件以在 MCU 域 R5F 上运行。

您希望在区经理的基础上介绍哪些附加功能？

此致、

Keerthy  

好的、现在我想办法了、如何使 r5-mcu 应用程序使用 SPL 运行：我基本上在 k3-j7200-binman.dtsi-file 中将其设置为 ti-dm。

不过、我遇到了另一个问题：在使用 RTOS-SDK 构建的自定义二进制文件时、引导过程会失败、而不是默认的二进制文件 (board-support/prebuilt-images/ti-dm/j7200/ipc_echo_testb_mcu1_0_release_strip.xer5f)。

U-Boot SPL 2024.04-ti-ga970f6e51043 (Nov 13 2024 - 14:26:23 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
## No elf image at address 0x89000000
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.12.0(release):11.00.09-dirty
NOTICE:  BL31: Built : 12:35:58, Mar 24 2025
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Unable to query firmware capabilities (-60)
I/TC:
I/TC: OP-TEE version: 4.5.0-73-gef1ebdc23-dev (gcc version 13.3.0 (GCC)) #1 Tue Feb  4 11:33:18 UTC 2025 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_do_xfer:120 Message receive failed (-65523)
E/TC:0 0 ti_sci_init:480 Unable to communicate with control firmware (-65523)
E/TC:0 0 do_init_calls:22 early_initcall __text_start + 0x00072db8 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_do_xfer:120 Message receive failed (-65523)
E/TC:0 0 sa2ul_init:61 Failed to get SA2UL device
E/TC:0 0 do_init_calls:22 service_initcall __text_start + 0x00073120 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_do_xfer:120 Message receive failed (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_do_xfer:120 Message receive failed (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_do_xfer:120 Message receive failed (-65523)
E/TC:0 0 tee_otp_get_hw_unique_key:104 Could not get HUK
E/TC:0 0 do_init_calls:22 service_initcall __text_start + 0x00073148 failed
E/TC:0 0
E/TC:0 0 Core data-abort at address 0x14 (translation fault)
E/TC:0 0  esr 0x96000005  ttbr0 0x9e8af000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x600003c4
E/TC:0 0  x0  000000009e877000 x1  0000000000000000
E/TC:0 0  x2  0000000000000000 x3  0000000000000000
E/TC:0 0  x4  0000000000000030 x5  000000009e876d78
E/TC:0 0  x6  00000000fffffff0 x7  00000000ffffffe8
E/TC:0 0  x8  0000000000000008 x9  000000009e89fd00
E/TC:0 0  x10 000000009e884040 x11 0000000000000008
E/TC:0 0  x12 0000000000000020 x13 000000009e89fc70
E/TC:0 0  x14 0000000000000000 x15 0000000000000000
E/TC:0 0  x16 000000009e81c26c x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 000000009e8a0000
E/TC:0 0  x20 000000009e8a0008 x21 000000009e877000
E/TC:0 0  x22 000000009e877000 x23 000000009e877ef0
E/TC:0 0  x24 000000009e876db0 x25 0000000000000000
E/TC:0 0  x26 0000000000000000 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 000000009e89ff90
E/TC:0 0  x30 000000009e816984 elr 000000009e816994
E/TC:0 0  sp_el0 000000009e89ff90
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e816994
E/TC:0 0  0x9e807c88
E/TC:0 0  0x9e821d3c
E/TC:0 0 Panic 'unhandled pageable abort' at /usr/src/debug/optee-os/4.5.0+git/core/arch/arm/kernel/abort.c:582 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e8080fc
E/TC:0 0  0x9e81e7d4
E/TC:0 0  0x9e807854
E/TC:0 0  0x9e804a68

您是否知道如何解决该问题？