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

wipe env on bootloader upgraded #38

Open
Shpinkso opened this issue Mar 2, 2017 · 0 comments
Open

wipe env on bootloader upgraded #38

Shpinkso opened this issue Mar 2, 2017 · 0 comments

Comments

@Shpinkso
Copy link
Contributor

Shpinkso commented Mar 2, 2017

Every so often we release a new bootloader to include new feature. Often if an advanced user has been changing the uEnv this is left behind and causes boot problems. The safest thing to do is to reset this uEnv whenever the bootloader is upgraded.

Acceptance criteria:

  • When programming a u-boot image into NOR with any tool (flashcp, dediprog, etc) the uEnv should get reset
  • The bootloader should not print out warnings about CRC failures in uEnv on boot after programming
  • Community team are informed of changes made and know how this would affect their documentation after the next release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant