We download Jetson Linux 35.1 BSP and its sample Root FS on a host PC. And then we flash our Jetson AGX Orin Developer Kit which now contains # R35.
Finally, we add and remove files on sample Root FS downloaded previously on host PC. And then we generate a newly system.img file after running from our host sudo ./flash.sh --no-flash ${BOARD} mmcblk0p1. Thus, we copy both newly generated system.img and OTA tools on our Jetson AGX Orin Developer kit target running # R35 and then we run
./nv_ota_rootfs_updater.sh -p /dev/mmcblk0p1 -d ~/work ~/work/system.img
But we get error below:
The rootfs image ~/work/system.img is invalid
Failed to run “update_rootfs_partition ~/work/system.img /dev/mmcblk0p1 ~/work”
Note: We do not want to upgrade a below L4T version to a higher. But we want to be able to add/remove files from a downloaded sample FS from an ‘alpha-version’ of a L4T and bring changes on a Jetson AGX Orin target running this # ‘alpha-version’ of L4T. Insist that trigger should be done within the Jetson AGX Orin device.
Thank you for helping us if you understand what we want.
hello mndiaye,
please refer to developer guide, Preparing for an Image-Based OTA Update.
please check you’ve perform the steps on the Host Machine and also Jetson Device.
thanks
Hello Jerry, the link you provided to us is for upgrading a Jetson module from a lower L4T to a higher one’s. we said in our note that we want to run for example L4T 35.1 on a Jetson Orin Module. Then we add/remove files from our host PC which contains L4T 35.1 BSP and FS. Finally, trigger update/push changes within Jetson Orin. Please check Updating the Rootfs Partition with a Customized Updater and Image. Then as image example it’s an system.img.
If you understand what we want do you know how be can handle it? As we repeat, we do not want an upgrade. But just update same L4T version with custom changes while we are in a Jetson module.
Hi mndiaye,
Please share your generate OTA payload package commands.
Hi @carolyuu, when we execute command below to generate OTA payload:
sudo ./tools/ota_tools/version_upgrade/build_base_recovery_image.sh jetson-agx-orin-devkit R35-1 ~/JetsonLinux35-1/Linux_for_Tegra/ ~/JetsonLinux35-1/Linux_for_Tegra/rootfs/ ~/JetsonLinux35-1/Linux_for_Tegra/
we get error below:
Target board(JETSON_AGX_ORIN_DEVKIT) and base version(R35_1) is not supported
Failed to run "ota_validate_params jetson-agx-orin-devkit R35-1 internal
As we said earlier we are running R35_1 on a Jetson AGX Orin Devkit. Then we made changes on development PC. The pending question is what file to generate and bring it on our Jetson AGX Orin for update. Still OTA not working.
The last thing we do is to generate the system.img as follow:
sudo ./flash.sh --no-flash jetson-agx-orin-devkit mmcblk0p1
But when we try Updating the Rootfs Partition with a Customized Updater and Image, it does not work. Thus, how can we handle this situation?
Thank you,
Hi mndiaye,
The Image-based OTA is not support AGX Orin.
Hello @carolyuu,
-
Do you understand what we want? This feature is really important for our commercial product.
-
Do you know if how we want to use OTA will never be supported on AGX Orin?
-
If you understand what we want, what are our alternatives?
-
Recall we want to base our solution on Nvidia tools. But sometime we want a continuous development of our commercial product based on a specific L4T. How can you help us?
Hi,
Image-based OTA update is not enabled for Orin on Jetpack 5.0.2. We are working on it. For Xavier, it fails to do OTA update from Jetpack 4.6 → Jetpack 4.6.2 → Jetpack 5.0.2. And we are developing the OTA update from from Jetpack 4.6 → Jetpack 4.6.2 → next Jetpack 5.1. After we enable it for Xavier, we will then enable image-based OTA update for Orin.
Hello @DaneLLL,
Can you share the roadmap about when image-based OTA update for Orin will be enabled?
Do you think that OTA will work from Jetpack 4.6 → Jetpack 4.6? We assume here, we are in a situation where a developer make continuous change to unique Jetpack, for example 4.6.
Hi,
For Orin, we are planning to support upgrading from Jetpack 5.1 to any version greater than 5.1. The support will be through OTA tools, so customers/forum users can go to production with Jetpack 5.1.
Hi @DaneLLL, it will be nice to perform upgrade from Jetpack 5.1 to any version greater than 5.1. But how do we perform update from Jetpack let us say 5.1 to 5.1. You talk about an upgrade from Jetpack 5.1 to any version greater than 5.1. In other word will you support an upgrade from Jetpack 5.1 to any version greater or equal 5.1?
Hi,
It shall be ready on Jetpack 5.2. So we can upgrade from Jetpack 5.2 to any version greater or equal 5.2.
I also need the functionality to perform updates of the rootfs via OTA without changing SDK versions. I want to use mender to perform the OTA upgrade. Mender had a description how to do that with R32.6 (Nvidia Jetson L4T Integration - #7 by lramirez - Debian family - Mender Hub), but this procedure doesn’t work anymore.
According to your answer, performing a rootfs update only should be supported in 5.2. Can you tell me when it will be available?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.