On 28.11.21 22:57, Ivan Mikhaylov wrote:

From: Ivan Mikhaylov ivan.mikhaylov@siemens.com

Set ta-target explicitly to correspond with OP-TEE recipe in siemens/meta-iot2050.

Errors without explicit set of ta-target: aarch64-linux-gnu-gcc: error: unrecognized command-line option ‘-mthumb’ aarch64-linux-gnu-gcc: error: unrecognized command-line option ‘-mno-unaligned-access’ aarch64-linux-gnu-gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’ make: *** [mk/compile.mk:159: out/arm-plat-k3/ta_arm32-lib/libdl/dlfcn.o] Error 1

Signed-off-by: Ivan Mikhaylov ivan.mikhaylov@siemens.com

doc/board/siemens/iot2050.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/board/siemens/iot2050.rst b/doc/board/siemens/iot2050.rst index 592c59be03..7e97f817ce 100644 --- a/doc/board/siemens/iot2050.rst +++ b/doc/board/siemens/iot2050.rst @@ -49,7 +49,7 @@ OP-TEE:

.. code-block:: text

• $ make PLATFORM=k3-am65x CFG_ARM64_core=y CFG_TEE_CORE_LOG_LEVEL=2 CFG_CONSOLE_UART=1

• $ make PLATFORM=k3-am65x CFG_ARM64_core=y CFG_TEE_CORE_LOG_LEVEL=2 CFG_CONSOLE_UART=1 CFG_USER_TA_TARGETS="ta_arm64"

U-Boot:

Reviewed-by: Jan Kiszka jan.kiszka@siemens.com

Thanks, Jan

PS: We should align our own build recipe to this pattern (CFG_USER_TA_TARGETS, rather than ta-targets).