current system: JetPack 6.0 Jetson AGX Orin Series, Jetson Orin NX Series, Jetson Orin Nano Series [L4T 36.3]
target system:JetPack 6.2.1 Jetson AGX Orin Series, Jetson Orin NX Series, Jetson Orin Nano Series [L4T 36.4.4]
how to only update bootloader kernel ,not rootfs?
*** Please note that this reply is generated by LLM automatically ***
To upgrade the Jetson Orin Nano from JetPack 4.6 (L4T 32.6.1) to JetPack 6.2.1 (L4T 34.1), you can follow these steps:
nvidia-jetpack and it requires an internet connection, you can use the same method to upgrade your system.Comparison of JetPack versions:
Upgrade steps:
nvidia-jetpack.Note: Make sure to back up any important data on your Jetson Orin Nano before upgrading, as the upgrade process may erase all data on the device.
Comparison of Jetson modules:
In summary, upgrading from JetPack 4.6 (L4T 32.6.1) to JetPack 6.2.1 (L4T 34.1) on Jetson Orin Nano Series will provide you with the latest features, security patches, and performance improvements. The upgrade process is straightforward using the nvidia-jetpack command, and you can expect improved performance and capabilities on your Jetson Orin Nano.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
but the actual working environment does not have an Internet connection,can not use nvidia-jetpack, Is there a feasible solution to achieve offline upgrade?
Hello @gengqi_yz,
You could create a OTA payload and deploy it via USB.
Would something like that work for you ?
best regards,
Andrew
Embedded Software Engineer at ProventusNova
I will suggest to first clone the rootfs of the existing system. If anything goes wrong, then you can try again.
Btw, besides the OTA payload mentioned, you can “download now, install later” to a host PC. This could be something like a laptop, which is updated this way prior to moving to a location without networking.
run ota steps:
1.sudo -E ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 -S 24GiB jetson-orin-nano-devkit R36-3
2.sudo ./nv_ota_start.sh ./ota_payload_package.tar.gz
question: It will overwrite the original rootfs, causing the private configuration and data in the original file system to be lost. How can we not lose the private configuration and data of the original rootfs?
You can clone first. Can you mount the NVMe on a different Linux computer? If so, then a simple dd command can give you an exact copy useful for recreating.
rsync is an option as well, although it differs in several ways. If you have sufficient storage, then rsync can be used locally as well as over ssh (and no Internet won’t matter if you have a second computer right there; either the USB virtual wired network would work, or a locally attached device such as a USB SATA drive).
Many parts of the flash directory’s content is used verbatim in creating the image to be flashed. Parts which might be edited are due to the flash target specification, and includes the kernel, device tree, and any boot config. You can later copy those over from a clone if you desire, but much of this can be preserved without issue by editing the “Linux_for_Tegra/rootfs/”. As an example, my ssh permissions, user accounts, ssh keys, host keys, bash aliases, so on, are in my “rootfs/”, and every flash has that right from the start.
Note that what really works best is that after you’ve installed a working system, and it is configured how you want, that a clone is a good idea because this can be used either directly during a flash or via copy into the “rootfs/” (direct use ignores “rootfs/” and is a bit-for-bit exact flash of your clone).
If your rootfs is on an NVMe, then it is far simpler to just mount it on another computer and use dd instead of cloning while it is on the Jetson. If you want dd information just ask.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.