* fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114
@ 2021-11-08 4:01 Brian Hutchinson
2021-11-08 10:49 ` [meta-freescale] " Fabio Estevam
[not found] ` <a111ce56-fe57-a0f1-07d5-684acbbf61dc@berginkonsult.se>
0 siblings, 2 replies; 8+ messages in thread
From: Brian Hutchinson @ 2021-11-08 4:01 UTC (permalink / raw)
To: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Hi,
I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in pre-programmed
NOR flash and was using linux-fslc-imx 5.4.114 kernel and
fw_printenv/fw_setenv were working fine.
After upgrading to linux-fslc-imx 5.10.69, fw_setenv will not change any
u-boot variable. fw_printenv looks like it is working ok. I've verified
all my .config settings are the same with regard to MTD etc as my older
5.4.114 kernel.
Any ideas what could be broken?
I'm using a Dunfell based rootfs for our main system. I did a hardknott
build of core-image-base in order to build linux-fslc-imx 5.10.69 and when
I realized fw_setenv wasn't working with Dunfell rootfs and 5.10.69 kernel,
I built hardknott core-image-base rootfs with libubootenv package added to
CORE_IMAGE_EXTRA_INSTALL thinking I'd copy over fw_printenv/fs_setenv and
libubootenv and that would probably solve my issue ... but it doesn't
include fw_printenv/fw_setenv (but libubootenv is there) in the rootfs so I
don't understand what all is going on here.
Been using fw_printenv/fw_setenv since like ... forever and haven't run
into something like this before that I can remember.
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 2633 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [meta-freescale] fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114
2021-11-08 4:01 fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114 Brian Hutchinson
@ 2021-11-08 10:49 ` Fabio Estevam
2021-11-08 12:55 ` Brian Hutchinson
[not found] ` <16B59367D6CBF8AF.22718@lists.yoctoproject.org>
[not found] ` <a111ce56-fe57-a0f1-07d5-684acbbf61dc@berginkonsult.se>
1 sibling, 2 replies; 8+ messages in thread
From: Fabio Estevam @ 2021-11-08 10:49 UTC (permalink / raw)
To: Brian Hutchinson; +Cc: meta-freescale
Hi Brian,
On Mon, Nov 8, 2021 at 1:01 AM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> Hi,
>
> I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in pre-programmed NOR flash and was using linux-fslc-imx 5.4.114 kernel and fw_printenv/fw_setenv were working fine.
>
> After upgrading to linux-fslc-imx 5.10.69, fw_setenv will not change any u-boot variable. fw_printenv looks like it is working ok. I've verified all my .config settings are the same with regard to MTD etc as my older 5.4.114 kernel.
>
> Any ideas what could be broken?
Could it be that on 5.10 the MTD devices are registered in a different
order, which causes a different mtd numbering of the devices?
Does fw_setenv give any error?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [meta-freescale] fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114
2021-11-08 10:49 ` [meta-freescale] " Fabio Estevam
@ 2021-11-08 12:55 ` Brian Hutchinson
[not found] ` <5bf7fb5e-cdfd-81b0-cbbb-6b958b909fce@berginkonsult.se>
[not found] ` <16B59367D6CBF8AF.22718@lists.yoctoproject.org>
1 sibling, 1 reply; 8+ messages in thread
From: Brian Hutchinson @ 2021-11-08 12:55 UTC (permalink / raw)
To: Fabio Estevam; +Cc: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Hi Fabio,
On Mon, Nov 8, 2021 at 5:49 AM Fabio Estevam <festevam@gmail.com> wrote:
> Hi Brian,
>
> On Mon, Nov 8, 2021 at 1:01 AM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> >
> > Hi,
> >
> > I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in
> pre-programmed NOR flash and was using linux-fslc-imx 5.4.114 kernel and
> fw_printenv/fw_setenv were working fine.
> >
> > After upgrading to linux-fslc-imx 5.10.69, fw_setenv will not change any
> u-boot variable. fw_printenv looks like it is working ok. I've verified
> all my .config settings are the same with regard to MTD etc as my older
> 5.4.114 kernel.
> >
> > Any ideas what could be broken?
>
> Could it be that on 5.10 the MTD devices are registered in a different
> order, which causes a different mtd numbering of the devices?
>
Nope, cat /proc/mtd looks good. Same order as in previous kernels.
> Does fw_setenv give any error?
>
It does not. It shows no signs of a problem, returns no errors or warnings
at all. It "looks" like it worked normal but does not change the u-boot
environment variable.
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 1797 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <16B59367D6CBF8AF.22718@lists.yoctoproject.org>]
* Re: [meta-freescale] fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114
[not found] ` <16B59367D6CBF8AF.22718@lists.yoctoproject.org>
@ 2021-11-08 19:02 ` Brian Hutchinson
0 siblings, 0 replies; 8+ messages in thread
From: Brian Hutchinson @ 2021-11-08 19:02 UTC (permalink / raw)
To: b.hutchman; +Cc: Fabio Estevam, meta-freescale
[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]
On Mon, Nov 8, 2021 at 7:55 AM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:
> Hi Fabio,
>
> On Mon, Nov 8, 2021 at 5:49 AM Fabio Estevam <festevam@gmail.com> wrote:
>
>> Hi Brian,
>>
>> On Mon, Nov 8, 2021 at 1:01 AM Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in
>> pre-programmed NOR flash and was using linux-fslc-imx 5.4.114 kernel and
>> fw_printenv/fw_setenv were working fine.
>> >
>> > After upgrading to linux-fslc-imx 5.10.69, fw_setenv will not change
>> any u-boot variable. fw_printenv looks like it is working ok. I've
>> verified all my .config settings are the same with regard to MTD etc as my
>> older 5.4.114 kernel.
>> >
>> > Any ideas what could be broken?
>>
>> Could it be that on 5.10 the MTD devices are registered in a different
>> order, which causes a different mtd numbering of the devices?
>>
>
> Nope, cat /proc/mtd looks good. Same order as in previous kernels.
>
>
>> Does fw_setenv give any error?
>>
>
> It does not. It shows no signs of a problem, returns no errors or
> warnings at all. It "looks" like it worked normal but does not change the
> u-boot environment variable.
>
> Regards,
>
> Brian
>
>
>
Update. I booted my board via NFS using core-image-base from the hardknot
build I got 5.10.69 from and libubootenv. I copied in
fw_printenv/fs_setenv from
tmp/work/imx8mm_ddr4_evk-poky-linux/libubootenv/0.3.1-r0/image/usr/bin ...
and got the same result. This eliminates any possibility that it was a
libc issue with me copying fw_printenv/fw_setenv to my Dunfell rootfs. So
something else must be going on here. fw_setenv not liking the format of
older u-boot env??? It will be a royal pain if I have to update our u-boot
just to get fw_setenv to work again.
I may take this hardknott wic image and flash it to sdcard and boot from
sdcard so both u-boot and 5.10.69 are of same release to see if that works
... if it does then it points to being a u-boot issue with my older u-boot
;(
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 3232 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <a111ce56-fe57-a0f1-07d5-684acbbf61dc@berginkonsult.se>]
* Re: [meta-freescale] fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114
[not found] ` <a111ce56-fe57-a0f1-07d5-684acbbf61dc@berginkonsult.se>
@ 2021-11-08 12:51 ` Brian Hutchinson
[not found] ` <73b9f65e-7938-7d99-d6c2-e93a74ecade3@berginkonsult.se>
0 siblings, 1 reply; 8+ messages in thread
From: Brian Hutchinson @ 2021-11-08 12:51 UTC (permalink / raw)
To: Peter Bergin; +Cc: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
On Mon, Nov 8, 2021 at 3:03 AM Peter Bergin <peter@berginkonsult.se> wrote:
Hi Peter,
Hi Brian,
> On 2021-11-08 05:01, Brian Hutchinson wrote:
>
> Hi,
>
> I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in
> pre-programmed NOR flash and was using linux-fslc-imx 5.4.114 kernel and
> fw_printenv/fw_setenv were working fine.
>
> After upgrading to linux-fslc-imx 5.10.69, fw_setenv will not change any
> u-boot variable. fw_printenv looks like it is working ok. I've verified
> all my .config settings are the same with regard to MTD etc as my older
> 5.4.114 kernel.
>
> Any ideas what could be broken?
>
> One fundamental part of the libubootenv is the file configuration file,
> default /etc/fw_env.config. This file must match what is configured in
> u-boot. If you only have changed kernel I guess this file is untouched?
>
> I don't know what debugging tools you have in the target, but one idea
> could be to use strace with working and non-working setup and compare.
>
My /etc/fw_env.config is correct. I have my mtd partitions defined in my
.dts and cat /proc/mtd is showing the partitions correctly so I don't see
any problems there.
> I'm using a Dunfell based rootfs for our main system. I did a hardknott
> build of core-image-base in order to build linux-fslc-imx 5.10.69 and when
> I realized fw_setenv wasn't working with Dunfell rootfs and 5.10.69 kernel,
> I built hardknott core-image-base rootfs with libubootenv package added
> to CORE_IMAGE_EXTRA_INSTALL thinking I'd copy over fw_printenv/fs_setenv
> and libubootenv and that would probably solve my issue ... but it doesn't
> include fw_printenv/fw_setenv (but libubootenv is there) in the rootfs so I
> don't understand what all is going on here.
>
> Been using fw_printenv/fw_setenv since like ... forever and haven't run
> into something like this before that I can remember.
>
> The binaries fw_*env is located in the package libubootenv-bin. Add that
> one to IMAGE_INSTALL and I hope you get them in your rootfs.
>
Why wouldn't CORE_IMAGE_EXTRA_INSTALL work to put these in rootfs like
previous builds did?
Thanks,
Brian
[-- Attachment #2: Type: text/html, Size: 5595 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2021-11-10 13:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-08 4:01 fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114 Brian Hutchinson
2021-11-08 10:49 ` [meta-freescale] " Fabio Estevam
2021-11-08 12:55 ` Brian Hutchinson
[not found] ` <5bf7fb5e-cdfd-81b0-cbbb-6b958b909fce@berginkonsult.se>
2021-11-09 14:06 ` Brian Hutchinson
[not found] ` <16B5E5E958FABAD3.3265@lists.yoctoproject.org>
2021-11-10 13:40 ` Brian Hutchinson
[not found] ` <16B59367D6CBF8AF.22718@lists.yoctoproject.org>
2021-11-08 19:02 ` Brian Hutchinson
[not found] ` <a111ce56-fe57-a0f1-07d5-684acbbf61dc@berginkonsult.se>
2021-11-08 12:51 ` Brian Hutchinson
[not found] ` <73b9f65e-7938-7d99-d6c2-e93a74ecade3@berginkonsult.se>
2021-11-08 22:30 ` Brian Hutchinson
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).