From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id B24A6C4332F for ; Mon, 8 Nov 2021 12:51:58 +0000 (UTC) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) by mx.groups.io with SMTP id smtpd.web08.44391.1636375915343121485 for ; Mon, 08 Nov 2021 04:51:55 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=eJr0xiTQ; spf=pass (domain: gmail.com, ip: 209.85.221.42, mailfrom: b.hutchman@gmail.com) Received: by mail-wr1-f42.google.com with SMTP id t30so26679135wra.10 for ; Mon, 08 Nov 2021 04:51:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZjSuc4UZss621T8MFbdINYsoaCFS2S1A8cnK2CynaRA=; b=eJr0xiTQWo0lp2fCxsvx0LoXcwfiABsT0MUwchwhvIVWyzfbDcQrLLdOWMQW/jKZwn dYnWhjhwqb9K2COrMUUAKN4Iwfx5i1dw+ah729eszcqq6doggmN5mizuplFCoki4ecDm rP8l5RCjYGmmiZTQ4OqKV0GM0kT42XynntpooicqeKY6Cxcu25s28b2tR9HKCpztpCTZ HyNGZgLjHtkHZkvKBDVyW8/3Ny5J/NW9VSif75nG6p7fa70BV1PptbpbCecO+JaXuGbL Nzh/KSmR8Yb5kMQHRk0zqDhxaAICONWoJblkAHGkgrltKfUToekq5DguFFPUtzq1yDmZ LETQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZjSuc4UZss621T8MFbdINYsoaCFS2S1A8cnK2CynaRA=; b=jOFo1O197G+z1KCWxsbsI8F+xeOwvk4j31mGv5603Pl4hdZzlTcQhaWqO6AXXOj1H6 OHN0uVpy6mv7FgCowjpyKHSuTCy7u+eEZDplIphAZcVOI18nO2CLuZFB4vi5syUjlr3D iTgEX4961J/AMduRdvAkPs4e0G7qwU8fNxy69Z9b8qGai8eKORv4w+UDbI7+yThay1TE cgIu7Wol1lWOGeRxxwwAX/cR1ljWb81CTSRqtnODjc5g/qOGEF+UZ37hcIaevtzq1HNT MDagvBKHw4dxWFSht9GI+7/2hytOHYmxB44At1aKrz9sT5Xet7QtAQa5/toSW2Xd/IL0 LDeQ== X-Gm-Message-State: AOAM531rA30L26TDJtvNzy+q4OrtJqTRd/DOP2E0Y0/Z+OTEVQaVsPUS YncBURfr5MmJL2z4Wm6F240I1JGlO0LLr3iMneo= X-Google-Smtp-Source: ABdhPJy3aVBYNFnsHAaa5foQ2VBY0Sb/OlBu7BobeiV/zIzenGFZa/aVZsklO59dzP7LLlvcQ5I7YyWAdtHAR9Az3DQ= X-Received: by 2002:a5d:4904:: with SMTP id x4mr89293960wrq.139.1636375913823; Mon, 08 Nov 2021 04:51:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Brian Hutchinson Date: Mon, 8 Nov 2021 07:51:43 -0500 Message-ID: Subject: 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 To: Peter Bergin Cc: meta-freescale@lists.yoctoproject.org Content-Type: multipart/alternative; boundary="00000000000010003405d046750a" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 08 Nov 2021 12:51:58 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/meta-freescale/message/24782 --00000000000010003405d046750a Content-Type: text/plain; charset="UTF-8" On Mon, Nov 8, 2021 at 3:03 AM Peter Bergin 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 --00000000000010003405d046750a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Nov 8, 2021 at 3:03 AM Peter = Bergin <peter@berginkonsult.se= > wrote:

Hi Peter,

=20 =20 =20

Hi Brian,

On 2021-11-08 05:01, Brian Hutchinson wrote:
=20
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.=C2=A0 fw_printenv looks like it i= s working ok.=C2=A0 I've verified all my .config settings a= re 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 on= e idea could be to use strace with working and non-working setup and compare.


My /etc/fw_env= .config is correct.=C2=A0 I have my mtd partitions defined in my .dts and c= at /proc/mtd is showing the partitions correctly so I don't see any pro= blems there.

I'm using a Dunfell based rootfs for our main system.=C2=A0 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 libubooten= v package added to CORE_IMAGE_EXTRA= _INSTALL thinking I'd copy over fw_printenv/fs_setenv and libubooten= v 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 ru= n 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=C2=A0 get them in your rootfs.=

Why wouldn't=C2=A0 CORE_IMAGE_EXTRA= _INSTALL work to put these in rootfs like previous builds did?

Thanks,
=
Brian
--00000000000010003405d046750a--