($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Peter Bergin" <peter@berginkonsult.se>
To: meta-freescale@lists.yoctoproject.org
Subject: Use u-boot-fslc for imx8mnevk
Date: Wed, 8 Jul 2020 16:40:11 +0200	[thread overview]
Message-ID: <23f399fe-2235-8390-b91a-ca88ecc6075b@berginkonsult.se> (raw)

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

Hi,

working with dunfell branch and I want to build image for i.Mx8M Nano 
EVK and using u-boot-fslc as bootloader.

I have this setup in my conf/auto.conf:

PREFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx"
PREFERRED_PROVIDER_virtual/bootloader="u-boot-fslc"
PREFERRED_PROVIDER_u-boot="u-boot-fslc"
UBOOT_DTB_NAME="imx8mn-ddr4-evk.dtb"

As I'm also building the linux-fslc-imx kernel I have 'IMX_DEFAULT_BSP = 
"nxp"' set. And with this setting the u-boot-fslc was incompatible with 
imx8mnevk machine. So here I'm a bit stuck. To come pass this I added a 
bbappend and made u-boot-fslc compatible with my machine. Is 
linux-fslc-imx+u-boot-fslc an unsupported config to use?

With u-boot-fslc enabled for my machine the build work as expected and 
the correct kernel and bootloader are built. But it fails at imx-boot 
that search for a dtb file that shall be present in 
tmp/deploy/images/imx8mnevk/imx-boot-tools. When using NXPs u-boot-imx 
this file is placed in that directory in do_deploy_append but this is 
not done for u-boot-fslc. Shall imx-boot and u-boor-fslc be used 
together or is it another way to package this when using u-boot-fslc?

Anyone having input in this? Is this a bug or do I need to change my 
config? Is this a tested configuration by someone or am I the first one 
trying this out?

Thanks,
/Peter



[-- Attachment #2: Type: text/html, Size: 1733 bytes --]

                 reply	other threads:[~2020-07-08 14:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=23f399fe-2235-8390-b91a-ca88ecc6075b@berginkonsult.se \
    --to=peter@berginkonsult.se \
    --cc=meta-freescale@lists.yoctoproject.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).