OTA Update from 5.1.2 to 6.1 using

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Hi,
Im currently building an ota update package to go from 5.1.2 to 6.1. I created the rootfs and created the ota update package using sdkmanager with the following command:

#export base bsp and target bsp variables
export BASE_BSP=/home/nvidia/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
export TARGET_BSP=/home/nvidia/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_TARGETS/Linux_for_Tegra
# Generate OTA package
sudo ROOTFS_AB=1 ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 brla4n-orin-nx R35-4

The package generation works. And the ota update also works when I do it only for 5.1.2. However now im doing it for JP 6.1 and get the following error running the update package on the device (which has 5.1.2 installed):

Command: ./nv_ota_start.sh /ota/ota_payload_package_JP6.tar.gz
Current rootfs is on /dev/nvme0n1
init_ota_log /ota_log
Create log file at /ota_log/ota_20250804-141705.log
OTA_LOG_FILE=/ota_log/ota_20250804-141705.log
Extract /ota/ota_payload_package_JP6.tar.gz
update_nv_boot_control_in_rootfs /ota_work
Warning: Cannot get compatible board name.
3767-000-0000--1--brla4n-orin-nx-
TNSPEC 3767-301-0000-G.1-1-0-brla4n-orin-nx-
COMPATIBLE_SPEC 3767-000-0000--1--brla4n-orin-nx-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
Info: Write TegraPlatformCompatSpec with 3767-000-0000--1--brla4n-orin-nx-.
Info: The esp is already mounted to /boot/efi.
check_prerequisites
decompress_ota_package ota_package.tar /ota_work
decompress_ota_package: start at Mon 04 Aug 2025 02:17:29 PM UTC
Sha1 checksum for /ota_work/ota_package.tar (8db2315bd09716559e94d80278a07d539b96906e) matches
decompress_ota_package: end at Mon 04 Aug 2025 02:17:40 PM UTC
nv_ota_update_without_layout_change.sh
Command: nv_ota_update_without_layout_change.sh
check_target_board /ota_work TARGET_BOARD
get_chip_id CHIP_ID
ota_choose_images /ota_work
COMPATIBLE_SPEC=3767-000-0000--1--brla4n-orin-nx-
TEGRA_CHIPID=0x23
_BOARD_SPEC_NAME=3767-000-0000-
Copy files from ./images-R35-ToT/3767-000-0000-/ to ./images-R35-ToT/
Copy files from ./images-R36-ToT/3767-000-0000-/ to ./images-R36-ToT/
get_rootfs_a_b_enabled ROOTFS_AB_ENABLED ROOTFS_CURRENT_SLOT
ROOTFS_AB_ENABLED=1
ROOTFS_CURRENT_SLOT=0
get_update_slot UPDATE_SLOT
UPDATE_SLOT=B
get_update_control /ota_work UPDATE_BOOTLOADER UPDATE_ROOTFS
UPDATE_BOOTLOADER=1, UPDATE_ROOTFS=1
select_uefi_capsule /ota_work
check_bsp_version /ota_work BASE_VERSION
The version of OTA package(R36-4) does not match the version of current system(R35-4), please check whether the OTA package is correct
Failed to run "check_bsp_version /ota_work BASE_VERSION"

Can you explain the error to me? Is there something I am doing wrong when I want to create the ota package for a major version upgrade?

Thank you for your help.

2

Hello @philipp.schmieder,

I believe this post here might be of help for you.

The error message you are getting:

Warning: Cannot get compatible board name.

Seems to be related to the board configuration you are using to generate the OTA payload.

Please give that blogpost a read and let us know if helps.
Otherwise, we will continue helping you find the cause of the problem.

best regards,
Andrew
Embedded Software Engineer at ProventusNova

3

*** Please note that this reply is generated by LLM automatically ***

I’d be happy to help you with your question.

It appears that you are trying to create an OTA (Over-the-Air) update package for a major version upgrade from JetPack 5.1.2 (JP 5.1.2) to JetPack 6.1 (JP 6.1) on a Jetson Orin NX device. You have successfully created the rootfs and generated the OTA update package using the SDK Manager. However, when you try to apply the update package on a device with JP 5.1.2 installed, you encounter an error.

The error message is not provided in your question, but I can try to help you troubleshoot the issue.

When creating an OTA update package for a major version upgrade, there are a few things to consider:

  1. Compatibility: Make sure that the OTA update package is compatible with the target device and the new version of JetPack. In your case, you are upgrading from JP 5.1.2 to JP 6.1, which is a major version upgrade.
  2. Rootfs: Ensure that the rootfs is properly created and configured for the new version of JetPack. You mentioned that you created the rootfs, but double-check that it is correct.
  3. OTA package generation: Verify that the OTA package is generated correctly using the SDK Manager. You mentioned that the package generation works, but make sure that you are using the correct command and options.
  4. Device compatibility: Ensure that the device is compatible with the new version of JetPack. Check the device’s specifications and ensure that it meets the requirements for JP 6.1.

To troubleshoot the issue, you can try the following:

  1. Check the error message: Provide the exact error message you are seeing, and I can help you understand what it means.
  2. Verify the OTA package: Check the OTA package that you generated to ensure that it is correct and complete.
  3. Check the device’s logs: Check the device’s logs to see if there are any error messages or clues that can help you understand what is going wrong.
  4. Try a different approach: If you are using the SDK Manager to generate the OTA package, try using the l4t_generate_ota_package.sh script instead. This script is provided by NVIDIA and can help you generate the OTA package manually.

In comparison to other Jetson devices, the Jetson Orin NX has similar requirements and constraints when it comes to OTA updates. However, the specific error message you are seeing may be related to the device’s configuration or the OTA package itself.

If you provide more information about the error message and your setup, I can try to help you troubleshoot the issue further.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

Image-based OTA from Jetpack 5.1.2(r35.4.1) to Jetpack 6.1(r36.4.0) directly is not supported.
You have to update from Jetpack 5.1.2(r35.4.1) to Jetpack 5.1.3(r35.5.0) first.

Please refer to the following link for all supported versions which could be updated to Jetpack 6.1.
Updating Jetson Linux with Image-Based Over-the-Air Update

6

That is very unfortunate. Is there any possible way to update a 5.1.2 to 6.1 via a remote update procedure?

7

Hi,

I tried to do a dist-upgrade on my machine using the provided information:

image
image1584×336 25 KB

However I run into the problem that it tells me

TNSPEC 3767-301-0000-G.1-1-1-brla4n-orin-nx-
COMPATIBLE_SPEC 3767-000-0000--1--brla4n-orin-nx-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
Info: Write TegraPlatformCompatSpec with 3767-000-0000--1--brla4n-orin-nx-.
Starting kernel post-install procedure.
Rootfs AB is not enabled.
ERROR. Procedure for A_kernel update FAILED.
Cannot install package. Exiting...
dpkg: error processing package nvidia-l4t-kernel (--configure):

However the system is booted from the nvme drive so the provided info for the emmc is not working for me. Can you guide me through on how to fix it when the system is on a nvme drive?

8

Image-based OTA can be done remotely.
The problem here is that the update from JP5.1.2 to JP6.1 directly is not supported.
Instead, you have to perform image-based OTA twice.
First, JP5.1.2 to JP5.1.3.
Second, JP5.1.3 to JP6.1.
Actually, you can refer to the steps in 3. OTA update from a version earlier than R35.5.0 to the latest R36 version section of Image_based_OTA_Examples.txt.

Debian-based OTA is not supported for the custom carrier board.

10

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