Trying OTA upgrade from 35.3.1 to 35.5 on Orin NX and got these errors:

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

I followed the instructions here:

https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/SD/SoftwarePackagesAndTheUpdateMechanism.html#updating-from-the-nvidia-apt-server

So I edited the file and mentioned from 35.3 → 35.5.

…but I end up with this (the same if I run it again).

oliver@Jetson-Dev:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  libavformat58 libavfilter7 libswresample3 libzmq5 iperf3 libswresample-dev
  libpostproc55 libavutil-dev libavcodec-dev libavcodec58 libavutil56
  libswscale5 libopenexr24 libsdl2-2.0-0 libmysofa1 libiperf0 python3-scipy
Learn more about Ubuntu Pro at https://ubuntu.com/pro
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up nvidia-l4t-kernel (5.10.192-tegra-35.5.0-20240219203809) ...
Using the existing boot entry 'primary'
Warning: Cannot get compatible board name.
3767--0001--1--p3509-a02+p3767-0000-
Info. Active boot storage: nvme0n1
Info. Legacy mode: false
TNSPEC 3767-300-0001-N.2-1-1-p3509-a02+p3767-0000-
COMPATIBLE_SPEC 3767--0001--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--0001--1--p3509-a02+p3767-0000-.
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):
 installed nvidia-l4t-kernel package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nvidia-l4t-kernel-headers:
 nvidia-l4t-kernel-headers depends on nvidia-l4t-kernel (= 5.10.192-tegra-35.5.0-20240219203809); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-headers (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-jetson-io:
 nvidia-l4t-jetson-io depends on nvidia-l4t-kernel (>> 5.10.192-tegra-35.5-0); however:
  Package nvidia-l4t-kernel is not configured yet.
 nvidia-l4t-jetson-io depends on nvidia-l4t-kernel (<< 5.10.192-tegra-35.6-0); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-jetson-io (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up error from a previous failure.
                                                                                                            No apport report written because the error message indicates it's a follow-up error from a previous fai
lure.
     dpkg: dependency problems prevent configuration of nvidia-l4t-display-kernel:
 nvidia-l4t-display-kernel depends on nvidia-l4t-kernel (= 5.10.192-tegra-35.5.0-20240219203809); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-display-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-kernel-dtbs:
 nvidia-l4t-kernel-dtbs depends on nvidia-l4t-kernel (= 5.10.192-tegra-35.5.0-20240219203809); however:
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package nvidia-l4t-kernel-dtbs (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports has already been reached
                                                                    No apport report written because MaxReports has already been reached
                                                                                                                                        Errors were encountered while processing:
 nvidia-l4t-kernel
 nvidia-l4t-kernel-headers
 nvidia-l4t-jetson-io
 nvidia-l4t-display-kernel
 nvidia-l4t-kernel-dtbs
E: Sub-process /usr/bin/dpkg returned an error code (1)

Is there a solution?

2

I’ve seen some commands to do weird stuff with the disk partitions,. mentioned in this solution:

So maybe I need something similar?

Here is my disk layout:

oliver@Jetson-Dev:~$ sudo parted /dev/nvme0n1 print
Model: FORESEE VP1000F128G (nvme)
Disk /dev/nvme0n1: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                       Flags
 2      20.5kB  67.1MB  67.1MB               A_kernel                   msftdata
 3      67.1MB  67.6MB  459kB                A_kernel-dtb               msftdata
 4      67.6MB  101MB   33.6MB               reserved_for_chain_A_user  msftdata
 5      101MB   168MB   67.1MB               B_kernel                   msftdata
 6      168MB   169MB   459kB                B_kernel-dtb               msftdata
 7      169MB   202MB   33.6MB               reserved_for_chain_B_user  msftdata
 8      202MB   286MB   83.9MB               recovery                   msftdata
 9      286MB   287MB   524kB                recovery-dtb               msftdata
10      287MB   601MB   315MB                RECROOTFS                  msftdata
11      601MB   668MB   67.1MB  fat32        esp                        boot, esp
12      668MB   752MB   83.9MB               recovery_alt               msftdata
13      752MB   753MB   524kB                recovery-dtb_alt           msftdata
14      753MB   820MB   67.1MB               esp_alt                    msftdata
 1      820MB   128GB   127GB   ext4         APP                        msftdata
4

Hi oviano,

Are you using the devkit or custom board for Orin NX?

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

$ cat /etc/nv_tegra_release
$ cat /etc/nv_boot_control.conf
5

This is a reComputer 401 board.

oliver@Jetson-Dev:~$ cat /etc/nv_tegra_release
# R35 (release), REVISION: 5.0, GCID: 35550185, BOARD: t186ref, EABI: aarch64, DATE: Tue Feb 20 04:46:31 UTC 2024
oliver@Jetson-Dev:~$ cat /etc/nv_boot_control.conf
TNSPEC 3767-300-0001-N.2-1-1-p3509-a02+p3767-0000-
COMPATIBLE_SPEC 3767--0001--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
6

It seems you are using the custom carrier board so that debian based OTA would not work for your board.

Please use the custom BSP package to perform the image-based OTA update.

7

Ok no problem.

9

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