From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Andreas L. Schauer" <schauerandreasphone@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: About the support of STM32MP15x by ISAR
Date: Wed, 18 Jan 2023 14:38:04 +0100 [thread overview]
Message-ID: <7bcd3995-e458-1181-2b9b-572b82f8f5dc@siemens.com> (raw)
In-Reply-To: <ab0532a4-cd31-40ec-b630-dc441fdfc746n@googlegroups.com>
On 18.01.23 14:18, Andreas L. Schauer wrote:
> Hello everyone,
> I am wondering if STM32MP15x is currently supported by ISAR.
> It is possible to build an image for it with "bitbake
> mc:stm32mp15x-bullseye:isar-image-base", as there are configurations for it.
> However: This image did not boot on the stm in my case, and there is no
> mention of the stm32mp15x in the Getting Started section in the
> user_manual.
> So i would like to know, if anyone has recently tried to run the image
> on the actual hardware, and if perhaps the stm32mp15x was never
> supported at an "out of the box"-level and users are required to make
> some adjustments.
It was me who once added "support" to Isar for that board as I had it in
hands. At that time, I was looking for a nice demo of integrating TF-A
and OPTEE firmware builds, and the STM was basically working without
some ugly BSP, just mainline. Basically.
I had to debug some stuff upstream as well [1], and it seemed to me that
there was a testing gap against upstream. Might be that something
regressed - or that Isar currently presents versions that contained
regressions meanwhile fixed in newer releases.
Jan
[1]
https://lore.kernel.org/u-boot/4ccf4dcc-a340-6c34-c5b4-ff06d79aa29d@web.de/
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-01-18 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 13:18 Andreas L. Schauer
2023-01-18 13:25 ` Baurzhan Ismagulov
2023-01-18 13:38 ` Jan Kiszka [this message]
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=7bcd3995-e458-1181-2b9b-572b82f8f5dc@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=schauerandreasphone@gmail.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