From: "Brian Hutchinson" <b.hutchman@gmail.com>
To: Peter Bergin <peter@berginkonsult.se>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] No u-boot-fslc-fw-utils recipe for Dunfell?
Date: Tue, 9 Mar 2021 16:35:21 -0500 [thread overview]
Message-ID: <CAFZh4h9uPtCYZCWkrzt-s2OA2sk7Z0yyoLKVVVfuHVE101Ph4A@mail.gmail.com> (raw)
In-Reply-To: <ec5ae010-1f72-c016-229d-93797398bbb9@berginkonsult.se>
[-- Attachment #1: Type: text/plain, Size: 2936 bytes --]
On Tue, Mar 9, 2021 at 4:29 PM Peter Bergin <peter@berginkonsult.se> wrote:
> Hi Brian,
>
>
> Reviving this issue again ... I noticed that I had to make my own
> fw_env.config file and copy it to etc. in a read/write rootfs for quick
> testing ... there is no fw_env.config sample provided by libubootenv that
> is placed in rootfs under /etc. I'm now generating a squashfs can can't do
> that hack so need to do it in recipe and looking at the recipes ... not
> 100% sure how to go about it.
>
> But shouldn't libubootenv put a example fw_env.config in /etc? I mean it
> won't work like it's supposed to without one.
>
> Regards,
>
> Brian
>
> it is quite useless for libubootenv (in oe-core) to put a general example
> in /etc as it is highly dependent of the target system and where u-boot
> environment is located. But in the BSP-layer(s) it could be good to have
> example files. There are in the meta-freescale-3rdparty for some boards
> already:
>
> meta-freescale-3rdparty$ find . -name fw_env.config
> ./recipes-bsp/u-boot/u-boot-boundary/arm/fw_env.config
> ./recipes-bsp/u-boot/u-boot-boundary/aarch64/fw_env.config
> ./recipes-bsp/u-boot/u-boot-toradex/fw_env.config
> ./recipes-bsp/u-boot/u-boot-toradex/colibri-imx7-emmc/fw_env.config
> ./recipes-bsp/u-boot/u-boot-toradex/colibri-imx6ull/fw_env.config
> ./recipes-bsp/u-boot/u-boot-toradex/mx6/fw_env.config
> ./recipes-bsp/u-boot/u-boot-toradex/colibri-imx7/fw_env.config
> ./recipes-bsp/u-boot/u-boot-toradex/vf/fw_env.config
> ./recipes-bsp/u-boot/u-boot-kontron/fw_env.config
>
> In u-boot there are around 10 options where to store the environment
> (EEPROM, ext4, FAT, flash memory, MMC......) and for some options eMMC for
> example there are several other options such as boot partition and address.
> This is a proof that it is best practice to create your own fw_env.config
> that fits your system and matches the u-boot configuration.
>
> Still no fw_env.config in meta-freescale for the boards defined there. I
> don't know why. Probably it could be feasible with some defaults there. As
> there are default configs for u-boot I guess a fw_env.config could be
> shipped matching that. But on the other hand there are no example images in
> poky or meta-freescale* that includes libubootenv so that can be a reason.
>
> Best regards,
> /Peter
>
I'm about to scream. I can't figure out what I'm doing wrong.
I made a libubootenv_%.bbappend with:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}/:"
SRC_URI_append += " file://fw_env.config"
do_install_append() {
install -d ${D}${sysconfdir}
install -m 0644 ${WORKDIR}/fw_env.config
${D}${sysconfdir}/fw_env.config
}
FILES_${PN} += "${sysconfdir}/fw_env.config"
... and fw_env.conf is going to tmp/deploy/images/imx8mmevk instead of
inside my squashfs.wic file.
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 4619 bytes --]
next prev parent reply other threads:[~2021-03-09 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 19:37 No u-boot-fslc-fw-utils recipe for Dunfell? Brian Hutchinson
2021-01-27 19:42 ` [meta-freescale] " Otavio Salvador
2021-01-27 19:57 ` Brian Hutchinson
2021-01-27 20:10 ` Brian Hutchinson
2021-01-27 20:13 ` Otavio Salvador
2021-01-27 22:24 ` Brian Hutchinson
[not found] ` <165E371A7C0B0DCE.12137@lists.yoctoproject.org>
2021-01-28 4:41 ` Brian Hutchinson
[not found] ` <165E4BA6BFE5FFD7.12137@lists.yoctoproject.org>
2021-01-28 5:25 ` Brian Hutchinson
[not found] ` <165E4E153C3FC07E.12137@lists.yoctoproject.org>
2021-01-29 2:28 ` Brian Hutchinson
[not found] ` <165E92F42A8AA8AC.17182@lists.yoctoproject.org>
2021-03-09 17:06 ` Brian Hutchinson
2021-03-09 21:30 ` Peter Bergin
2021-03-09 21:35 ` Brian Hutchinson [this message]
[not found] ` <166ACA32331689CD.29360@lists.yoctoproject.org>
2021-03-09 22:03 ` Brian Hutchinson
2021-01-27 19:43 ` Chris Dimich
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=CAFZh4h9uPtCYZCWkrzt-s2OA2sk7Z0yyoLKVVVfuHVE101Ph4A@mail.gmail.com \
--to=b.hutchman@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=peter@berginkonsult.se \
/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 NNTP newsgroup(s).