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

Bricked device on warrior branch with Mender 2.3

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: (None)
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: None
    • Labels:
    • Days in progress:
      0

      Description

      After updating our warrior-based rootfs to use Mender version 2.3, the next update bricks the device. This is because the u-boot variables (such as mender_boot_part) get unset. I've traced it back to this commit:

      https://github.com/mendersoftware/mender/commit/b2507398889da5de4d859a97cf9fd8d0daf1449c

      I manually run fw_setenv to verify:

      nobi-aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:~# echo "mender_boot_part=1" | fw_setenv -s -
      nobi-aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:~# fw_printenv mender_boot_part
      ## Error: "mender_boot_part" not defined
      nobi-aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:~# echo "mender_boot_part 1" | fw_setenv -s -
      nobi-aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:~# fw_printenv mender_boot_part
      mender_boot_part=1
      

      For the record: we're using a Jetson TX2 and the meta-mender-tegra community layer, but I don't think they're involved here.

        Attachments

          Activity

            People

            • Assignee:
              a10040 Kristian Amlie
              Reporter:
              nielsavonds Niels Avonds
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support