obmc-flash-bmc: write variables twice to ensure both banks are correct

The U-Boot environment maintains two banks of environment variables. The
banks need to be consistent with each other to ensure that these
variables can be reliably read from file, as they would be in the
context of a C++ program. In order to guarantee that the two banks are
both correct, we need to run fw_setenv twice when writing environment
variables.

This change accompanies a change to phosphor-bmc-code-mgmt for
openbmc/openbmc#2666.

Change-Id: I72d7fd79faf271d017703464fd9ad0cd20f4e2a0
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
1 file changed
tree: 5aad2ae01cf397f9051956c49271adb39eaa9423
  1. classes/
  2. common/
  3. conf/
  4. COPYING.apache-2.0
  5. COPYING.MIT
  6. LICENSE