Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nitrogen6x: Can't write on U-Boot environment #211

Open
Ossanes opened this issue Apr 29, 2022 · 3 comments
Open

nitrogen6x: Can't write on U-Boot environment #211

Ossanes opened this issue Apr 29, 2022 · 3 comments

Comments

@Ossanes
Copy link
Contributor

Ossanes commented Apr 29, 2022

Image: core-image-base
Kernel version: 5.10.104+gbb58f0eeb397
U-Boot Boundary version: v2020.10+gitAUTOINC+3d5e7f6023
Release: Master

I'm using fw_printenv (from u-boot-fw-utils) to read the environment.

fw_env.config:
/dev/mtd1 0x00000 0x2000 0x1000 2

When I write any variable to the env using fw_setenv, I can't read it anymore.

root@nitrogen6x:/# fw_printenv
Cannot read environment, using default
Cannot read default environment from file

@gibsson

@gibsson
Copy link
Contributor

gibsson commented Apr 29, 2022

@chrisdimich could you look into that, is it ok on our honister image? Thanks

@otavio
Copy link
Member

otavio commented Jun 23, 2022

News?

@gibsson
Copy link
Contributor

gibsson commented Jun 23, 2022

Yes, this is a bug in the MTD driver of the kernel which is broken since 5.4 (up to 5.15). When you write from userspace only the first byte is written to, so CRC is wrong. We hope to have a solution soon. We'll update once it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants