Ota update Failer in jetpack 5.1.2

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

I’m using Jetson orin NX on jetson xavier Nx carrier board. I flash the carrier board using this command
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 external

I generated an ota image and tried to update.
ota generation command :
sudo -E ROOTFS_AB=1 TARGET_BSP=$WORKDIR/Linux_for_Tegra ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 jetson-orin-nano-devkit R35-4

While trying to do the update it’s showing this error :

sudo ./nv_ota_start.sh /ota/ota_payload_package.tar.gz
Command: ./nv_ota_start.sh /ota/ota_payload_package.tar.gz
Current rootfs is on /dev/nvme0n1
init_ota_log /ota_log
Create log file at /ota_log/ota_20230315-154503.log
OTA_LOG_FILE=/ota_log/ota_20230315-154503.log
Extract /ota/ota_payload_package.tar.gz
update_nv_boot_control_in_rootfs /ota_work
Warning: Cannot get compatible board name.
3767-000-0000–1–p3509-a02+p3767-0000-
Info. Installing mtdblock.
Info. Active boot storage: nvme0n1
Info. Legacy mode: false
TNSPEC 3767-300-0000-K.1-1-1-p3509-a02+p3767-0000-
COMPATIBLE_SPEC 3767-000-0000–1–p3509-a02+p3767-0000-
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–p3509-a02+p3767-0000-.
Info. Uninstalling mtdblock.
check_prerequisites
decompress_ota_package ota_package.tar /ota_work
decompress_ota_package: start at Wed 15 Mar 2023 03:45:39 PM UTC
Sha1 checksum for /ota_work/ota_package.tar (c2fa7751f15dc57e3707aeb26902109192c1e00e) matches
decompress_ota_package: end at Wed 15 Mar 2023 03:45:57 PM UTC
nv_ota_update_without_layout_change.sh
Command: nv_ota_update_without_layout_change.sh
check_target_board /ota_work TARGET_BOARD
The board name in OTA package(jetson-orin-nano-devkit) does not match current board(p3509-a02+p3767-0000)
Failed to run “check_target_board /ota_work TARGET_BOARD”

3

Hi,

In your flash command, you flashed the board without using ROOTFS_AB=1 and then set the OTA command with it, which is not supported.
Additionally, the board configuration jetson-orin-nano-devkit in your OTA command is incorrect. Please use p3509-a02+p3767-0000 instead. For example:

sudo -E TARGET_BSP=$WORKDIR/Linux_for_Tegra ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 p3509-a02+p3767-0000 R35-4

Thanks.

4

@DavidDDD Tried the above command but couldn’t generate the OTA image
got error: Linux_for_Tegra/tools/ota_tools/version_upgrade/ota_validate_params.sh: line 75: P3509_A02+P3767_0000_R35_4_ALIAS: invalid variable name

5

One more question to confirm.
Is your Xavier NX a dev kit or the custom carrier board?

Thanks

6

@DavidDDD Custom carrier board

7

Hi,

In a custom carrier board, you should verify that it can be successfully flashed with the target BSP first.

Thanks

8

@DavidDDD
Hi,
I was able to successfully flash the target with this command :

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 external
9

@DavidDDD
Hi,
What happens internally when we flash the board with different board name lets say in this case when I use p3509-a02+p3767-0000 and jetson-orin-nano-devkit

10

Have you successfully flashed JetPack 5.1.2 on your Orin NX

different board name catch different configure like device tree

Thanks

12

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