Bricked device on warrior branch with Mender 2.3

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.

Affects versions

Environment

None

Checklist

Activity

Show:

Kristian AmlieAugust 28, 2020 at 8:14 AM

Fixed with a build warning that you need to cherry-pick a specific patch.

Kristian AmlieAugust 27, 2020 at 7:11 AM

: If you cherry-pick this commit to warrior, does the warning trigger for you? https://github.com/mendersoftware/meta-mender/pull/1069/commits/758ba7b9cdf7d0a6a05f2772d55163f7d58658eb

Niels AvondsAugust 26, 2020 at 7:21 AM

Hi Kristian, no problem. The u-boot and u-boot-fw-utils versions are both 2016.07. The recipe used for those are in the meta-tegra Yocto layer.

Kristian AmlieAugust 26, 2020 at 7:14 AM

Hi, , sorry for the delay. I don't have the board myself; which version of U-Boot is being used?

Fixed

Details

Assignee

Reporter

Labels

Priority

Days in progress

0

Zendesk Support

Checklist

Created July 31, 2020 at 12:19 PM
Updated June 25, 2024 at 12:02 PM
Resolved August 28, 2020 at 8:14 AM

Flag notifications