Fail to install jetpack to Jetson xavier NX with sdkmanager

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
,
1

I failed to install jetpack through sdkmanager.
I don’t know how to fix this.

Please help me.

host machine : Ubuntu 20.04 PC

device : Jetson xavier NX

16:14:20 INFO: VPI on Host - host: Hit:11 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease

16:14:20 INFO: VPI on Host - host: Hit:12 Index of /compute/cuda/repos/ubuntu2004/x86_64 InRelease

16:14:20 INFO: VPI on Host - host: Hit:13 https://dl.google.com/linux/chrome/deb stable InRelease

16:14:20 INFO: VPI on Host - host: Hit:14 Index of /ubuntu focal InRelease

16:14:20 INFO: VPI on Host - host: Hit:15 Index of /ubuntu focal-security InRelease

16:14:21 INFO: VPI on Host - host: Hit:16 Index of /ubuntu focal-updates InRelease

16:14:21 INFO: VPI on Host - host: Hit:17 Index of /graphics-drivers/ppa/ubuntu focal InRelease

16:14:21 INFO: VPI on Host - host: Hit:18 Index of /ubuntu focal-backports InRelease

16:14:23 INFO: VPI on Host - host: Reading package lists…

16:14:23 ERROR: VPI on Host - host: E: The repository ‘cdrom://Ubuntu 20.04.5 LTS Focal Fossa - Release amd64 (20220831) focal Release’ does not have a Release file.

16:14:23 ERROR: VPI on Host - host: W: GPG error: file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7F08EFB052C1F678

16:14:23 ERROR: VPI on Host - host: E: The repository ‘file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease’ is not signed.

16:14:23 ERROR: VPI on Host - host: Error: safe apt install failed: sudo apt-get update , exit code: 100, retry number: 2

16:14:23 INFO: VPI on Host - host: will sleep 20 seconds before next attempt

16:14:43 INFO: VPI on Host - host: Ign:1 cdrom://Ubuntu 20.04.5 LTS Focal Fossa - Release amd64 (20220831) focal InRelease

16:14:43 ERROR: VPI on Host - host: Err:2 cdrom://Ubuntu 20.04.5 LTS Focal Fossa - Release amd64 (20220831) focal Release

16:14:43 INFO: VPI on Host - host: Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs

16:14:43 INFO: VPI on Host - host: Get:3 file:/var/cuda-repo-cross-aarch64-ubuntu2004-11-4-local InRelease [1,575 B]

16:14:43 INFO: VPI on Host - host: Get:4 file:/var/cuda-repo-ubuntu2004-11-4-local InRelease [1,575 B]

16:14:43 INFO: VPI on Host - host: Get:5 file:/var/cuda-repo-ubuntu2004-12-1-local InRelease [1,572 B]

16:14:43 INFO: VPI on Host - host: Get:3 file:/var/cuda-repo-cross-aarch64-ubuntu2004-11-4-local InRelease [1,575 B]

16:14:43 INFO: VPI on Host - host: Get:6 file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease [1,572 B]

16:14:43 INFO: VPI on Host - host: Get:4 file:/var/cuda-repo-ubuntu2004-11-4-local InRelease [1,575 B]

16:14:43 INFO: VPI on Host - host: Get:5 file:/var/cuda-repo-ubuntu2004-12-1-local InRelease [1,572 B]

16:14:43 INFO: VPI on Host - host: Get:6 file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease [1,572 B]

16:14:43 INFO: VPI on Host - host: Hit:7 Index of linux/ubuntu/ focal InRelease

16:14:43 ERROR: VPI on Host - host: Err:6 file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease

16:14:43 INFO: VPI on Host - host: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7F08EFB052C1F678

16:14:44 INFO: VPI on Host - host: Hit:8 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/amd64 InRelease

16:14:44 INFO: VPI on Host - host: Hit:9 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64 InRelease

16:14:44 INFO: VPI on Host - host: Hit:10 Index of /repos/edge/ stable InRelease

16:14:44 INFO: VPI on Host - host: Hit:11 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 InRelease

16:14:44 INFO: VPI on Host - host: Hit:12 https://dl.google.com/linux/chrome/deb stable InRelease

16:14:44 INFO: VPI on Host - host: Hit:13 Index of /compute/cuda/repos/ubuntu2004/x86_64 InRelease

16:14:44 INFO: VPI on Host - host: Hit:14 Index of /ubuntu focal-security InRelease

16:14:44 INFO: VPI on Host - host: Hit:15 Index of /ubuntu focal InRelease

16:14:44 INFO: VPI on Host - host: Hit:16 Index of /graphics-drivers/ppa/ubuntu focal InRelease

16:14:44 INFO: VPI on Host - host: Hit:17 Index of /ubuntu focal-updates InRelease

16:14:45 INFO: VPI on Host - host: Hit:18 Index of /ubuntu focal-backports InRelease

16:14:46 INFO: VPI on Host - host: Reading package lists…

16:14:46 ERROR: VPI on Host - host: E: The repository ‘cdrom://Ubuntu 20.04.5 LTS Focal Fossa - Release amd64 (20220831) focal Release’ does not have a Release file.

16:14:46 ERROR: VPI on Host - host: W: GPG error: file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7F08EFB052C1F678

16:14:46 ERROR: VPI on Host - host: E: The repository ‘file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease’ is not signed.

16:14:46 ERROR: VPI on Host - host: Unhandled error when running sudo apt-get update : E: The repository ‘cdrom://Ubuntu 20.04.5 LTS Focal Fossa - Release amd64 (20220831) focal Release’ does not have a Release file.;W: GPG error: file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7F08EFB052C1F678;E: The repository ‘file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease’ is not signed.;

16:14:46 INFO: VPI on Host - host: [ Package Install Finished with Error ]

16:14:46 INFO: VPI on Host - host: [host] [ 3.03 MB released. Disk Avail: 3235.54 GB ]

16:14:46 INFO: VPI on Host - host: [ NV_VPI_HOST_COMP Install took 43s ]

16:14:46 ERROR: VPI on Host - host: command terminated with error

16:14:46 SUMMARY: VPI on Host - host: safe_apt_install failed to run.

16:36:30 INFO: File System and OS - target_image: Hit:13 Index of /compute/cuda/repos/ubuntu2004/x86_64 InRelease

16:36:31 INFO: File System and OS - target_image: Hit:14 Index of /graphics-drivers/ppa/ubuntu focal InRelease

16:36:31 INFO: File System and OS - target_image: Hit:15 Index of /ubuntu focal InRelease

16:36:31 INFO: File System and OS - target_image: Get:16 Index of /ubuntu focal-security InRelease [114 kB]

16:36:31 INFO: File System and OS - target_image: Get:17 Index of /ubuntu focal-updates InRelease [114 kB]

16:36:32 INFO: File System and OS - target_image: Get:18 Index of /ubuntu focal-backports InRelease [108 kB]

16:36:49 INFO: File System and OS - target_image: Reading package lists…

16:36:49 ERROR: File System and OS - target_image: E: The repository ‘cdrom://Ubuntu 20.04.5 LTS Focal Fossa - Release amd64 (20220831) focal Release’ does not have a Release file.

16:36:49 ERROR: File System and OS - target_image: W: GPG error: file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7F08EFB052C1F678

16:36:49 ERROR: File System and OS - target_image: E: The repository ‘file:/var/nv-tensorrt-local-repo-ubuntu2004-8.6.0-cuda-12.0 InRelease’ is not signed.

16:36:49 INFO: File System and OS - target_image: Reading package lists…

16:36:49 INFO: File System and OS - target_image: Building dependency tree…

16:36:49 INFO: File System and OS - target_image: Reading state information…

16:36:49 INFO: File System and OS - target_image: lz4 is already the newest version (1.9.2-2ubuntu0.20.04.1).

16:36:49 INFO: File System and OS - target_image: The following packages were automatically installed and are no longer required:

16:36:49 INFO: File System and OS - target_image: cuda-cccl-12-1 cuda-command-line-tools-12-1 cuda-compiler-12-1

16:36:49 INFO: File System and OS - target_image: cuda-cudart-12-1 cuda-cudart-dev-12-1 cuda-cuobjdump-12-1 cuda-cupti-12-1

16:36:49 INFO: File System and OS - target_image: cuda-cupti-dev-12-1 cuda-cuxxfilt-12-1 cuda-documentation-12-1

16:36:49 INFO: File System and OS - target_image: cuda-driver-dev-12-1 cuda-gdb-12-1 cuda-libraries-12-1

16:36:49 INFO: File System and OS - target_image: cuda-libraries-dev-12-1 cuda-nsight-12-1 cuda-nsight-compute-12-1

16:36:49 INFO: File System and OS - target_image: cuda-nsight-systems-12-1 cuda-nvcc-12-1 cuda-nvdisasm-12-1

16:36:49 INFO: File System and OS - target_image: cuda-nvml-dev-12-1 cuda-nvprof-12-1 cuda-nvprune-12-1 cuda-nvrtc-12-1

16:36:49 INFO: File System and OS - target_image: cuda-nvrtc-dev-12-1 cuda-nvtx-12-1 cuda-nvvp-12-1 cuda-opencl-12-1

16:36:49 INFO: File System and OS - target_image: cuda-opencl-dev-12-1 cuda-profiler-api-12-1 cuda-sanitizer-12-1

16:36:49 INFO: File System and OS - target_image: cuda-toolkit-12-1 cuda-toolkit-12-1-config-common

16:36:49 INFO: File System and OS - target_image: cuda-toolkit-12-config-common cuda-tools-12-1 cuda-visual-tools-12-1

16:36:49 INFO: File System and OS - target_image: gds-tools-12-1 libcublas-12-1 libcublas-dev-12-1 libcufft-12-1

16:36:49 INFO: File System and OS - target_image: libcufft-dev-12-1 libcufile-12-1 libcufile-dev-12-1 libcurand-12-1

16:36:49 INFO: File System and OS - target_image: libcurand-dev-12-1 libcusolver-12-1 libcusolver-dev-12-1 libcusparse-12-1

16:36:49 INFO: File System and OS - target_image: libcusparse-dev-12-1 libnpp-12-1 libnpp-dev-12-1 libnvjitlink-12-1

16:36:49 INFO: File System and OS - target_image: libnvjitlink-dev-12-1 libnvjpeg-12-1 libnvjpeg-dev-12-1 libnvvm-samples-12-1

16:36:49 INFO: File System and OS - target_image: nsight-compute-2023.1.0 nsight-systems-2023.1.2

16:36:49 INFO: File System and OS - target_image: Use ‘sudo apt autoremove’ to remove them.

16:36:50 INFO: File System and OS - target_image: 0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.

16:36:50 INFO: File System and OS - target_image: Using rootfs directory of: /home/soynet/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs

16:36:50 INFO: File System and OS - target_image: Installing extlinux.conf into /boot/extlinux in target rootfs

16:36:50 INFO: File System and OS - target_image: /home/soynet/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/nv_tegra/nv-apply-debs.sh

16:36:50 INFO: File System and OS - target_image: Root file system directory is /home/soynet/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs

16:36:50 INFO: File System and OS - target_image: Copying public debian packages to rootfs

16:37:00 INFO: File System and OS - target_image: Skipping installation of nvidia-l4t-dgpu-apt-source_35.3.1-20230319081403_arm64.deb …

16:37:00 INFO: File System and OS - target_image: Skipping installation of nvidia-l4t-dgpu-config_35.3.1-20230319081403_arm64.deb …

16:37:11 INFO: File System and OS - target_image: Start L4T BSP package installation

16:37:11 INFO: File System and OS - target_image: QEMU binary is not available, looking for QEMU from host system

16:37:11 INFO: File System and OS - target_image: ERROR qemu not found! To install - please run: “sudo apt-get install qemu-user-static”

16:37:11 INFO: File System and OS - target_image: [ Package Install Finished with Error ]

16:37:11 INFO: File System and OS - target_image: [host] [ 4.69 GB used. Disk Avail: 3235.53 GB ]

16:37:11 INFO: File System and OS - target_image: [ NV_L4T_FILE_SYSTEM_AND_OS_COMP Install took 2m25s ]

16:37:11 ERROR: File System and OS - target_image: command terminated with error

16:37:11 SUMMARY: File System and OS - target_image: First Error: Installation failed.

3

Hi dkdlatjsh,

Are you using the devkit or custom board for Jetson Nano?

Jetson Nano could only support Jetpack4, which is supported by Ubuntu 16.04 and 18.04. It seems you are using Ubuntu 20.04 as your host PC, it might cause some packages install issue and cause flash failed.

Please get a standalone Ubuntu 18.04 as your host PC to flash the Jetson Nano.

4

No, I’m not using Jetson Nano, I using mini PC with Jetson xavier NX

this is the PC

5

Flash requires a separate host PC with a desktop architecture. Although JetPack/SDK Manager itself would “seem” to work over a somewhat wider range of Ubuntu releases, the Nano itself will require an Ubuntu 18.04 (preferred) or Ubuntu 16.04 host PC.

Note that this particular Nano is an eMMC model, which differs from the development kit which NVIDIA sells (it’s an upgrade over the regular dev kit). This means that the software used for flashing is modified relative to the regular dev kit, and the dev kit is what NVIDIA’s flash software is aimed at. So you need to use the software provided by the manufacturer of that particular Mini PC-A206. Sometimes the instructions will simply be to use NVIDIA’s software after updating a file, but I have no idea what that particular Jetson’s instructions are.

6

I was mean that I have a Ubuntu 20.04 PC for host, and I want to flash other mini PC.
Jetson xavier NX is embedded in that mini PC, so I thought that I can flash it.

7

Your topic was in Jetson Nano category, I’ve moved it to Jetson Xavier NX category.

Okay, It seems Jetson Mini PC-A206 with Jetson Xavier NX module is a custom board with Jetson Xavier NX. You can not use SDK Manager to flash this board due to the custom design different from the devkit from NVIDIA.

Please request your vendor for the custom BSP package first, and use the flash script to flash your board.

8

If a computer has a Jetson of any kind in it, then we would not normally refer to this as a “PC”…this tends to imply amd64/x86_64 architecture, but that might just be a convention on these forums. Perhaps a more correct way to describe this is an Xavier NX with custom carrier board (the chassis surrounding it won’t matter, but the use of a commercial module on a custom carrier board is quite important; custom carrier boards I think tend to use eMMC modules, which development kits don’t have). But it is good to know the “host PC” is Ubuntu 20.04.

As mentioned by @KevinFFF, you need the manufacturer’s software. Jetsons have some software controlled pin layout whereby some pins have multiple functions available, and the layout chosen by the manufacturer is unknown to the NVIDIA software. That’s basically device tree content (a.k.a., firmware). Thus the software the manufacturer provides is usually a slightly modified version of the flash software which NVIDIA uses. Perhaps it differs only in device tree, and so sometimes a third party carrier board manufacturer will simply provide a few patch files to add to the NVIDIA software, but the manufacturer must provide that.

2 Likes
10

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