From: Peter Korsgaard <peter@korsgaard.com>
To: Javad Rahimipetroudi <javad.rahimipetroudi@essensium.com>
Cc: Marleen Vos <marleen.vos@mind.be>,
Javad Rahimipetroudi <javad.rahimipetroudi@mind.be>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 3/3] configs/avenger96: bump ATF version to v2.8
Date: Tue, 19 Mar 2024 11:30:33 +0100 [thread overview]
Message-ID: <87le6ecy46.fsf@48ers.dk> (raw)
In-Reply-To: <CAP_ewpNv3=yRKwOfpBVHAy5mY2uDf-dxEErXrzVm=Ff7xNwCyg@mail.gmail.com> (Javad Rahimipetroudi's message of "Tue, 19 Mar 2024 11:28:08 +0100")
>>>>> "Javad" == Javad Rahimipetroudi <javad.rahimipetroudi@essensium.com> writes:
> Hi Arnout,
> On Tue, Mar 19, 2024 at 9:47 AM Arnout Vandecappelle <arnout@mind.be> wrote:
>>
>>
>>
>> On 19/03/2024 08:05, Javad Rahimipetroudi wrote:
>> > This patch upgrades the ATF version to v2.8. Please note that
>> > due to DTS chages from commit 51e223058fe70b311542178f1865514745fa7874
>> > ("feat(stm32mp15-fdts): add Avenger96 board with STM32MP157A DHCOR SoM")
>> > The ATF additional build variable also modified to use the new DTS file.
>>
>> I noticed that the old DTS file fdts/stm32mp157a-avenger96.dts still exists,
>> but I suppose it doesn't actually work any more then?
>>
> Yes, we are using "stm32mp157a-dhcor-avenger96.dts". If
> "stm32mp157a-avenger96.dts"
> be used, the board will not board with the following error:
> NOTICE: CPU: STM32MP157AAC Rev.B
> NOTICE: Model: Arrow Electronics STM32MP157A Avenger96 board
> ERROR: nvmem node board_id not found
> ERROR: Product_below_2v5=1:
> ERROR: HSLVEN update is destructive,
> ERROR: no update as VDD > 2.7V
> PANIC at PC : 0x2ffee95d
Which seems to match:
commit deb8d71c9285eb60bc3d28e8abcf7208f78980a7
Author: Peter Korsgaard <peter@korsgaard.com>
Date: Sun Nov 5 19:37:19 2023 +0100
configs/avenger96_defconfig: downgrade to TF-A v2.5
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
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-03-19 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 7:05 [Buildroot] [PATCH v3 1/3] configs/avenger96: bump Uboot version to 2024.01 Javad Rahimipetroudi via buildroot
2024-03-19 7:05 ` [Buildroot] [PATCH v3 2/3] configs/avenger96: bump Linux version to 6.6.21LTS Javad Rahimipetroudi via buildroot
2024-03-19 7:05 ` [Buildroot] [PATCH v3 3/3] configs/avenger96: bump ATF version to v2.8 Javad Rahimipetroudi via buildroot
2024-03-19 7:38 ` Peter Korsgaard
2024-03-19 9:57 ` Javad Rahimipetroudi via buildroot
2024-03-19 8:47 ` Arnout Vandecappelle via buildroot
2024-03-19 10:28 ` Javad Rahimipetroudi via buildroot
2024-03-19 10:30 ` Peter Korsgaard [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=87le6ecy46.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=javad.rahimipetroudi@essensium.com \
--cc=javad.rahimipetroudi@mind.be \
--cc=marleen.vos@mind.be \
/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