Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-3970

uboot: When Mender client writes U-Boot environment with fw_setenv, it results in an empty value instead of the real value, bricking devices.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: (None)
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: None
    • Sprint:
      MEN Sprint 121, MEN Sprint 122, MEN Sprint 123
    • Story Points:
      5
    • Backlog:
      yes
    • Days in progress:
      20

      Description

      Problem:

      • The problem stems from this commit.
      • While the comment in the commit is correct, the problem is that U-Boot has not supported this syntax for very long, so it still breaks on older U-Boot forks.

      Preferred fix:

      • Strictly speaking, it is libubootenv which broke this, not us.
      • Fix libubootenv so that it supports variable value syntax, in addition to variable=value.
      • Submit upstream.
      • While waiting for acceptance, submit to meta-mender/master and meta-mender/dunfell as a libubootenv.bbappend patch.
      • Revert the Mender client commit.

      Backup fix (more hacky, less desirable):

      • Adapt Mender client so that it first writes a dummy variable using the new syntax, checks that to see if it can read it back, and then uses that to decide which syntax to use.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              oleorhagen Ole Petter Orhagen
              Reporter:
              a10040 Kristian Amlie
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support