PROCESSOR-SDK-AM64X: SDK 09.02.01.10: error when compiling OP-TEE

Benjamin Limmer

Prodigy 70 points

Part Number: PROCESSOR-SDK-AM64X
Other Parts Discussed in Thread: SK-AM64B

Tool/software:

I am trying to get the MCU+ example "SBL OSPI Linux" working on the SK-AM64B board.

To do this, I have to re-build OP-TEE.

Unfortunately, when trying to compile OP-TEE as described here

https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/09_02_01_10/exports/docs/linux/Foundational_Components_OPTEE.html

I get the following error:

...@...:~/ti/ubootsources/optee_os$ make CROSS_COMPILE="$CROSS_COMPILE_32" CROSS_COMPILE64="$CROSS_COMPILE_64" PLATFORM=k3-am64x CFG_ARM64_core=y
  CHK     out/arm-plat-k3/conf.mk
  CHK     out/arm-plat-k3/include/generated/conf.h
  CHK     out/arm-plat-k3/core/include/generated/asm-defines.h
  LD      out/arm-plat-k3/ldelf/ldelf.elf
/home/.../ti/ti-processor-sdk-linux-am64xx-evm-09.02.01.10//linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf] Error 1

I use the recommended toolchain setup as described here:

https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/09_02_01_10/exports/docs/linux/Overview/GCC_ToolChain.html#yocto-toolchain

Regards,

Benjamin

over 1 year ago

0 Yogesh Siraswar over 1 year ago

TI__Mastermind 21125 points

Hi Benjamin,

I tested on my machine and I am able to build.

Few questions:

1) What the Ubuntu version on the host machine?

2) Could you please try with arm tool chain setup@https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/09_02_01_10/exports/docs/linux/Overview/GCC_ToolChain.html#arm-toolchains

Thanks

Yogesh

+1 Benjamin Limmer over 1 year ago in reply to Yogesh Siraswar

Prodigy 70 points

Hi Yogesh,

1) I am using Ubuntu 22.04., as recommended.

2) I seems to work with the ARM toolchain. That does not really solve my problem though. The Linux appimage created with this OP-TEE image does not start correctly on my board. So I really want to use the "strongly recommended" way to build to minimize error sources.

Is it possible that there is an error in the SDK build tools?
I seem to have the same problem as described in this thread:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1371051/am625-op-tee-build-fail-sdk9-2

Regards,

Benjamin

0 Yogesh Siraswar over 1 year ago in reply to Benjamin Limmer

TI__Mastermind 21125 points

Benjamin,

Strongly recommended doesn't mean you cannot use external tool chain as long as version are the same. As stated in the above thread, the issue is being tracked with internal tool Chain and will be resolved in the next release.

Are you using signed optee image for linuxappimage? Kindly share the log to debug this further.

Thanks

Yogesh

0 Benjamin Limmer over 1 year ago in reply to Yogesh Siraswar

Prodigy 70 points

Hi Yogesh,

I am building OP-TEE as described here

https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/09_02_01_10/exports/docs/linux/Foundational_Components_OPTEE.html

with the following command:

make CROSS_COMPILE="$CROSS_COMPILE_32" CROSS_COMPILE64="$CROSS_COMPILE_64" PLATFORM=k3-am64x CFG_ARM64_core=y

So I don't think that it is signed in the process. I downloaded the source code from the OP-TEE git repo (github.com/OP-TEE/optee_os.git).

This is the log from the board:

DMSC Firmware Version 9.2.7--v09.02.07 (Kool Koala)
DMSC Firmware revision 0x9
DMSC ABI revision 3.1

[BOOTLOADER_PROFILE] Boot Media       : undefined 
KPI_DATA: [BOOTLOADER_PROFILE] Boot Image Size  : 0 KB 
[BOOTLOADER_PROFILE] Cores present    : 
KPI_DATA: [BOOTLOADER PROFILE] System_init                      :      58080us 
KPI_DATA: [BOOTLOADER PROFILE] Drivers_open                     :        288us 
KPI_DATA: [BOOTLOADER PROFILE] Board_driversOpen                :      30661us 
KPI_DATA: [BOOTLOADER PROFILE] App_loadImages                   :      23381us 
KPI_DATA: [BOOTLOADER_PROFILE] SBL Total Time Taken             :     227599us 

Image loading done, switching to application ...
Starting linux and RTOS/Baremetal applications
ENOTIRCE:  RBL31:O v2.10R.0(:rel ease)B:v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
I/TC: 
I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan 30 10:48:03 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/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
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

After the line "Primary CPU switching to normal world boot" the whole thing seems to get stuck. I can only guess that is has something to do with OP-TEE, but I am not sure.

Regards,

Benjamin

0 Yogesh Siraswar over 1 year ago in reply to Benjamin Limmer

TI__Mastermind 21125 points

Benjamin,

The OPTEE seems to be working fine. Do you have the system booting with pre-built optee?

Thanks

Yogesh

0 Benjamin Limmer over 1 year ago in reply to Yogesh Siraswar

Prodigy 70 points

The behavior is the same when I use the pre-built OP-TEE from sdk/board-support/prebuilt-images.

0 Yogesh Siraswar over 1 year ago in reply to Benjamin Limmer

TI__Mastermind 21125 points

Benjamin,

So, it's not an OPTEE issue. Can you please create another thread so that the issue can be addressed better.

Thanks

Yogesh

Processors

Processors forum

PROCESSOR-SDK-AM64X: SDK 09.02.01.10: error when compiling OP-TEE