OTA tools: broken support of AGX Xavier 64Gb

pim_pam · March 2, 2025, 4:56pm

Latest OTA tools (R35.6.0) that supports Xavier AGX fails to apply OTA update on 64gb xavier version:

Command: ./nv_ota_start.sh /dev/mmcblk0 /home/jetuser/ota_payload_package.tar.gz
Current rootfs is on /dev/mmcblk0
init_ota_log /ota_log
Creating log dir at /ota_log
Create log file at /ota_log/ota_20250222-100405.log
OTA_LOG_FILE=/ota_log/ota_20250222-100405.log
Extract /home/jetuser/ota_payload_package.tar.gz
update_nv_boot_control_in_rootfs /ota_work
2888-402-0005-G.0-1-2-jetson-agx-xavier-devkit-
check_prerequisites
decompress_ota_package ota_package.tar /ota_work
decompress_ota_package: start at Sat Feb 22 10:04:48 UTC 2025
Sha1 checksum for /ota_work/ota_package.tar (fc0e76ba49e15583e1ad96cc5eb0a52203aa7e68) matches
decompress_ota_package: end at Sat Feb 22 10:05:10 UTC 2025
nv_ota_update_with_layout_change.sh /dev/mmcblk0
Command: nv_ota_update_with_layout_change.sh /dev/mmcblk0
check_bsp_version /ota_work BASE_VERSION
check_target_board /ota_work TARGET_BOARD
set_msi_emmc_min_size jetson-agx-xavier-devkit MSI_EMMC_MIN_SIZE
ota_check_rollback /ota_work jetson-agx-xavier-devkit R32-7 /dev/mmcblk0
OTA_PACKAGE version: branch:35 revision:6.0 major.minor:6.0
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB, 8.0 MiB) copied, 2.45499 s, 3.4 MB/s
boot_device_size=8388608
VER_b's offset is 2203648 and size is 65536
VER's offset is 2269184 and size is 65536
VER_b version: branch:32 revision:7.5 major.minor:7.5
VER version: branch:32 revision:7.5 major.minor:7.5
Check BCT/MB1/MB1_BCT partiton for fresh OTA
Checking BCT partition
Checking MB1 partition
Checking MB1_BCT partition
ver_check_res=0
ota_choose_images /ota_work
COMPATIBLE_SPEC=2888-402-0005-G.0-1-2-jetson-agx-xavier-devkit-
TEGRA_CHIPID=0x19
_BOARD_SPEC_NAME=2888-402-0005-G.0
No image is found for compatible SPEC 2888-402-0005-G.0
Failed to call "copy_board_spec_dep_files /ota_work/internal_device"
Failed to run "ota_choose_images /ota_work"

Could you fix it please? It seems, that problem exist for both 0004 and 0005.

Also, I succesfully applied OTA update with this workaround:

--- a/ota_tools/version_upgrade/ota_multi_board_specs.sh
+++ b/ota_tools/version_upgrade/ota_multi_board_specs.sh
@@ -61,6 +61,9 @@ construct_board_spec_name()
        # board_spec_name=${boardid}-${boardver}-${boardsku}-${boardrev}
        # For example, for jetson-agx-xavier-devkit, board_spec_name can be 2888-400-0001-D.0
        # or 2888-400-0001-E.0.
+       if [ "${boardsku}" == "0005" ]; then
+               boardrev=""
+       fi
        name="${boardid}-${boardver}-${boardsku}-${boardrev}"
        eval "${board_spec_name}=${name}"
        return 0

KevinFFF · March 3, 2025, 12:54am

Hi pim_pam,

Are you using the devkit or custom board for AGX Xavier?
What’s you L4T release before update? (i.e. are you trying to update from r35.6.0 to r35.6.0)

Would you like to perform image-based OTA update for each partitions including rootfs? Or you just want to update bootloader through capsule update?

Please also share the result of the following command on your board.

$ sudo cat /etc/nv_boot_control.conf

pim_pam · March 3, 2025, 7:36am

Hi! It is custom board with 64gb xavier module, and I am trying to update from 32.7.5 to 35.6.0, all partitions including rootfs.

$ cat /etc/nv_boot_control.conf
TNSPEC 2888-402-0005-G.0-1-2-jetson-agx-xavier-devkit-
COMPATIBLE_SPEC 2888-402-0005-G.0-1-2-jetson-agx-xavier-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY true
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1

Also, just for information, on 16Gb devkit OTA works without any problems, and 16gb module on custom board also OK.

pim_pam · March 3, 2025, 7:43am

from log above, OTA scripts get this SPEC from nv_boot_control.conf:

_BOARD_SPEC_NAME=2888-402-0005-G.0
No image is found for compatible SPEC 2888-402-0005-G.0

but generated ota_package.tar has only these directories for 0005, with null boardrev:

# tar tf ota_package.tar | grep '2888-402-0005.*\/$'
./internal_device/images-R32x-R35i/2888-402-0005-/
./internal_device/images-R35-ToT/2888-402-0005-/
./internal_device/images-R35A-R35i/2888-402-0005-/

pim_pam · March 4, 2025, 9:05pm

sorry, I answered not in reply…

KevinFFF · March 7, 2025, 6:17am

Do you mean the issue is specific to AGX Xavier 64GB(SKU5)?

And there’s no issue after you add this line in ota_multi_board_specs.sh?

Could you elaborate on this? Do you mean something missing for SKU5 in OTA payload?

I would also like to check the full log when you generate the OTA payload for 2888-0005.

pim_pam · March 8, 2025, 9:16am

yes

And there’s no issue after you add this line in ota_multi_board_specs.sh ?

yes

pim_pam · March 8, 2025, 9:47am

generate-ota.log (944.7 KB)

Do you mean something missing for SKU5 in OTA payload?

I am not expert in your code :) but I think, payload is fine, but… there is a bug in “using” this payload.

In ota_payload_package.tar.gz → ota_package.tar these directories are generated:

./internal_device/images-*/2888-400-0001-D.0
./internal_device/images-*/2888-400-0001-E.0
./internal_device/images-*/2888-400-0004-
./internal_device/images-*/2888-402-0005-

but applying payload mistakenly tries to using 2888-402-0005-G.0 directory instead of 2888-402-0005-

KevinFFF · March 10, 2025, 9:35am

It seems there’s the bug for AGX Xavier SKU5.

Could you modify the following line of /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh in your board ?

@@ -251,7 +251,11 @@ update_jetson_xavier_spec () {
         board_ver="400"
         return 0
     fi
-
+    if [[ "${board_sku}" == "0005" ]]; then
+        board_rev=""
+        board_ver="402"
+        return 0
+    fi
     if [[ "${board_ver}" == "400" ]]; then
         if [[ "${board_rev}" == "D.0" || "${board_rev}" < "D.0" ]]; then
             board_rev="D.0"

After rebooting the board, please share the result of the following command on your board.

$ cat /etc/nv_boot_control.conf

If its COMPATIBLE_SPEC becomes 2888-402-0005--1-2-jetson-agx-xavier-devkit-, then you can try using the OTA payload you generated before to update the board.

pim_pam · March 13, 2025, 1:07pm

yes, COMPATIBLE_SPEC changed:

$ grep -A 15 'update_jetson_xavier_spec ()' /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh
update_jetson_xavier_spec () {
    if [[ "${board_sku}" == "0004" ]]; then
        board_rev=""
        board_ver="400"
        return 0
    fi

    if [[ "${board_sku}" == "0005" ]]; then
        board_rev=""
        board_ver="402"
        return 0
    fi

    if [[ "${board_ver}" == "400" ]]; then
        if [[ "${board_rev}" == "D.0" || "${board_rev}" < "D.0" ]]; then
            board_rev="D.0"
$ cat /etc/nv_boot_control.conf
TNSPEC 2888-402-0005-G.0-1-2-jetson-agx-xavier-devkit-
COMPATIBLE_SPEC 2888-402-0005--1-2-jetson-agx-xavier-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY true
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1

KevinFFF · March 13, 2025, 1:09pm

Please also modify those lines in file of you BSP package(<Linux_for_Tegra>/rootfs/opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh) and generate OTA payload again.

pim_pam · March 13, 2025, 4:11pm

Please also modify those lines in file of you BSP package(<Linux_for_Tegra>/rootfs/opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh) and generate OTA payload again.

done, ota update from 32.7.5 to 35.6.0 successfully finished, thanks.

Is there any chance to have update with fixed bug soon?

KevinFFF · March 14, 2025, 7:15am

Thanks for your update.
We are working on fixing this issue with internal, it may be fixed in the next release.
Before that, please take above modification as WA for AGX Xavier SKU5.

pim_pam · March 14, 2025, 7:29am

Thanks!

Topic		Replies	Views
Can't find matching TN Spec in OTA Blob! Jetson AGX Xavier ota	20	817	July 3, 2023
How to OTA update from JP4.6.2 to JP5.1.X Jetson AGX Xavier boot , ota	7	903	November 20, 2023
Image-Based OTA Failed Jetson AGX Xavier reflash	33	880	September 11, 2023
OTA fails on Nx-devkit when system is installed on nvme Jetson Xavier NX ota	10	1704	March 10, 2022
Questions about Image based OTA update Jetson AGX Xavier ota	23	2349	March 2, 2022
ROOTFS AB OTA for SSD with Increased size on Xavier NX emmc Jetson Xavier NX security , ota	52	108	March 17, 2025
OTA upgrade from JP 4.3 to JP 4.6.1 fails Jetson AGX Xavier nvbugs , ota	9	1205	June 1, 2022
OTA bricks Jetson AGX Xavier (industrial) when writing SMD partitions without any checks Jetson AGX Xavier security , ota	7	570	November 16, 2023
JetPack 4 to JetPack 5 update with A/B rootfs enabled without booting into recovery partition and/or without layout change Jetson AGX Xavier security	19	702	March 12, 2024
AGX Xavier image based Ota update process never starts from nvme Jetson AGX Xavier ota	23	676	November 29, 2023

OTA tools: broken support of AGX Xavier 64Gb

Related topics