[Bug 1870981] Re: u-boot environment modification does not work raspberry 4 with eoan

[Dave Jones]

I'm unable to reproduce this on either the 19.10.1 image, or the current
Focal dailies.

On the very first boot the message "Loading environment from FAT... ***
Warning - bad CRC, using default environment" does appear but that's
because these images have no environment to load from the FAT boot
partition. However, interrupting u-boot and entering the commands you've
specified does produce a valid uboot.env on the partition and subsequent
boots show the message "Loading environment from FAT... OK", and don't
show any interruption prompt.

Can you confirm a uboot.env exists in /boot/firmware and is 131072 bytes
large?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/1870981

Title:
  u-boot environment modification does not work raspberry 4 with eoan

Status in u-boot package in Ubuntu:
  New

Bug description:
  Description:    Ubuntu 19.10
  Release:        19.10
  Package: u-boot-rpi (2019.07+dfsg-1ubuntu3)

  On a Raspberry Pi 3 model B, I can interrupt the u-boot process and
  use the following two commands to disable the boot delay. I do this as
  I have a GPS device attached to the serial port and the NMEA messages
  will halt the u-boot boot process.

  Commands:
  setenv bootdelay -2
  saveenv

  This saves a u-boot environment file into the /boot filesystem such
  that this setting persists across power cycles.

  However, with eoan on a Raspberry Pi 4, this environment file is not
  written out properly and on subsequent reboots u-boot will say that
  the file is corrupt. This will cause u-boot to revert to the built in
  defaults which causes the u-boot process to halt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1870981/+subscriptions