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

Brian Hutchinson <[email protected]> Mon, 8 Nov 2021 07:55:00 -0500
Newsgroups org.yoctoproject.lists.meta-freescale
Message-ID <CAFZh4h-1famKHUGPxAr7fvT7mFu5rv7ecG-5TWj9nSa-Y+LFOA@mail.gmail.com>
Hi Fabio,

On Mon, Nov 8, 2021 at 5:49 AM Fabio Estevam <[email protected]> wrote:

> Hi Brian,
>
> On Mon, Nov 8, 2021 at 1:01 AM Brian Hutchinson <[email protected]>
> 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