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 <b.hutchman@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Hi Peter,

On Mon, Nov 8, 2021 at 3:54 PM Peter Bergin <peter@berginkonsult.se> wrote:

> Hi Brian,
> On 2021-11-08 13:51, Brian Hutchinson wrote:
>
> 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?
>
>
> CORE_IMAGE_EXTRA_INSTALL can be used as well and it will end up in
> IMAGE_INSTALL variable handled by core-image.bbclass. My point was that the
> binaries are in the package libubootenv-bin not in libubootenv. So you have
> to make sure you have libubootenv-bin in your IMAGE_INSTALL or another
> package that RDEPENDS on libubootenv-bin in order to get the binaries in
> your rootfs.
>
You got me!  In my previous build I just had libubootenv and that appeared
to work for my dunfell build somehow even that release shows
fw_printenv/fw_setenv to be in the libubootenv-bin package too.  Weird.

But putting libubootenv-bin in my build did make the bins included in my
rootfs now.  So one mystery solved.

Thank you!

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 3776 bytes --]