1. posterid:3619744
  2. Messages

Re: 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
 



On Mon, Nov 8, 2021 at 7:55 AM Brian Hutchinson via lists.yoctoproject.org <b.hutchman=gmail.com@...> wrote:
Hi Fabio,

On Mon, Nov 8, 2021 at 5:49 AM Fabio Estevam <festevam@...> wrote:
Hi Brian,

On Mon, Nov 8, 2021 at 1:01 AM Brian Hutchinson <b.hutchman@...> 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
Join meta-freescale@lists.yoctoproject.org to automatically receive all group messages.