oe4t / meta-mender-community Goto Github PK

See post at https://hub.mender.io/t/failing-updates-on-tegra-tx2-due-to-issues-with-nvbootctrl/2765 and https://forums.developer.nvidia.com/t/nvbootctrl-get-current-slot-returning-unexpected-slot/156982/2

It appears boot slots are changing in some cases between mender updates for reasons unknown. When the boot slot gets out of sync with u-boot partitions bad things happen.

For TX2 this is a reason to make the mender build use PREFERRED_PROVIDER_virtual/bootloader = "cboot-prebuilt" as default as described at this link. It may not solve the problem completely but I think it will make the resulting situation less of a mess.

For Nano we are stuck with u-boot so we'll need to figure out how to handle this.

Hi,

We recently started working on a new version of our device based on the Xavier NX module. By default, the meta-tegra layer configures this module to use cboot instead of UBoot.

To make this work with Mender, there is the custom libubootenv-fake scripts that are installed on the rootfs. However, when using delta updates, these are not sufficient. For more context, see https://hub.mender.io/t/delta-updates-checksum-mismatch/3312

Basically, what happens, is that the binary delta installer looks at mender_boot_part to determine which partition it should use as its base for applying the delta update. However, in the fake fw_printenv script, this will return nvbootctrl get-current-slot, essentially toggling between 0 or 1. The delta update then fails to apply because the checksum mismatches.

Would it be possible to modify this script to return the correct rootfs partition based on the slot? Or do you think this would trigger other issues? If you see no problems with this, I can try to make a pull request.

Thanks in advance,
Best regards,
Niels Avonds

As of OE4T/meta-tegra#452 the L4T release 32.4.4 is supported on the master branch of meta-tegra. This release should support the Nano 2GB, and support is in progress - see latest status at https://github.com/OE4T/meta-tegra/wiki/L4T-R32.4.4-Notes

There are no plans currently to backport support for r32.4.4 to dunfell or to upstream Nano 2GB support to meta-mender-community until L4T+next.

We are looking for community members who are interested in helping with adding/testing support for Nano 2GB. Please comment here if you would like to help.

I hope this is the right place to post this:
I'm using a TX2, and meta-tegra zeus-l4t-32.3.1 , meta-mender zeus-v2020.06 and u-boot.
I built an artifact using meta-tegra dunfell-l4t-32.4.3 and meta-mender dunfell-v2020.10
A Mender (managed, not standalone) update with this artifact is successful:

{"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactCommit_Leave_20_printVolatileInfo
nvbootctrl dump-slots-info:
slot: 0,             priority: 14,             suffix: _a,             retry_count: 7,             boot_successful: 0
slot: 1,             priority: 15,             suffix: _b,             retry_count: 7,             boot_successful: 1
nvbootctrl get-current-slot:1
mender_boot_part=33
---------- end of script output","timestamp":"2020-11-16T18:32:16Z"}
/dev/mmcblk0p33 is used

But after another reboot, it switches back to the old partition:

slot: 0,            priority: 13,            suffix: _a,            retry_count: 7,            boot_successful: 0
slot: 1,            priority: 15,            suffix: _b,            retry_count: 7,            boot_successful: 1
current-slot 1
/dev/mmcblk0p1 is used
mender_boot_part=1

Hi

I have prepare the tegraflash file using "bitbake demo-image-weston".
Build is successfully.
Now I have flash the SD card using "./dosdcard.sh", it is also success.

Now when I connect the SD Card to NVIDIA Tegra Jetson Xavier NX board, it is giving error
failed to mounting ext4 file system using ext3 subsystem
failed to mounting ext4 file system using ext2 subsystem

Can you please suggest what could be the problem?

Regards,

Partition layout changes on L4T releases have made this not trivial to support for older yocto branches.

Changes are coming with L4T version 32.6 which we may be able to leverage to upgrade from older branches, and no partition changes are planned from r32.5 (gatesgarth) forward at this time.

See OE4T meeting notes at this link and watch meeting updates in this link for more information.

See this sheet which tracks some combination of changes to partition layout between releases and has some references to associated xml files where these changes are tracked.

See this commit which backs out a feature to support u-boot environment partition migration between releases, which could be useful for TX2 u-boot based mender implementations.