From: "Brian Hutchinson" <b.hutchman@gmail.com>
To: "b.hutchman" <b.hutchman@gmail.com>
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: Thu, 28 Jan 2021 21:28:02 -0500 [thread overview]
Message-ID: <CAFZh4h85JwPFUcZRPitKBpYtBT5zbmyNPJ8xco02fxkPHfcpBQ@mail.gmail.com> (raw)
In-Reply-To: <165E4E153C3FC07E.12137@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
>
>
> Update ... feeling like I'm losing my mind now.
>
> fw_env.config must be sensitive to spaces or tabs or something.
>
> I messed around with it some more and it magically started working with my
> imx8mm-evk board with fw_env.config containing:
>
> /dev/mmcblk1 0x400000 0x1000
>
> I don't know why that didn't work before ... I tried all kinds of things
> to get this to work and really can't explain why it just started working.
> To test, I used fw_setenv to set a variable and rebooted and stopped in
> u-boot and did printenv and sure enough the variable I set is there.
>
> Regards,
>
> Brian
>
So I think I figured out what was going on. I flashed sdcard with fresh
Yocto build. Apparently the default u-boot environment is in ram and not
in the eMMC until you stop in u-boot and do a saveenv ... then when you
boot into Linux fw_printenv works. Prior to doing that, fw_printenv will
return the error I previously mentioned.
Hopefully this will help the next person thinking they are losing their
mind messing with creating a fw_env.config file.
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 1624 bytes --]
next prev parent reply other threads:[~2021-01-29 2:28 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 [this message]
[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
[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=CAFZh4h85JwPFUcZRPitKBpYtBT5zbmyNPJ8xco02fxkPHfcpBQ@mail.gmail.com \
--to=b.hutchman@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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).