From: Brian Hutchinson <b.hutchman@gmail.com>
To: "b.hutchman" <b.hutchman@gmail.com>
Cc: Peter Bergin <peter@berginkonsult.se>,
meta-freescale@lists.yoctoproject.org
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
Date: Wed, 10 Nov 2021 08:40:18 -0500 [thread overview]
Message-ID: <CAFZh4h8jxtf_4j9KSHTy=2A_T0JPcTY_t=ap35U-0L=Bk7jwXw@mail.gmail.com> (raw)
In-Reply-To: <16B5E5E958FABAD3.3265@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 2501 bytes --]
Hi everyone and thank you for the comments/ideas etc.
I found my problem. In the new imx8mm-evk.dts for 5.10.69 the flexspi node
has spi-tx-bus-width = <1>; and in all the previous kernel versions
it was spi-tx-bus-width
= <4>; so when moving our customized .dts over to new kernel that was
missed.
flashcp to our NOR and fw_setenv both work now.
Sorry for the noise.
Regards,
Brian
On Tue, Nov 9, 2021 at 9:07 AM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:
> Hi Peter,
>
> Update below.
>
> On Mon, Nov 8, 2021 at 4:14 PM Peter Bergin <peter@berginkonsult.se>
> wrote:
>
>> Hi Brian,
>>
>> On 2021-11-08 13:55, Brian Hutchinson wrote:
>> > 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.
>> >
>> libubootenv in hardknott seems to be 0.3.1. Looked in the libubootenv
>> repo and found this commit that is added after which indicates that it
>> could be silent failure of fw_setenv.
>>
>> https://github.com/sbabic/libubootenv/commit/42f919e29c7b5e86a25877a9c492017e62f8827c
>> I don't have a clue if this helps but just to help you with ideas one
>> thing could be to test this and see if the function libuboot_set_env
>> returns error code or not.
>>
>> Can you write to the memory with some other application than fw_setenv?
>>
>
> No. Apparently not. I've compared kernel .config and device tree source
> from 5.4 series kernel and 5.10 series kernel and I cannot find an
> explanation for this but the following test fails:
>
> root@imx8mmevk:~# flashcp -v ./imx8mm-evk.dtb /dev/mtd7
>
> Erasing blocks: 11/11 (100%)
> Writing data: 40k/40k (100%)
> Verifying data: 10k/40k (24%)File does not seem to match flash data. First
> mismatch at 0x00000000-0x00002800
>
> I simply tried writing a file to an area of my NOR that I didn't care if
> it got overwritten. So it does look like there is a problem with kernel
> flexspi driver or mtd drivers?
>
> Regards,
>
> Brian
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#24788):
> https://lists.yoctoproject.org/g/meta-freescale/message/24788
> Mute This Topic: https://lists.yoctoproject.org/mt/86899154/3619744
> Group Owner: meta-freescale+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub [
> b.hutchman@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 6375 bytes --]
next prev parent reply other threads:[~2021-11-10 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFZh4h8jxtf_4j9KSHTy=2A_T0JPcTY_t=ap35U-0L=Bk7jwXw@mail.gmail.com' \
--to=b.hutchman@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=peter@berginkonsult.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).