From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] configs/avenger96_defconfig: downgrade to TF-A v2.5
Date: Fri, 10 Nov 2023 13:26:09 +0100 [thread overview]
Message-ID: <87h6ltlrq6.fsf@48ers.dk> (raw)
In-Reply-To: <20231105183719.3811015-4-peter@korsgaard.com> (Peter Korsgaard's message of "Sun, 5 Nov 2023 19:37:19 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Commit 27bf08e4addb78 (configs/avenger96_defconfig: bump ATF version to 2.9
> for binutils 2.39+ support) bumped TF-A, but it unfortunately does not boot
> and instead dies with a panic:
> NOTICE: CPU: STM32MP157AAC Rev.B
> NOTICE: Model: Arrow Electronics STM32MP157A Avenger96 board
> ERROR: nvmem node board_id not found
> INFO: PMIC version = 0x10
> ERROR: Product_below_2v5=1:
> ERROR: HSLVEN update is destructive,
> ERROR: no update as VDD > 2.7V
> PANIC at PC : 0x2fff086f
> Exception mode=0x00000016 at: 0x2fff086f
> Instead use v2.5 to match the other stm32mp1 boards and use the same E=0
> -Werror workaround. The avenger95 support is unfortunately broken since
> v2.3 with the introduction of authentication support, so add a patch to the
> DTS to fix that.
> Notice that the authentication support was reworked in v2.7 so it is skipped
> for the mp157a variant used on the avenger96, so the patch is not upstreamable.
> While we're at it, also drop the debug option for consistency with the other
> boards.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-10 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 18:37 [Buildroot] [PATCH 1/4] configs/stm32mp157a_dk1_defconfig: unbreak TF-A build with GCC >= 12 Peter Korsgaard
2023-11-05 18:37 ` [Buildroot] [PATCH 2/4] configs/stm32mp157c_dk2_defconfig: " Peter Korsgaard
2023-11-10 12:24 ` Peter Korsgaard
2023-11-05 18:37 ` [Buildroot] [PATCH 3/4] configs/stm32mp157c_odyssey_defconfig: use a fixed TF-A version Peter Korsgaard
2023-11-10 12:24 ` Peter Korsgaard
2023-11-05 18:37 ` [Buildroot] [PATCH 4/4] configs/avenger96_defconfig: downgrade to TF-A v2.5 Peter Korsgaard
2023-11-10 12:26 ` Peter Korsgaard [this message]
2023-11-05 20:22 ` [Buildroot] [PATCH 1/4] configs/stm32mp157a_dk1_defconfig: unbreak TF-A build with GCC >= 12 Arnout Vandecappelle via buildroot
2023-11-06 9:18 ` Peter Korsgaard
2023-11-06 22:11 ` Thomas Petazzoni via buildroot
2023-11-10 12:24 ` Peter Korsgaard
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=87h6ltlrq6.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.