[参考译文] PROCESSOR-SDK-AM62X：PSDK 11.00 中发生 OPTEE 错误

admin

Other Parts Discussed in Thread: SYSCONFIG

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

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1532039/processor-sdk-am62x-optee-error-is-occurred-in-psdk-11-00

器件型号：PROCESSOR-SDK-AM62X
主题：SysConfig 中讨论的其他器件

工具/软件：

将 AM62x SDK 从 09.02.01.09 升级到 11.00.09.04 后、OPTEE 中出现错误。

U-Boot SPL 2025.01-00406-gcd91d7360181-dirty (Mar 25 2025 - 16:14:37 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

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 + 0x000727e8 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 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 do_init_calls:22 service_initcall __text_start + 0x00072b50 failed

您能告诉我解决方法吗？

此致、

Koji

4 个月前

0 admin 4 个月前

TI__Guru**** 2422260 points

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

尊敬的 Koji-San：

将 AM62x SDK 从 09.02.01.09 升级到 11.00.09.04 后、OPTEE 中出现错误。

您能否解释一下从 SDK 9.2 更新到 11.0 的具体程度？任何控制台日志或命令序列都会有所帮助。

0 admin 4 个月前

TI__Guru**** 2422260 points

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

您能解释一下如何从 SDK 9.2 更新到 11.0？

1.根据 Yocto 层配置配置了 Yocto 层

2.将 tiboot3 构建为 am62xx-EVM

MACHINE=am62xx-EVM Arago_RT_ENABLE=1 位 bake MC：k3r5：u-boot-ti-staging

3. 为我的定制电路板复制了 am62xx-EVM 源

4. 修改了自定义板的设备树和配置

5. 添加机器作为 am62xx-customboard 并构建 tiboot3.

MACHINE=am62xx-customboard Arago_RT_ENABLE=1 位 bake MC：k3r5：u-boot-ti-staging

此致、

Koji

0 admin 4 个月前

TI__Guru**** 2422260 points

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

我正在将您的疑问发送给我们的 Yocto 专家以获取评论。

0 admin 3 个月前

TI__Guru**** 2422260 points

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

您有任何更新吗？

0 admin 3 个月前

TI__Guru**** 2422260 points

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

Hirohashi-San,

core/arch/arm/plat-k3/drivers/sa2ul.c-  /* Claim the TRNG firewall for ourselves */
core/arch/arm/plat-k3/drivers/sa2ul.c-  ret = ti_sci_change_fwl_owner(fwl_id, rng_region, owner_index,
core/arch/arm/plat-k3/drivers/sa2ul.c-                                &owner_privid, &owner_permission_bits);
core/arch/arm/plat-k3/drivers/sa2ul.c-  if (ret) {
core/arch/arm/plat-k3/drivers/sa2ul.c:          EMSG("Could not change TRNG firewall owner");
core/arch/arm/plat-k3/drivers/sa2ul.c-          return TEE_ERROR_GENERIC;
core/arch/arm/plat-k3/drivers/sa2ul.c-  }

您遇到的错误与 OPTEE 无法与 TIFS 固件通信有关、请参阅上面的 OPTEE 源提取。这可能是 U-Boot（包括固件和器件树文件）或 OPTEE 本身的配置问题、可能与您向 U-Boot 中添加另一个电路板/平台有关、但缺少一些详细信息。

您可以尝试以下操作：

根据 SDK 文档构建过程、在不使用 Yocto 的情况下手动为定制平台构建 U-Boot、包括根据文档中的构建步骤从 SDK 安装程序直接使用预构建的 TIFS、DM、TF-A 和 OPTEE 固件文件。请参阅 https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/11_00_09_04/exports/docs/linux/Foundational_Components /U-Boot/UG-General-Info.html#build-u-boot
若要检查问题是否由 U-Boot 配置引起、请继续为构建 U-Boot am62xx-EVM 使用现有的 Yocto 设置、并比较 U-Boot .config 用于生成的文件 tiboot3.bin 。请注意 tiboot3.bin 是使用 Yocto 中的“multi-config"方法“方法构建的、文件应位于下 arago-tmp-default-BareMetal-k3r5/ 但您似乎已经很清楚这一点。

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

谢谢 Andreas、

我尝试根据构建步骤进行构建。

但是、在 cross_compile=“S_compile_32"执行“执行 make 命令时、会导致错误。

$ export CROSS_COMPILE_64="${SDK_INSTALL_DIR}/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-"
$ export SYSROOT_64="${SDK_INSTALL_DIR}/linux-devkit/sysroots/aarch64-oe-linux"
$ export CC_64="${CROSS_COMPILE_64}gcc --sysroot=${SYSROOT_64}"
$ export CROSS_COMPILE_32="${SDK_INSTALL_DIR}/k3r5-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-oe-eabi/arm-oe-eabi-"

$ export UBOOT_DIR=~/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/
$ export TI_LINUX_FW_DIR=~/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-glibc/work/am62xx_customboard-oe-linux/linux-ti-staging-rt/6.12.17+git/git/
$ export TFA_DIR=~/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-glibc/work/am62xx_customboard-oe-linux/trusted-firmware-a/2.12+git/git/
$ export OPTEE_DIR=~/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-glibc/work/am62xx_customboard-oe-linux/optee-os/4.5.0+git/git/

$ cd $UBOOT_DIR

$ make ARCH=arm CROSS_COMPILE="S_COMPILE_32" am62x_customboard_r5_defconfig O=$UBOOT_DIR/out/r5
make[1]: Entering directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
/bin/sh: line 1: S_COMPILE_32gcc: command not found
  HOSTCC  scripts/basic/fixdep
  GEN     Makefile
  HOSTCC  scripts/kconfig/conf.o
  YACC    scripts/kconfig/zconf.tab.c
  LEX     scripts/kconfig/zconf.lex.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
make[2]: S_COMPILE_32gcc: No such file or directory
make[2]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/scripts/kconfig/Makefile:96: am62x_customboard_r5_defconfig] Error 127
make[1]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/Makefile:586: am62x_customboard_r5_defconfig] Error 2
make[1]: Leaving directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
make: *** [Makefile:177: sub-make] Error 2

通过不带参数执行命令解决了错误、但导致了其他错误。

$ make ARCH=arm am62x_customboard_r5_defconfig O=$UBOOT_DIR/out/r5
make[1]: Entering directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
  HOSTCC  scripts/basic/fixdep
  GEN     Makefile
  HOSTCC  scripts/kconfig/conf.o
  YACC    scripts/kconfig/zconf.tab.c
  LEX     scripts/kconfig/zconf.lex.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
make[1]: Leaving directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'

$ make ARCH=arm O=$UBOOT_DIR/out/r
5 BINMAN_INDIRS=$TI_LINUX_FW_DIR
make[1]: Entering directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
  GEN     Makefile
scripts/kconfig/conf  --syncconfig Kconfig
  UPD     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
  CFG     spl/u-boot.cfg
  GEN     spl/include/autoconf.mk
  UPD     include/config/uboot.release
  Using /home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git as source for U-Boot
  GEN     Makefile
  UPD     include/generated/version_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  UPD     include/generated/dt.h
  ENVC    include/generated/env.txt
  ENVP    include/generated/env.in
cc1: error: bad value ('armv7-r') for '-march=' switch
cc1: note: valid arguments to '-march=' switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids alderlake bonnell atom silvermont slm goldmont goldmont-plus tremont knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 btver1 btver2 native
make[1]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/Makefile:1875: include/generated/env.in] Error 1
make[1]: Leaving directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
make: *** [Makefile:177: sub-make] Error 2

我为 am62xx-EVM 和 am62xx-customboard 连接每个 U-boot.config。

e2e.ti.com/.../evm_2E00_config

e2e.ti.com/.../customboard_2E00_config

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

Hirohashi-San,

但在使用 cross_compile=“S_compile_32"执行“执行 make 命令时导致了错误。

`为 Cortex-R5 MCU 内核构建初始引导二进制文件的正确的 Δ T ake `m参数是make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_32"。根据 https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/11_00_09_04/exports/docs/linux/Foundational_Components /U-Boot/UG-General-Info.html#build-u-boot 上的文档、我不确定您从哪里获得“S_compile_32"？“？

通过不带参数执行命令来解决该错误、但引起了其他错误。

对于交叉编译 U-Boot（和 Linux 内核）、两者`arch=...` 和`cross_compile =……` make 变量赋值是必需的。如果保留交叉编译设置、它将尝试使用无效的主机编译器。

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

抱歉。我似乎有误读。

我尝试了以下命令、但仍然存在错误。

$ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_32" am62x_customboard_r5_defconfig O=$UBOOT_DIR/out/r5
make[1]: Entering directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
/bin/sh: line 1: /k3r5-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-oe-eabi/arm-oe-eabi-gcc: No such file or directory
  HOSTCC  scripts/basic/fixdep
  GEN     Makefile
  HOSTCC  scripts/kconfig/conf.o
  YACC    scripts/kconfig/zconf.tab.c
  LEX     scripts/kconfig/zconf.lex.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
make[2]: /k3r5-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-oe-eabi/arm-oe-eabi-gcc: No such file or directory
make[2]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/scripts/kconfig/Makefile:96: am62x_customboard_r5_defconfig] Error 127
make[1]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/Makefile:586: am62x_customboard_r5_defconfig] Error 2
make[1]: Leaving directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
make: *** [Makefile:177: sub-make] Error 2

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Koji-San：

您可以从错误消息（第 11 行）中看到无法找到交叉编译器。这可能是因为 CROSS_COMPILE_32 变量设置不正确。如果您查看文档中的步骤...

host# export cross_compile_32=“$｛SDK_INSTALL_DIR｝/k3r5-Devkit/sysroots/x86_64-arago-linux/usr/bin/arm-oe-eabi/arm-oe-eabi-“

你需要替换 $｛SDK_INSTALL_DIR｝ 以及实际 SDK 安装位置的路径 CROSS_COMPILE_32 变有效。

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

[报价 userid=“4452" url="“ url="~“~/support/processors-group/processors/f/processors-forum/1532039/processor-sdk-am62x-optee-error-is-occurred-in-psdk-11-00/5904481 #5904481“].您需要替换 $｛SDK_INSTALL_DIR｝ 以及实际 SDK 安装位置的路径 CROSS_COMPILE_32 变量有效。

由于 SDK 安装目录中不存在 cross_compile_32 路径、因此失败。

/home/tisdk/k3r5-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-oe-eabi/arm-oe-eabi-gcc: No such file or directory

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

失败、因为 SDK 安装目录中不存在 cross_compile_32 路径。

您的路径似乎仍然错误。

尝试找出您的二进制文件的位置,然后调整路径以使其匹配。

$ find /home -name arm-oe-eabi-gcc

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

我找到了每个正确的路径并尝试构建。

已解决上述错误、但导致 gnutls 错误。

$ make make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_32" O=$UBOOT_DIR/out/r5 BINMAN_INDIRS=$TI_LINUX_FW_DIR
make[1]: Entering directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
  GEN     Makefile
scripts/kconfig/conf  --syncconfig Kconfig
  UPD     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
  CFG     spl/u-boot.cfg
  GEN     spl/include/autoconf.mk
  UPD     include/config/uboot.release
  Using /home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git as source for U-Boot
  GEN     Makefile
  UPD     include/generated/version_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  UPD     include/generated/dt.h
  ENVC    include/generated/env.txt
  ENVP    include/generated/env.in
  ENVT    include/generated/environment.h
  CC      lib/asm-offsets.s
  UPD     include/generated/generic-asm-offsets.h
  CC      arch/arm/lib/asm-offsets.s
  UPD     include/generated/asm-offsets.h
  SHIPPED scripts/dtc/pylibfdt/libfdt.i
  PYMOD   rebuild
  HOSTCC  scripts/dtc/dtc.o
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/fstree.o
  HOSTCC  scripts/dtc/data.o
  HOSTCC  scripts/dtc/livetree.o
  HOSTCC  scripts/dtc/treesource.o
  HOSTCC  scripts/dtc/srcpos.o
  HOSTCC  scripts/dtc/checks.o
  HOSTCC  scripts/dtc/util.o
  LEX     scripts/dtc/dtc-lexer.lex.c
  YACC    scripts/dtc/dtc-parser.tab.h
  HOSTCC  scripts/dtc/dtc-lexer.lex.o
  YACC    scripts/dtc/dtc-parser.tab.c
  HOSTCC  scripts/dtc/dtc-parser.tab.o
  HOSTLD  scripts/dtc/dtc
  HOSTCC  tools/gen_eth_addr
  HOSTCC  tools/gen_ethaddr_crc.o
  WRAP    tools/generated/lib/crc8.c
  HOSTCC  tools/generated/lib/crc8.o
  HOSTLD  tools/gen_ethaddr_crc
  HOSTCC  tools/img2srec
  HOSTCC  tools/mkenvimage.o
  HOSTCC  tools/os_support.o
  WRAP    tools/generated/lib/crc32.c
  HOSTCC  tools/generated/lib/crc32.o
  HOSTLD  tools/mkenvimage
  HOSTCC  tools/aisimage.o
  HOSTCC  tools/atmelimage.o
  HOSTCC  tools/fit_common.o
  HOSTCC  tools/fit_image.o
  HOSTCC  tools/image-host.o
  WRAP    tools/generated/boot/image-fit.c
  HOSTCC  tools/generated/boot/image-fit.o
  HOSTCC  tools/image-sig-host.o
  WRAP    tools/generated/boot/image-fit-sig.c
  HOSTCC  tools/generated/boot/image-fit-sig.o
  WRAP    tools/generated/boot/image-cipher.c
  HOSTCC  tools/generated/boot/image-cipher.o
  WRAP    tools/generated/boot/fdt_region.c
  HOSTCC  tools/generated/boot/fdt_region.o
  WRAP    tools/generated/boot/bootm.c
  HOSTCC  tools/generated/boot/bootm.o
  HOSTCC  tools/default_image.o
  WRAP    tools/generated/lib/fdtdec_common.c
  HOSTCC  tools/generated/lib/fdtdec_common.o
  WRAP    tools/generated/lib/fdtdec.c
  HOSTCC  tools/generated/lib/fdtdec.o
  WRAP    tools/generated/boot/image.c
  HOSTCC  tools/generated/boot/image.o
  WRAP    tools/generated/boot/image-host.c
  HOSTCC  tools/generated/boot/image-host.o
  HOSTCC  tools/imagetool.o
  HOSTCC  tools/imximage.o
  HOSTCC  tools/imx8image.o
  HOSTCC  tools/imx8mimage.o
  HOSTCC  tools/kwbimage.o
  WRAP    tools/generated/lib/md5.c
  HOSTCC  tools/generated/lib/md5.o
  HOSTCC  tools/lpc32xximage.o
  HOSTCC  tools/mxsimage.o
  HOSTCC  tools/omapimage.o
  HOSTCC  tools/pblimage.o
  HOSTCC  tools/pbl_crc32.o
  HOSTCC  tools/renesas_spkgimage.o
  HOSTCC  tools/sfspl.o
  HOSTCC  tools/vybridimage.o
  HOSTCC  tools/stm32image.o
  WRAP    tools/generated/lib/rc4.c
  HOSTCC  tools/generated/lib/rc4.o
  HOSTCC  tools/rkcommon.o
  HOSTCC  tools/rkimage.o
  HOSTCC  tools/rksd.o
  HOSTCC  tools/rkspi.o
  HOSTCC  tools/socfpgaimage.o
  HOSTCC  tools/sunxi_egon.o
  WRAP    tools/generated/lib/crc16-ccitt.c
  HOSTCC  tools/generated/lib/crc16-ccitt.o
  WRAP    tools/generated/lib/hash-checksum.c
  HOSTCC  tools/generated/lib/hash-checksum.o
  WRAP    tools/generated/lib/sha1.c
  HOSTCC  tools/generated/lib/sha1.o
  WRAP    tools/generated/lib/sha256.c
  HOSTCC  tools/generated/lib/sha256.o
  WRAP    tools/generated/lib/sha512.c
  HOSTCC  tools/generated/lib/sha512.o
  WRAP    tools/generated/common/hash.c
  HOSTCC  tools/generated/common/hash.o
  HOSTCC  tools/ublimage.o
  HOSTCC  tools/zynqimage.o
  HOSTCC  tools/zynqmpimage.o
  HOSTCC  tools/zynqmpbif.o
  WRAP    tools/generated/lib/fdt-libcrypto.c
  HOSTCC  tools/generated/lib/fdt-libcrypto.o
  HOSTCC  tools/sunxi_toc0.o
  HOSTCC  tools/libfdt/fdt.o
  HOSTCC  tools/libfdt/fdt_ro.o
  HOSTCC  tools/libfdt/fdt_wip.o
  HOSTCC  tools/libfdt/fdt_sw.o
  HOSTCC  tools/libfdt/fdt_rw.o
  HOSTCC  tools/libfdt/fdt_strerror.o
  HOSTCC  tools/libfdt/fdt_empty_tree.o
  HOSTCC  tools/libfdt/fdt_addresses.o
  HOSTCC  tools/libfdt/fdt_overlay.o
  HOSTCC  tools/gpimage.o
  HOSTCC  tools/gpimage-common.o
  HOSTCC  tools/mtk_image.o
  HOSTCC  tools/mtk_nand_headers.o
  WRAP    tools/generated/lib/ecdsa/ecdsa-libcrypto.c
  HOSTCC  tools/generated/lib/ecdsa/ecdsa-libcrypto.o
  WRAP    tools/generated/lib/rsa/rsa-sign.c
  HOSTCC  tools/generated/lib/rsa/rsa-sign.o
  WRAP    tools/generated/lib/rsa/rsa-verify.c
  HOSTCC  tools/generated/lib/rsa/rsa-verify.o
  WRAP    tools/generated/lib/rsa/rsa-mod-exp.c
  HOSTCC  tools/generated/lib/rsa/rsa-mod-exp.o
  WRAP    tools/generated/lib/aes/aes-encrypt.c
  HOSTCC  tools/generated/lib/aes/aes-encrypt.o
  WRAP    tools/generated/lib/aes/aes-decrypt.c
  HOSTCC  tools/generated/lib/aes/aes-decrypt.o
  HOSTCC  tools/dumpimage.o
  HOSTLD  tools/dumpimage
  HOSTCC  tools/mkimage.o
  HOSTLD  tools/mkimage
  HOSTCC  tools/fit_info.o
  HOSTLD  tools/fit_info
  HOSTCC  tools/fit_check_sign.o
  HOSTLD  tools/fit_check_sign
  HOSTCC  tools/fdt_add_pubkey.o
  HOSTLD  tools/fdt_add_pubkey
  HOSTCC  tools/proftool.o
  WRAP    tools/generated/lib/abuf.c
  HOSTCC  tools/generated/lib/abuf.o
  HOSTLD  tools/proftool
  HOSTCC  tools/fdtgrep.o
  HOSTLD  tools/fdtgrep
  HOSTCC  tools/spl_size_limit
  WRAP    tools/generated/lib/uuid.c
  HOSTCC  tools/generated/lib/uuid.o
  HOSTCC  tools/mkeficapsule.o
/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/tools/mkeficapsule.c:20:10: fatal error: gnutls/gnutls.h: No such file or directory
   20 | #include <gnutls/gnutls.h>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.host:112: tools/mkeficapsule.o] Error 1
make[1]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/Makefile:1916: tools] Error 2
make[1]: Leaving directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
make: *** [Makefile:177: sub-make] Error 2

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

gnutls 错误已解决,以引用以下论坛。

AM62L-PROCESSOR-SDK：构建 u-boot 错误 gnutls/gnutls.h

我附加构建 u-boot 的当前状态。

$ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_32" O=$UBOOT_DIR/out/r5 BINMAN_INDIRS=$TI_LINUX_FW_DIR
make[1]: Entering directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
  GEN     Makefile
scripts/kconfig/conf  --syncconfig Kconfig
  UPD     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
  CFG     spl/u-boot.cfg
  GEN     spl/include/autoconf.mk
  UPD     include/config/uboot.release
  Using /home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git as source for U-Boot
  GEN     Makefile
  UPD     include/generated/version_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  UPD     include/generated/dt.h
  ENVC    include/generated/env.txt
  ENVP    include/generated/env.in
  ENVT    include/generated/environment.h
  CC      lib/asm-offsets.s
  UPD     include/generated/generic-asm-offsets.h
  CC      arch/arm/lib/asm-offsets.s
  UPD     include/generated/asm-offsets.h
  SHIPPED scripts/dtc/pylibfdt/libfdt.i
  PYMOD   rebuild
  HOSTCC  scripts/dtc/dtc.o
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/fstree.o
  HOSTCC  scripts/dtc/data.o
  HOSTCC  scripts/dtc/livetree.o
  HOSTCC  scripts/dtc/treesource.o
  HOSTCC  scripts/dtc/srcpos.o
  HOSTCC  scripts/dtc/checks.o
  HOSTCC  scripts/dtc/util.o
  LEX     scripts/dtc/dtc-lexer.lex.c
  YACC    scripts/dtc/dtc-parser.tab.h
  HOSTCC  scripts/dtc/dtc-lexer.lex.o
  YACC    scripts/dtc/dtc-parser.tab.c
  HOSTCC  scripts/dtc/dtc-parser.tab.o
  HOSTLD  scripts/dtc/dtc
  HOSTCC  tools/gen_eth_addr
  HOSTCC  tools/gen_ethaddr_crc.o
  WRAP    tools/generated/lib/crc8.c
  HOSTCC  tools/generated/lib/crc8.o
  HOSTLD  tools/gen_ethaddr_crc
  HOSTCC  tools/img2srec
  HOSTCC  tools/mkenvimage.o
  HOSTCC  tools/os_support.o
  WRAP    tools/generated/lib/crc32.c
  HOSTCC  tools/generated/lib/crc32.o
  HOSTLD  tools/mkenvimage
  HOSTCC  tools/aisimage.o
  HOSTCC  tools/atmelimage.o
  HOSTCC  tools/fit_common.o
  HOSTCC  tools/fit_image.o
  HOSTCC  tools/image-host.o
  WRAP    tools/generated/boot/image-fit.c
  HOSTCC  tools/generated/boot/image-fit.o
  HOSTCC  tools/image-sig-host.o
  WRAP    tools/generated/boot/image-fit-sig.c
  HOSTCC  tools/generated/boot/image-fit-sig.o
  WRAP    tools/generated/boot/image-cipher.c
  HOSTCC  tools/generated/boot/image-cipher.o
  WRAP    tools/generated/boot/fdt_region.c
  HOSTCC  tools/generated/boot/fdt_region.o
  WRAP    tools/generated/boot/bootm.c
  HOSTCC  tools/generated/boot/bootm.o
  HOSTCC  tools/default_image.o
  WRAP    tools/generated/lib/fdtdec_common.c
  HOSTCC  tools/generated/lib/fdtdec_common.o
  WRAP    tools/generated/lib/fdtdec.c
  HOSTCC  tools/generated/lib/fdtdec.o
  WRAP    tools/generated/boot/image.c
  HOSTCC  tools/generated/boot/image.o
  WRAP    tools/generated/boot/image-host.c
  HOSTCC  tools/generated/boot/image-host.o
  HOSTCC  tools/imagetool.o
  HOSTCC  tools/imximage.o
  HOSTCC  tools/imx8image.o
  HOSTCC  tools/imx8mimage.o
  HOSTCC  tools/kwbimage.o
  WRAP    tools/generated/lib/md5.c
  HOSTCC  tools/generated/lib/md5.o
  HOSTCC  tools/lpc32xximage.o
  HOSTCC  tools/mxsimage.o
  HOSTCC  tools/omapimage.o
  HOSTCC  tools/pblimage.o
  HOSTCC  tools/pbl_crc32.o
  HOSTCC  tools/renesas_spkgimage.o
  HOSTCC  tools/sfspl.o
  HOSTCC  tools/vybridimage.o
  HOSTCC  tools/stm32image.o
  WRAP    tools/generated/lib/rc4.c
  HOSTCC  tools/generated/lib/rc4.o
  HOSTCC  tools/rkcommon.o
  HOSTCC  tools/rkimage.o
  HOSTCC  tools/rksd.o
  HOSTCC  tools/rkspi.o
  HOSTCC  tools/socfpgaimage.o
  HOSTCC  tools/sunxi_egon.o
  WRAP    tools/generated/lib/crc16-ccitt.c
  HOSTCC  tools/generated/lib/crc16-ccitt.o
  WRAP    tools/generated/lib/hash-checksum.c
  HOSTCC  tools/generated/lib/hash-checksum.o
  WRAP    tools/generated/lib/sha1.c
  HOSTCC  tools/generated/lib/sha1.o
  WRAP    tools/generated/lib/sha256.c
  HOSTCC  tools/generated/lib/sha256.o
  WRAP    tools/generated/lib/sha512.c
  HOSTCC  tools/generated/lib/sha512.o
  WRAP    tools/generated/common/hash.c
  HOSTCC  tools/generated/common/hash.o
  HOSTCC  tools/ublimage.o
  HOSTCC  tools/zynqimage.o
  HOSTCC  tools/zynqmpimage.o
  HOSTCC  tools/zynqmpbif.o
  WRAP    tools/generated/lib/fdt-libcrypto.c
  HOSTCC  tools/generated/lib/fdt-libcrypto.o
  HOSTCC  tools/sunxi_toc0.o
  HOSTCC  tools/libfdt/fdt.o
  HOSTCC  tools/libfdt/fdt_ro.o
  HOSTCC  tools/libfdt/fdt_wip.o
  HOSTCC  tools/libfdt/fdt_sw.o
  HOSTCC  tools/libfdt/fdt_rw.o
  HOSTCC  tools/libfdt/fdt_strerror.o
  HOSTCC  tools/libfdt/fdt_empty_tree.o
  HOSTCC  tools/libfdt/fdt_addresses.o
  HOSTCC  tools/libfdt/fdt_overlay.o
  HOSTCC  tools/gpimage.o
  HOSTCC  tools/gpimage-common.o
  HOSTCC  tools/mtk_image.o
  HOSTCC  tools/mtk_nand_headers.o
  WRAP    tools/generated/lib/ecdsa/ecdsa-libcrypto.c
  HOSTCC  tools/generated/lib/ecdsa/ecdsa-libcrypto.o
  WRAP    tools/generated/lib/rsa/rsa-sign.c
  HOSTCC  tools/generated/lib/rsa/rsa-sign.o
  WRAP    tools/generated/lib/rsa/rsa-verify.c
  HOSTCC  tools/generated/lib/rsa/rsa-verify.o
  WRAP    tools/generated/lib/rsa/rsa-mod-exp.c
  HOSTCC  tools/generated/lib/rsa/rsa-mod-exp.o
  WRAP    tools/generated/lib/aes/aes-encrypt.c
  HOSTCC  tools/generated/lib/aes/aes-encrypt.o
  WRAP    tools/generated/lib/aes/aes-decrypt.c
  HOSTCC  tools/generated/lib/aes/aes-decrypt.o
  HOSTCC  tools/dumpimage.o
  HOSTLD  tools/dumpimage
  HOSTCC  tools/mkimage.o
  HOSTLD  tools/mkimage
  HOSTCC  tools/fit_info.o
  HOSTLD  tools/fit_info
  HOSTCC  tools/fit_check_sign.o
  HOSTLD  tools/fit_check_sign
  HOSTCC  tools/fdt_add_pubkey.o
  HOSTLD  tools/fdt_add_pubkey
  HOSTCC  tools/proftool.o
  WRAP    tools/generated/lib/abuf.c
  HOSTCC  tools/generated/lib/abuf.o
  HOSTLD  tools/proftool
  HOSTCC  tools/fdtgrep.o
  HOSTLD  tools/fdtgrep
  HOSTCC  tools/spl_size_limit
  WRAP    tools/generated/lib/uuid.c
  HOSTCC  tools/generated/lib/uuid.o
  HOSTCC  tools/mkeficapsule.o
  HOSTLD  tools/mkeficapsule
  AR      arch/arm/cpu/built-in.o
  CC      arch/arm/cpu/armv7/cache_v7.o
Assembler messages:
Fatal error: invalid -march= option: `armv7-r'
make[2]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/scripts/Makefile.build:257: arch/arm/cpu/armv7/cache_v7.o] Error 2
make[1]: *** [/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/Makefile:1916: arch/arm/cpu/armv7] Error 2
make[1]: Leaving directory '/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/work/am62xx_customboard_k3r5-oe-eabi/u-boot-ti-staging/2025.01+git/git/out/r5'
make: *** [Makefile:177: sub-make] Error 2

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

您的位置 CROSS_COMPILE_32 ENV 变量指向？错误消息“Fatal error: invalid -march= option:`armv7-r'“表明它不指向 R5 内核所需的 BareMetal 工具链。

$ echo $CROSS_COMPILE_32

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

您的位置 CROSS_COMPILE_32 ENV 变量指向？

$ echo $cross_compile_32
/home/tisdk/am62xx-tisdk-11.00.09.04/build/arago-tmp-default-baremetal-k3r5/sysroots-components/x86_64/gcc-cross-arm/usr/libexec/arm-oe-eabi/gcc/arm-oe-eabi/13.3.0/arm-oe-eabi-

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

您有任何更新吗？

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

我已禁用 ATF 控制台、因此尝试在启用 ATF 控制台的情况下启动。

因此、我发现 ATF 中已经出现了错误。

U-Boot SPL 2025.01-00406-gcd91d7360181-dirty (Mar 25 2025 - 16:14:37 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.12.0(debug):11.00.09-dirty
NOTICE:  BL31: Built : 12:35:58, Mar 24 2025
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    Maximum SPI INTID supported: 287
INFO:    SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
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)
WARNING: Unable to take system power reference
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
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)
INFO:    BL31: Initializing BL32
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 + 0x000727e8 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 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 do_init_calls:22 service_initcall __text_start + 0x00072b50 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)

它在旧 PSDK 文档中按如下方式编写。

4.1.12.7.故障排除

是同一个问题吗？

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

Koji-San、

[引述 userid=“582335" url="“ url="~“~/support/processors-group/processors/f/processors-forum/1532039/processor-sdk-am62x-optee-error-is-occurred-in-psdk-11-00/5923901

因此、已尝试在启用 ATF 控制台启动。

因此、我发现 ATF 中已经出现了错误。

[/报价]

很棒的体验！

[引述 userid=“582335" url="“ url="~“~/support/processors-group/processors/f/processors-forum/1532039/processor-sdk-am62x-optee-error-is-occurred-in-psdk-11-00/5923901

它在旧 PSDK 文档中按如下方式编写。

4.1.12.7.故障排除

是同一个问题吗？

[/报价]

是的、这就是它的样子。我们应该通过设备管理器进一步调查潜在问题。

您`检查生成的 μ s tispl.bin` U-Boot SPL (A53) 映像中是否包含设备管理器 (DM) 固件二进制文件？该映像是适合的 blob、您可以使用`dtc`工具进行反向编译、如下所示：

$ dtc -I dtb tispl.bin | cut -b -80 -
/dts-v1/;

/ {
        timestamp = <0x6749a882>;
        #address-cells = <0x01>;
        description = "Configuration to load ATF and SPL";

        images {

                atf {
                        entry = <0x80000000>;
                        load = <0x80000000>;
                        os = "arm-trusted-firmware";
                        compression = "none";
                        arch = "arm64";
                        type = "firmware";
                        description = "ARM Trusted Firmware";
                        data = <0x308206a0 0x30820488 0xa0030201 0x2021459 0xb15c8522 0x7503e361 0xd5
                };

                tee {
                        entry = <0x9e800000>;
                        load = <0x9e800000>;
                        os = "tee";
                        compression = "none";
                        arch = "arm64";
                        type = "tee";
                        description = "OP-TEE";
                        data = <0x308206a0 0x30820488 0xa0030201 0x2021410 0x63d2fe65 0x95e9768b 0xe7
                };

                dm {
                        entry = <0x89000000>;
                        load = <0x89000000>;
                        os = "DM";
                        compression = "none";
                        arch = "arm32";
                        type = "firmware";
                        description = "DM binary";
                        data = <0x308206a0 0x30820488 0xa0030201 0x202144c 0x3479f19c 0x3f30357d 0x99
                };

                spl {
                        entry = <0x80080000>;
                        load = <0x80080000>;
                        compression = "none";
                        arch = "arm64";
                        os = "U-Boot";
                        type = "standalone";
                        description = "SPL (64-bit)";
                        data = <0x308206a0 0x30820488 0xa0030201 0x202141f 0xbbe238b7 0xb0eec063 0x13
                };
<...snip...>

在我生成的示例中、您会看到一个`dm｛`元件、它具有一个活跃的非空的`data =`属性（包含 DM 固件二进制文件）。如果您看到这样一个列出了十六进制值的`data =`属性、这意味着 DM 固件是您构建的一部分（但可能是其固件版本不正确，这就是它失败的原因？）。 `dμ V ata =`μ V 属性为空、则由于某种原因、U-Boot SPL (A53) 是在没有所需 DM 固件的情况下构建的、我们需要检查这方面的情况。

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

感谢您的答复。

您能否检查生成的`tispl.bin` U-Boot SPL (A53) 映像中是否包含设备管理器 (DM) 固件二进制文件？ [/报价]

我附加执行 DTC 命令的结果。

dm 数据属性不为空。

$ dtc -I dtb tispl.bin | cut -b -80 -
/dts-v1/;

/ {
        timestamp = <0x67e2d66d>;
        #address-cells = <0x01>;
        description = "Configuration to load ATF and SPL";

        images {

                atf {
                        entry = <0x80000000>;
                        load = <0x80000000>;
                        os = "arm-trusted-firmware";
                        compression = "none";
                        arch = "arm64";
                        type = "firmware";
                        description = "ARM Trusted Firmware";
                        data = <0x308206a0 0x30820488 0xa0030201 0x202146a 0x7d8926ca 0xb5e55fd0 0x81
                };

                tee {
                        entry = <0x9e800000>;
                        load = <0x9e800000>;
                        os = "tee";
                        compression = "none";
                        arch = "arm64";
                        type = "tee";
                        description = "OP-TEE";
                        data = <0x308206a0 0x30820488 0xa0030201 0x2021472 0x57a2fb75 0x80ff54d7 0x8f
                };

                dm {
                        entry = <0x89000000>;
                        load = <0x89000000>;
                        os = "DM";
                        compression = "none";
                        arch = "arm32";
                        type = "firmware";
                        description = "DM binary";
                        data = <0x308206a0 0x30820488 0xa0030201 0x2021460 0xf1f44c7 0x8839b21c 0x8db
                };

                spl {
                        entry = <0x80080000>;
                        load = <0x80080000>;
                        compression = "none";
                        arch = "arm64";
                        os = "U-Boot";
                        type = "standalone";
                        description = "SPL (64-bit)";
                        data = <0x308206a0 0x30820488 0xa0030201 0x2021475 0xc0a03817 0x6eac3a4 0x661
                };

                tifsstub-hs {
                        entry = <0x9dc00000>;
                        load = <0x9dc00000>;
                        os = "tifsstub-hs";
                        compression = "none";
                        arch = "arm32";
                        type = "firmware";
                        description = "TIFSSTUB";
                        data = [30 82 06 ce 30 82 04 b6 a0 03 02 01 02 02 14 49 b3 0f 9b 3a 38 e8 e5
                };

                tifsstub-fs {
                        entry = <0x9dc00000>;
                        load = <0x9dc00000>;
                        os = "tifsstub-fs";
                        compression = "none";
                        arch = "arm32";
                        type = "firmware";
                        description = "TIFSSTUB";
                        data = [30 82 06 8f 30 82 04 77 a0 03 02 01 02 02 09 00 90 6d 16 70 4d 05 fa
                };

                tifsstub-gp {
                        entry = <0x9dc00000>;
                        load = <0x9dc00000>;
                        os = "tifsstub-gp";
                        compression = "none";
                        arch = "arm32";
                        type = "firmware";
                        description = "TIFSSTUB";
                        data = [30 82 03 c7 30 82 03 30 a0 03 02 01 02 02 14 20 b9 97 89 ea 87 06 e3
                };

                fdt-0 {
                        compression = "none";
                        arch = "arm";
                        type = "flat_dt";
                        description = "k3-am625-customboard";
                        data = [30 82 06 9f 30 82 04 87 a0 03 02 01 02 02 14 73 e1 ae c5 14 44 54 e1
                };
        };

        configurations {
                default = "conf-0";

                conf-0 {
                        description = "k3-am625-customboard";
                        firmware = "atf";
                        loadables = "tee\0tifsstub-hs\0tifsstub-fs\0tifsstub-gp\0dm\0spl";
                        fdt = "fdt-0";
                };
        };
};

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

Koji-San、

[引述 userid=“582335" url="“ url="~“~/support/processors-group/processors/f/processors-forum/1532039/processor-sdk-am62x-optee-error-is-occurred-in-psdk-11-00/5931608

我附加执行 DTC 命令的结果。

dm 数据属性不为空。

[/报价]

这是一个很好的起点。我们需要验证 DM 固件是否正常运行。

您使用的是定制板、对吧？您是否可以使用 JTAG 连接到“Cortex R5“主代码、看看它在做什么？当 TF-A 启动时、此内核应专用于运行设备管理器 (DM) 固件和 TIFS 存根。因此、如果您像所附屏幕截图中那样连接到内核、并查看 个人计算机 和反汇编、它应该从任一位置执行 0x89000000 地址范围（如果正在执行 DM 固件功能）、或来自 0x9dc00000 地址范围（如果内核正在执行 TIFS 存根固件中的代码）。并且汇编指令看起来应该是有效的。

似乎有一些问题可能会干扰设备管理器 (DM) 固件的正常启动或运行。

您对 U-Boot SPL (R5) 进行了哪些自定义？

谢谢。此致、
Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

当我使用 PSDK 09.02.01.09 时、我替换了 DMFW 以禁用 WKUP 控制台。

我使用了与之前 PSDK 相同的 DMFW。

我将 DMFW 恢复为原始格式 ipc_echo_testb_mcu1_0_release_strip.xer5f、并成功引导。

不能使用 MCUSDK.09.02.00.24 与 PSDK 11.00.09.04 构建的 DMFW？

我要禁用 WKUP 控制台。

此致、

Koji

0 admin 3 个月前

TI__Guru**** 2422260 points

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

Koji-San \、

[引述 userid=“582335" url="“ url="~“~/support/processors-group/processors/f/processors-forum/1532039/processor-sdk-am62x-optee-error-is-occurred-in-psdk-11-00/5940953

当我使用 PSDK 09.02.01.09 时、我替换了 DMFW 以禁用 WKUP 控制台。

我使用了与之前 PSDK 相同的 DMFW。

我将 DMFW 恢复为原始格式 ipc_echo_testb_mcu1_0_release_strip.xer5f、并成功引导。

不能使用 MCUSDK.09.02.00.24 与 PSDK 11.00.09.04 构建的 DMFW？

[/报价]

啊、好的、现在这解释了事情。至于器件固件、您必须始终从相同的 SDK 级别同步所有固件版本、包括设备管理器 (DM) 固件（“ipc_echo_testb_mcu1_0_release_strip.xer5")“）、TIFS、TIFS-stub、TF-A、OPTEE、以及 U-Boot 和内核驱动程序等所有这些都相互依赖、有时会进行 API 更改（如 TISCI 通信协议示例）或介绍其他关键更改（例如，SDK v10.0+中的 DM 固件包含关键的 PLL 修复、而 SDK v9.x DM 固件中不存在）、所有这些都需要满足这些依赖项。

您应该根据当前关联的 MCU+ SDK 源重新构建新的器件管理器固件以供使用。另请注意、我们现已提供 MCU+ SDK v11.1 和 Linux SDK v11.1、这些版本已在 7 月 15 日发布、因此如果您当前更新软件栈、应考虑使用这些最新的 SDK。

我想禁用 WKUP 控制台。

您可以通过对 MCU+ SDK 中相应固件工程的 SysConfig 更改来完成此操作。

此致、Andreas

0 admin 3 个月前

TI__Guru**** 2422260 points

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

尊敬的 Andreas：

我了解同步的需求。

感谢您的支持。

此致、

Koji

处理器（参考译文帖）

处理器（参考译文帖）(Read Only)

[参考译文] PROCESSOR-SDK-AM62X：PSDK 11.00 中发生 OPTEE 错误