From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Bartosz Bilas <b.bilas@grinn-global.com>,
Simon Doppler <dopsi@dopsi.ch>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] configs/stm32mp157*_dk*: bump U-Boot version to 2023.04
Date: Wed, 26 Jul 2023 23:09:08 +0200 [thread overview]
Message-ID: <20230726230908.73695bcf@windsurf> (raw)
In-Reply-To: <20230703160149.2302949-2-dario.binacchi@amarulasolutions.com>
On Mon, 3 Jul 2023 18:01:49 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> The u-boot.stm32 image is now created by binman tool, so the
> BR2_TARGET_UBOOT_BUILD_FORMAT_STM32_LEGACY configuration needs to be
> disabled.
>
> Tested on stm32mp157f_dk2
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> configs/stm32mp157a_dk1_defconfig | 3 +--
> configs/stm32mp157c_dk2_defconfig | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/configs/stm32mp157a_dk1_defconfig b/configs/stm32mp157a_dk1_defconfig
> index 3b8fdea993ac..2ec063b51c61 100644
> --- a/configs/stm32mp157a_dk1_defconfig
> +++ b/configs/stm32mp157a_dk1_defconfig
> @@ -36,11 +36,10 @@ BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_DTC=y
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> BR2_TARGET_UBOOT_CUSTOM_VERSION=y
> -BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2021.10"
> +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2023.04"
> BR2_TARGET_UBOOT_BOARD_DEFCONFIG="stm32mp15_trusted"
> # BR2_TARGET_UBOOT_FORMAT_BIN is not set
> BR2_TARGET_UBOOT_FORMAT_STM32=y
> -BR2_TARGET_UBOOT_BUILD_FORMAT_STM32_LEGACY=y
> BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
> BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=stm32mp157a-dk1"
This was not sufficient: as binman is now used, it needs pylibfdt, so
the option BR2_TARGET_UBOOT_NEEDS_PYLIBFDT had to be enabled as well. I
did that for both defconfigs, and verified that uboot was building fine
inside a minimal Docker container.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-26 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 16:01 [Buildroot] [PATCH 1/2] boot/u-boot: fix u-boot.stm32 creation on newer version Dario Binacchi
2023-07-03 16:01 ` [Buildroot] [PATCH 2/2] configs/stm32mp157*_dk*: bump U-Boot version to 2023.04 Dario Binacchi
2023-07-26 21:09 ` Thomas Petazzoni via buildroot [this message]
2023-07-17 16:48 ` [Buildroot] [PATCH 1/2] boot/u-boot: fix u-boot.stm32 creation on newer version David Reaver
2023-07-26 21:08 ` Thomas Petazzoni via buildroot
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=20230726230908.73695bcf@windsurf \
--to=buildroot@buildroot.org \
--cc=b.bilas@grinn-global.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=dopsi@dopsi.ch \
--cc=thomas.petazzoni@bootlin.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