From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] stm32mp157c_dk2: fix U-Boot corruption on the first boot
Date: Sun, 4 Jul 2021 18:27:28 +0300 [thread overview]
Message-ID: <YOHTYLvkhpjBDreo@curiosity> (raw)
In-Reply-To: <20210703233130.57f276a7@windsurf>
Hello Thomas,
> > Both trusted and basic images successfully boot only once. Subsequent
> > boot attempts fail to reach U-Boot. The root cause turns out to be in
> > U-Boot corruption during the first boot. The stm32mp1 U-Boot stores its
> > environment at the end of GPT partition named 'ssbl' since v2020.10-rc2.
> > However Buildroot genimage template for stm32mp157 boards creates 'ssbl'
> > partition w/o extra space for U-Boot primary and redundant environments.
> > Add post-build script that appends placeholder for environment to U-Boot
> > image.
> >
> > Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
>
> What about making the ssbl partition larger in the genimage
> configuration file ?
Appending env placeholders looked a bit more ergonomic and future proof
to me. But just making 'ssbl' larger also works fine.
Regards,
Sergey
prev parent reply other threads:[~2021-07-04 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 21:00 [Buildroot] [PATCH 0/4] stm32mp157c-dk2: non-trusted config and bsp updates Sergey Matyukevich
2021-07-01 21:00 ` [Buildroot] [PATCH 1/4] configs/stm32mp157c_dk2: bump BSP versions Sergey Matyukevich
2021-07-03 21:32 ` Thomas Petazzoni
2021-07-01 21:00 ` [Buildroot] [PATCH 2/4] stm32mp157c_dk2: add non-trusted configuration Sergey Matyukevich
2021-07-03 21:16 ` Thomas Petazzoni
2021-07-04 15:30 ` Sergey Matyukevich
2021-07-01 21:00 ` [Buildroot] [PATCH 3/4] stm32mp157c_dk2: remove uboot config fragment Sergey Matyukevich
2021-07-01 21:00 ` [Buildroot] [PATCH 4/4] stm32mp157c_dk2: fix U-Boot corruption on the first boot Sergey Matyukevich
2021-07-03 21:31 ` Thomas Petazzoni
2021-07-04 15:27 ` Sergey Matyukevich [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=YOHTYLvkhpjBDreo@curiosity \
--to=geomatsi@gmail.com \
--cc=buildroot@busybox.net \
/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