Mender update has no effect on Xavier NX (eMMC) about tegra-demo-distro HOT 12 CLOSED

Check your build setup... that script gets deployed by the tegra-state-scripts recipe, and it sounds like that isn't getting built for some reason.

The script was indeed missing from the deploy directory. Weird though the build step went through without error...
bitbake -c clean tegra-state-scripts; bitbake tegra-state-scripts did the job.

Thanks !

from tegra-demo-distro.

When doing manual installs, you must reboot first. If the reboot into the new rootfs succeeds, then log in and commit the update.

from tegra-demo-distro.

I did it as you said, rebooting after install and then committing. But it still uses the old partition.
INFO[0000] Mender running on partition: /dev/mmcblk0p1

from tegra-demo-distro.

Which branch are you using?

from tegra-demo-distro.

Also can you share the console output from mender install?

from tegra-demo-distro.

And also check if the update actually succeeded... if the boot failed, it would fallback to the old partition.

from tegra-demo-distro.

Here it is:

root@jetcam:~# mender --log-level debug --log-file /data/mender_install.log install /data/jetcam-image-minimal-jetson-xavier-nx-devkit-emmc.mender 
Installing Artifact of size 123020800...
.............................................................. - 100 %
Use -commit to update, or -rollback to roll back the update.
At least one payload requested a reboot of the device it updated.

Also, the produced log:
mender_install.log

It doesn't seem to have failed, from the look of it :/

from tegra-demo-distro.

Which branch are you using?

dunfell

from tegra-demo-distro.

And also check if the update actually succeeded... if the boot failed, it would fallback to the old partition.

As it does fallback to the old partition, I guess it failed to boot to the other one. But where should I look for the actual error message ? dmesg does not give me much (nothing out of the ordinary) information.

from tegra-demo-distro.

I don't see the ArtfifactInstall_Leave_80_bl-update script getting executed. That script is the one that informs the bootloader of the slot switch (as well as updating the bootloader in the target slot).

from tegra-demo-distro.

Indeed. It doesn't seem to be present in the .mender file either...

from tegra-demo-distro.

Check your build setup... that script gets deployed by the tegra-state-scripts recipe, and it sounds like that isn't getting built for some reason.

from tegra-demo-distro.