[参考译文] TDA4VM：嵌入在 tispl.bin 中的 R5f MCU1_0内核的 CDD_IPC FW 出现 SPL 启动错误

admin

请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1295238/tda4vm-spl-startup-error-with-cdd_ipc-fw-for-r5f-mcu1_0-core-embeded-in-tispl-bin

器件型号：TDA4VM

您好！

在`将` tispl.bin `中嵌入的默认演示应用程序替换为 SDK 8.6中的另一个固件(ti-processor-sdk-rtos-j721e-evm-08_06_01_03)时、我们面临一些问题、例如从 mcusw 演示版本编译的` cdd_ipc_profiling (编译为在 mcu1_0中运行)。生成的`cdd_ipc_profile_app_freertos_mcu1_0_release_strip.xer5f`、根据 RTOS SDK 中`mcusw`文件夹内的文档指南进行编译。

从 Linux SDK 8.6 (ti-processor-sdk-linux-j7-evm-08_06_01_02)生成 u-boot 后、我们在 DFU 中设置引导模式并传递生成的映像、在加载新的`tispl.bin`后获取以下输出：

init_env from device 18 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 15:40:55, May  2 2023
I/TC:
I/TC: OP-TEE version: 3.20.0 (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Tue May  2 15:41:00 UTC 2023 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: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.3--v08.06.03 (Chill Capybar')
I/TC: HUK Initialized
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_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:59 Failed to get SA2UL device
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00063c20 failed
I/TC: Primary CPU switching to normal world boot
E/TC:0 0
E/TC:0 0 Core data-abort at address 0x10 (translation fault)
E/TC:0 0  esr 0x96000005  ttbr0 0x9e894000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x800003c4
E/TC:0 0  x0  000000009e867000 x1  0000000000000010
E/TC:0 0  x2  0000000000000000 x3  0000000000000000
E/TC:0 0  x4  0000000000000001 x5  0000000000ffffff
E/TC:0 0  x6  0000000000000002 x7  000000009e89c190
E/TC:0 0  x8  000000009e89c190 x9  000000009e884d70
E/TC:0 0  x10 0000000000000000 x11 0000000000000000
E/TC:0 0  x12 000000009e89c100 x13 000000000000000a
E/TC:0 0  x14 00000000ffffffff x15 0000000000000020
E/TC:0 0  x16 000000009e813c40 x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 000000009e89eca0
E/TC:0 0  x20 000000009e89eca8 x21 0000000000000007
E/TC:0 0  x22 000000009e873000 x23 000000009e8736a0
E/TC:0 0  x24 0000000100000000 x25 0000000000000000
E/TC:0 0  x26 0000000000000000 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 000000009e89ec30
E/TC:0 0  x30 000000009e80e3ac elr 000000009e80e3cc
E/TC:0 0  sp_el0 000000009e89ec30
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e80e3cc
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:572 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e8087dc
E/TC:0 0  0x9e81506c
E/TC:0 0  0x9e807fd8
E/TC:0 0  0x9e805520

我们是否需要执行任何额外步骤来使 MCU 岛与主域 A72 (QNX 7.1)之间进行引导？

非常感谢

2 年多前