I can only add to this discussion that we are facing a similar issue using both a command line tool and the sdk manager that fail.
While for JetPack 5.1.5, after running:
sudo ./nvautoflash.sh
It gets stuck on (see attached full dump):
jet_pack_5.1.5_cli_flash_output.txt (79.3 KB)
[ 9.7018 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin
For JetPack 6.2.1, the command:
sudo ./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-super internal
Runs until reaching:
***************************************
* *
* Step 3: Start the flashing process *
* *
***************************************
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ...sysctl -n net.ipv6.conf.enx2201d6ea5db9.disable_ipv6
net.ipv6.conf.enx2201d6ea5db9.disable_ipv6 = 1
IPv6 is disabled. Please enable ipv6 to use this tool
Error: ipv6: IPv6 is disabled on this device.
Error: ipv6: IPv6 is disabled on this device.
........................................................................................................................................................................................................................................................................................................................................................................Timeout
Device should have booted into initrd kernel now. However, the host cannot connect to its ssh server
Command failed: ping6 -c 1 fe80::1%enx2201d6ea5db9. Check your network settings (firewall, VPN,...) so that it can ping fe80::1%enx2201d6ea5db9
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 10:98:19:12:81:19 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether a0:d3:65:5f:07:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.XXX.XXX/24 brd 192.168.XXX.255 scope global dynamic noprefixroute wlp0s20f3
valid_lft 597938sec preferred_lft 597938sec
inet6 fe80::e239:ae34:d75c:67/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 46:57:b2:11:dc:25 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
8: enx2201d6ea5db9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 22:01:d6:ea:5d:b9 brd ff:ff:ff:ff:ff:ff
inet 192.168.123.120/24 brd 192.168.123.255 scope global noprefixroute enx2201d6ea5db9
valid_lft forever preferred_lft forever
And the query continues for many minutes until a timeout occurs.
jet_pack_6.2.1_cli_flash_output.txt (289.0 KB)
I’ve even installed a real NVMe storage card thinking what could get wrong in the process.
It is becoming a critical issue for us after spending many days on flashing trials.
Hope this can help a little.
Moti.