Fixed
Details
Assignee
Kristian AmlieKristian AmlieReporter
Niels AvondsNiels AvondsLabels
Priority
(None)Days in progress
0
Details
Details
Assignee
Kristian Amlie
Kristian AmlieReporter
Niels Avonds
Niels AvondsLabels
Priority
Days in progress
0
Zendesk Support
Zendesk Support
Zendesk Support
Checklist
Checklist
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
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.