Proper way of updating rootfs in a jetson nano with A/B redundancy enabled

What is the best practices for performing an A/B rootfs update? Following this documentation, I am able to manually generate a rootfs. My ideal path would be to take this and then deploy it to the inactive partition and then call nvbootctrl to switch over the active partition. From my understanding, this should work, correct?

I’ve read about capsules and BUPs, however I’d prefer to stay away from that solution from now because we’d like to adapt our in-house deployment system to update the rootfs for the jetsons only for OTA updates, and do not foresee the need to update jetpack versions, kernels or DTBs.

However, when I do follow this path, after I extract the sample_fs.tar.gz generated by nv_build_samplefs.sh, i just get a blank screen for next boot and never actually see the other partition boot. FWIW, I have validated that my A/B partitioning scheme is setup correctly, as i can swap between the partitions using nvbootcrl (as well as verify that they have been set using the same tool) before I modify either of the rootfs’s.

Is using nv_build_samplefs.sh the preferred method, or should I use the flash tool to take a recovery image of one partition and then use that to flash the other?

hello happyhipposhell,

honestly, it depends-on your own use-case,
for instance, you may see-also readme file, $OUT/Linux_for_Tegra/tools/ota_tools/version_upgrade/Image_based_OTA_Examples.txt for some specific use cases.

This file does not exist in R36.3.0.

But directly addressing my question, there is nothing to indicate that a root file system that is generated from nv_build_samplefs.sh and then copied over to a partition that was previously designated as an A/B filesystem would not work, correct?

Is there any reason i would be seeing the error I shared above, in the third paragraph?

hello happyhipposhell,

you should download [OTA Tools r36.3.0] from jetson-linux-r363 to obtain the tools.
since RootfsA/B is disabled by default, you should creating OTA payload image with ROOTFS_AB=1

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.