All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Thiery <heiko.thiery@gmail.com>
To: Stefano Babic <sbabic@denx.de>, Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, "Fabio Estevam" <festevam@gmail.com>,
	"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>,
	"Peng Fan" <peng.fan@nxp.com>, "Ye Li" <ye.li@nxp.com>,
	"Patrick Wildt" <patrick@blueri.se>,
	"Michael Walle" <michael@walle.cc>,
	"Thomas Schäfer" <thomas.schaefer@kontron.com>
Subject: Re: [PATCH v6 2/2] board: kontron: pitx-imx8m: Add Kontron pitx-imx8m board support
Date: Thu, 21 Oct 2021 15:57:22 +0200	[thread overview]
Message-ID: <CAEyMn7bBgst-+SshW+=tGv0+cFj7DD=Qjv5HYmbpf4JERUHA2Q@mail.gmail.com> (raw)
In-Reply-To: <ea6be4f8-d8d4-7773-0ae2-d10cdf07f63b@denx.de>

Hi Stefano, Hi Simon,


Am Do., 21. Okt. 2021 um 15:29 Uhr schrieb Stefano Babic <sbabic@denx.de>:
>
> On 21.10.21 15:17, Heiko Thiery wrote:
> > Hi Stefano,
> >
> >
> > Am Do., 21. Okt. 2021 um 13:31 Uhr schrieb Stefano Babic <sbabic@denx.de>:
> >>
> >> Hi Heiko,
> >>
> >> On 14.10.21 20:08, Heiko Thiery wrote:
> >>> The Kontron pitx-imx8m is an NXP i.MX8MQ based board in the pITX
> >>> form factor.
> >>>
> >>
> >> There is still something using binman that does not work with CI.
> >> Without CI, we load all firmware including signed_hdmi_imx8m.bin.
> >>
> >> But on CI, file is not loaded, but instead of warnings, build for this
> >> board fails with :
> >>
> >> +Image 'main-section' is missing external blobs and is non-functional:
> >> blob-ext@1 blob-ext@2 blob-ext@3 blob-ext@4
> >> +binman: Error 1 running 'mkimage -d ./mkimage.spl.mkimage -n
> >> spl/u-boot-spl.cfgout -T imx8mimage -e 0x7e1000
> >> ./mkimage-out.spl.mkimage': signed_hdmi_imx8m.bin: Can't open: No such
> >> file or directory
> >> +
> >>
> >> Could you take a look ?
> >
> > Sure. Could you point me to the right CI configuration?
> >
>
> Configuration is in .gitlab-ci.yml. For thsi board, buildman is called
> as part of aarch64 target, that is
>
>         buildman -o /tmp -P -E -W arm -x aarch64
>
> > I need to understand how the required imx-firmware files are copied to
> > the u-boot dir. This seems to work already for e. g. the imx8mm
> > boards. These require the lpdd* train fw files.

Here we seem to hit an issue with the CI. blobs (lpddr*) are required
for the imx8mm boards. Binman reports the missing files only as a
warning and buildman does not care about that:
----
+WARNING 'mkimage.flash.mkimage' not found, resulting binary is not-functional
----

With the imx8mq boards switching to binman we also need an additional
fw part (signed_hdmi_imx8m.bin). But other than the lpddr firmware as
blob the signed_hmdi'_imx8m.bin is passed to mkimage and mkimage exits
with an error. Thats leads to the error:
----
binman: Error 1 running 'mkimage -d ./mkimage.spl.mkimage -n
spl/u-boot-spl.cfgout -T imx8mimage -e 0x7e1000
./mkimage-out.spl.mkimage': signed_hdmi_imx8m.bin: Can't open: No such
file or directory
----

Currently I do not have an idea how to handle that. Anyone else?

-- 
Heiko

  reply	other threads:[~2021-10-21 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 18:08 [PATCH v6 1/2] arm: dts: imx8mq: Add Kontron pitx-imx8m Heiko Thiery
2021-10-14 18:08 ` [PATCH v6 2/2] board: kontron: pitx-imx8m: Add Kontron pitx-imx8m board support Heiko Thiery
2021-10-21 11:31   ` Stefano Babic
2021-10-21 13:17     ` Heiko Thiery
2021-10-21 13:29       ` Stefano Babic
2021-10-21 13:57         ` Heiko Thiery [this message]
2021-10-22  8:19           ` Heiko Thiery
2021-10-22 12:37             ` Stefano Babic
2021-10-22 13:24               ` Heiko Thiery
2021-10-22 16:07                 ` Simon Glass
2021-10-22 17:54                   ` Heiko Thiery
2021-10-24 19:54                     ` Simon Glass

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='CAEyMn7bBgst-+SshW+=tGv0+cFj7DD=Qjv5HYmbpf4JERUHA2Q@mail.gmail.com' \
    --to=heiko.thiery@gmail.com \
    --cc=festevam@gmail.com \
    --cc=michael@walle.cc \
    --cc=patrick@blueri.se \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=sjg@chromium.org \
    --cc=thomas.schaefer@kontron.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    --cc=ye.li@nxp.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 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.