cancel
Showing results for 
Search instead for 
Did you mean: 

export-user_ta is missing in yocto SDK

Morandg
Associate II

Hi ST community!

I am porting our Yocto bsp to the latest st scarthgap (openstlinux-6.6-yocto-scarthgap-mpu-v25.03.19) for our custom modules based on a stm32mp157c. When I source the Yocto SDK, the error is shown:

 

[SDK ERROR] Issue to optee export-user_ta directory

 

My main issue is that I cannot recompile optee (4.0.0-stm32mp-r1.2) outside of yocto:

 

make PLATFORM=stm32mp1 CFG_EMBED_DTB_SOURCE_FILE=<our-devkit>.dts CFG_TEE_CORE_LOG_LEVEL=2 O=build all
...
arm-poky-linux-gnueabi-ld.bfd: cannot find libgcc.a: No such file or directory

 

I have tried to pass the sysroot on the command line (CFLAGS, LDFLAGS, ...) but nothing worked!

  • What is missing during the SDK build?
  • Is there a way to fix this temporarly on the command line?

Thanks for the pointers!

6 REPLIES 6
jpcarlos
Associate II

I got this one fixed after changing the appended value to BOOTSCHEME_LABELS from "opteemin" to "optee". You will find this line in the machine configuration file of your custom board ( meta-st/meta-st-stm32mp-addons/conf/machine/).

After updating this don't forget to regenerate and re-install the SDK.

 

Thanks for your input, I will give it a try! But what if I really want "opteemin"?

jpcarlos
Associate II

That's something I have not tried yet but if you look at the machine configuration file stmm32mp1.conf (meta-st/meta-st-stm32mp/conf/machine) BOOTSCHEME_LABELS is set to optee + opteemin + fastboot-opteemin + fastboot. I'm assuming for now we just have to always include optee for some reason.

Hey,

I tried your solution but it didn't work for me. Switching to the optee version had the same problem. I was using the Distribution-package (open Embedded build).  

jpcarlos
Associate II

Hi cwei2010

Could you please provide more details as I already tested both of my suggestions are working.

Hi,

I checked again and found that switching to optee does work while building the default image (st-image-weston). However, I was using images like core-image-full-cmdline from meta layer so it couldn't get fixed from that. It pointed to somewhere, though, thanks a lot.