From: Christian Melki <christian.melki@t2data.com>
To: Felix Mellmann <flix.ptxdist@benfm.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Best practice integrating firmwares in U-Boot builds
Date: Wed, 25 May 2022 17:56:27 +0200 [thread overview]
Message-ID: <f93b4c2b-03b6-414b-9b55-d3d2a97b44de@t2data.com> (raw)
In-Reply-To: <8f755f04-56ea-127b-ce7e-48018a7bc1b8@benfm.de>
On 5/25/22 17:22, Felix Mellmann wrote:
> Hi,
>
> when I tried to set up a PTXdist environment for a NXP i.MX8MP based
> board (Phytec phyBoard Pollux) I stumbled across the need to provide
> firmware images during the U-Boot build process (LPDDR4 training data
> and TF-A BL31 firmware).
>
> Is there a best practice on how to provide those firmwares during build?
> Currently I helped myself and modified u-boot.make to copy the firmware
> files at the very beginning of the compile stage to the build directory...
>
Ie. I did something like this a while ago.
PTXCONF_U_BOOT_CUSTOM_MAKE_OPTS="BL31=${PTXDIST_PLATFORMDIR}/build-target/tf-a-imx_5.4.70_2.3.0/build/imx8mm/release/bl31.bin
ATF_LOAD_ADDR=0x920000 flash.bin
> Best regards,
>
> Felix
>
>
>
next prev parent reply other threads:[~2022-05-25 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 15:22 Felix Mellmann
2022-05-25 15:53 ` Christian Melki
2022-05-25 15:56 ` Christian Melki [this message]
2022-05-25 18:55 ` Sascha Hauer
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=f93b4c2b-03b6-414b-9b55-d3d2a97b44de@t2data.com \
--to=christian.melki@t2data.com \
--cc=flix.ptxdist@benfm.de \
--cc=ptxdist@pengutronix.de \
/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