Unable to install jetpack 6.1 using SDK

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

I have an Orin nano and installed SDK manager 2.2.0 and are unable to install jetpack 6.0 or 6.1 on the NVME memory.
Need some advice of how to be able to install latest jetpack version.

It is possible to install jetpack 5.1.4 using the SDK but fails when trying to install 6.1. The firmware is upgraded using the SD-card method.
The point of failure is when it have flashed the linux system and waiting for the target to boot up linux and the should install all linux-drivers. The screen remains black.

How can I proceed?
SDK manager: fails
SD-card method: No, I want it on the NVME because it’s faster and I need large amounts of memory.
Upgrade using deb-package: Does not work. it needs L4T 36.x to be able to upgrade.

Here is parts of the log when trying to install jetpack 6.0 (similar with 6.1)
7:13:15 INFO: Flash Jetson Linux - flash: tar: Read checkpoint 10000

17:13:15 INFO: Flash Jetson Linux - flash: tar: Read checkpoint 20000

17:19:17 INFO: Flash Jetson Linux - flash: Flash failure

17:19:17 INFO: Flash Jetson Linux - flash: Either the device cannot mount the NFS server on the host or a flash command has failed. Debug log saved to /tmp/tmp.KZDMhJchNX. You can access the target’s terminal through “sshpass -p root ssh root@fc00:1:1:0::2”

17:19:18 INFO: Flash Jetson Linux - flash: Cleaning up…

17:19:18 ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /home/user/.nvsdkm/replays/scripts/JetPack_6.0_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: 129883 blocks

17:19:18 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]

17:19:18 INFO: Flash Jetson Linux - flash: [host] [ 15.56 GB used. Disk Avail on Partition /dev/mapper/vgubuntu-root: 45.28 GB ]

17:19:18 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 11m23s ]

17:19:18 ERROR: command error code: 11

17:19:18 ERROR: Flash Jetson Linux - flash: command terminated with error

17:19:18 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

17:19:18 SUMMARY: Multimedia API - target: Depends on failed component

17:19:18 SUMMARY: TensorRT Runtime - target: Depends on failed component

17:19:18 SUMMARY: CUDA Runtime - target: Depends on failed component

17:19:18 SUMMARY: CuDNN Runtime - target: Depends on failed component

17:19:18 SUMMARY: OpenCV Runtime - target: Depends on failed component

17:19:18 SUMMARY: CuPVA Runtime - target: Depends on failed component

17:19:18 SUMMARY: VPI Runtime - target: Depends on failed component

17:19:18 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta) - target: Depends on failed component

17:19:18 SUMMARY: Gstreamer - target: Depends on failed component

17:19:18 SUMMARY: DLA Compiler - target: Depends on failed component

17:19:18 SUMMARY: DateTime Target Setup - target: Depends on failed component

17:19:18 DEBUG: running command < true >

17:19:18 INFO: exec_command: true

17:19:18 INFO: command finished successfully

17:19:18 DEBUG: running command < sudo rm -rf ‘/home/user/nvidia/nvidia_sdk/JetPack_6.0_Linux’ >

17:19:18 INFO: exec_command: sudo rm -rf ‘/home/user/nvidia/nvidia_sdk/JetPack_6.0_Linux’

17:19:18 INFO: command finished successfully

3

Hi daniel.nvidia,

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

Are you using stand alone Ubuntu 20.04 or 22.04 as your host PC?

Please try using the following command to flash the devkit with JP6.1.

$ sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
4

For this issue, please disable the firewall configuration on your host.

5

I’m using the devkit 0005 and ubuntu 20.04 as host pc.
Regarding the firewall, it seems like it have been inactive the whole time. I tried the following:

sudo ufw status
[sudo] password for user:
Status: inactive

I’m will try your command as soon as I’m back at work. Thanks.

6

I have tried your command from “/home/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra” and are still facing problems.

This is parts of the log:
64055296 bytes (64 MB, 61 MiB) copied, 0.921698 s, 69.5 MB/s
Writing recovery partition done
writing item=9, 9:0:recovery-dtb, 420237312, 524288, tegra234-p3768-0000+p3767-0005-nv.dtb.rec, 249593, fixed--9, cb0bd420bd258e3b111cf272f313e841da8cd6bb
Writing recovery-dtb partition with tegra234-p3768-0000+p3767-0005-nv.dtb.rec
Get size of partition through connection.
249593 bytes from /mnt/external/tegra234-p3768-0000+p3767-0005-nv.dtb.rec to /dev/nvme0n1: 1KB block=243 remainder=761
dd if=/mnt/external/tegra234-p3768-0000+p3767-0005-nv.dtb.rec of=/dev/nvme0n1 bs=1K skip=0 seek=410388 count=243
243+0 records in
243+0 records out
248832 bytes (249 kB, 243 KiB) copied, 0.00708346 s, 35.1 MB/s
dd if=/mnt/external/tegra234-p3768-0000+p3767-0005-nv.dtb.rec of=/dev/nvme0n1 bs=1 skip=248832 seek=420486144 count=761
761+0 records in
761+0 records out
761 bytes copied, 0.00150157 s, 507 kB/s
Writing recovery-dtb partition done
writing item=10, 9:0:esp, 420761600, 67108864, esp.img, 67108864, fixed--10, f1a1a98db44ae1e6bae50eeb8eef4fa0b94b3343
Writing esp partition with esp.img
Get size of partition through connection.
67108864 bytes from /mnt/external/esp.img to /dev/nvme0n1: 1KB block=65536 remainder=0
dd if=/mnt/external/esp.img of=/dev/nvme0n1 bs=1K skip=0 seek=410900 count=65536
65536+0 records in
65536+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 1.00146 s, 67.0 MB/s
Writing esp partition done
writing item=11, 9:0:recovery_alt, 487870464, 83886080, , , fixed--11,
[ 8]: l4t_flash_from_kernel: Warning: skip writing recovery_alt partition as no image is specified
writing item=12, 9:0:recovery-dtb_alt, 571756544, 524288, , , fixed--12,
[ 8]: l4t_flash_from_kernel: Warning: skip writing recovery-dtb_alt partition as no image is specified
writing item=13, 9:0:esp_alt, 572280832, 67108864, , , fixed--13,
[ 8]: l4t_flash_from_kernel: Warning: skip writing esp_alt partition as no image is specified
writing item=14, 9:0:UDA, 639401984, 419430400, , , fixed--14,
[ 8]: l4t_flash_from_kernel: Skip writing UDA partition
writing item=15, 9:0:reserved, 1058832384, 502792192, , , fixed--15,
[ 8]: l4t_flash_from_kernel: Warning: skip writing reserved partition as no image is specified
writing item=16, 9:0:APP, 1561624576, 59641638912, , , expand--1,
Formatting APP partition /dev/nvme0n1p1 …
mke2fs 1.46.5 (30-Dec-2021)
Discarding device blocks: done
Creating filesystem with 243809385 4k blocks and 60956672 inodes
Filesystem UUID: d35663cc-e3c0-496e-b8bc-7b7b8f7c4992
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

Formatting APP parition done
Formatting APP partition /dev/nvme0n1p1 …
tar --checkpoint-action="ttyout=Hit %s checkpoint #%u%\r" -x -I ‘zstd -T0’ -pf /mnt/external/system.img --warning=no-timestamp --numeric-owner --xattrs --xattrs-include= -C /tmp/ci-mvsf4lUeEx
Flash failure
Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,…) to make sure the device can mount NFS server. Debug log saved to /tmp/tmp.EX938YwII0. You can access the target’s terminal through “sshpass -p root ssh root@fc00:1:1:0::2”
Cleaning up…

However:
I’m thinking about the possibility for the device to not being able to mount the NFS server.
My firewall is down and we have tried on other computers and are facing the same problems. Isn’t it the same solution as jetpack 5.1.4 where is succueeds or is this a new item in the installation steps for 6.0 and above?

It also suggest that I should ssh into the device. This is not possible, I’ve tried to just restart it using the power button and also start it in manual mode.

I’m suspecting there is a problem when writing to the device and then waiting for it to reboot where it fails. Then it’s not possible to communicate anymore. It could be either something wrong when writing to the NVME (we have tried two separate Jetsons with tro separate NVME disks) or something wrong with the boot record,.

Any other suggestions for us to try?

7

Please provide the full flash log as file here instead of pasting part of them.

You can also try to remove /etc/exports from your host and check if it could help in your case.

9

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