From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Schultschik,
Sven (DI PA DCP R&D 2)" <sven.schultschik@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [isar-cip-core][PATCH 1/7] add recipe for optee qemu arm64
Date: Wed, 19 Oct 2022 15:14:08 +0200 [thread overview]
Message-ID: <dd629831-dd5e-550a-b378-64ff3d48bbef@siemens.com> (raw)
In-Reply-To: <PAXPR10MB50378126C15801DC63D38C72902B9@PAXPR10MB5037.EURPRD10.PROD.OUTLOOK.COM>
On 19.10.22 15:05, Schultschik, Sven (DI PA DCP R&D 2) wrote:
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
>> Gesendet: Mittwoch, 19. Oktober 2022 12:44
>> An: Schultschik, Sven (DI PA DCP R&D 2) <sven.schultschik@siemens.com>; cip-
>> dev@lists.cip-project.org
>> Betreff: Re: [isar-cip-core][PATCH 1/7] add recipe for optee qemu arm64
>>
>>> + gcc-arm-linux-gnueabihf,"
>>> +
>>> +OPTEE_EXTRA_BUILDARGS =
>> "CFG_STMM_PATH=/usr/lib/edk2/BL32_AP_MM.fd CFG_RPMB_FS=y \
>>> + CFG_RPMB_FS_DEV_ID=0 CFG_CORE_HEAP_SIZE=524288
>> CFG_RPMB_WRITE_KEY=1 \
>>> + CFG_CORE_DYN_SHM=y CFG_RPMB_TESTKEY=y \
>>> + CFG_REE_FS=n\
>>> + CFG_TEE_CORE_LOG_LEVEL=1 CFG_TEE_TA_LOG_LEVEL=1
>> CFG_SCTLR_ALIGNMENT_CHECK=n \
>>> + CFG_ARM64_core=y CFG_CORE_ARM64_PA_BITS=48"
>>> +
>>> +ISAR_CROSS_COMPILE = "0"
>>
>> This looks wrong, specifically as you are installing a 32-bit cross-compiler and
>> calling a 64-bit one as well below.
>
> Optee has it's own weired way to cross compile. If you configure optee for arm64 and activate ISAR cross compile it breaks.
That is at least not generally true:
https://github.com/siemens/meta-iot2050/blob/master/recipes-bsp/optee-os/optee-os-iot2050_3.18.0.bb
>
> Just come in my mind. I could delete the exports completly and set isar cross compile to true. So deactivate the
> Cross compile of optee and use the isar one. I will test if this will work.
>
Will be curious to see the result.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-10-19 13:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 9:21 [isar-cip-core][PATCH 1/7] add recipe for optee qemu arm64 sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 2/7] add recipe for for edk2 sven.schultschik
2022-10-19 10:57 ` Jan Kiszka
2022-10-19 13:14 ` AW: " Schultschik, Sven
2022-10-19 13:21 ` Jan Kiszka
2022-10-20 17:59 ` AW: " Schultschik, Sven
2022-10-20 16:24 ` Schultschik, Sven
2022-10-21 6:57 ` Jan Kiszka
2022-10-19 9:21 ` [isar-cip-core][PATCH 3/7] add recipe for trusted firmware a qemu arm64 sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 4/7] add u-boot patch for qemu to support RPMB sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 5/7] add kas files for building qemu secure boot images sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 6/7] enhance start-qemu.sh for arm64 secure boot sven.schultschik
2022-10-19 9:21 ` [isar-cip-core][PATCH 7/7] no merge - manually instructions test " sven.schultschik
2022-10-19 10:44 ` [isar-cip-core][PATCH 1/7] add recipe for optee qemu arm64 Jan Kiszka
2022-10-19 10:46 ` Jan Kiszka
2022-10-19 13:05 ` AW: " Schultschik, Sven
2022-10-19 13:14 ` Jan Kiszka [this message]
2022-10-19 13:21 ` Schultschik, Sven
2022-10-19 13:24 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd629831-dd5e-550a-b378-64ff3d48bbef@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=sven.schultschik@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox