Hi, I am trying to flash Jetson Orin Nano Devkit using SDK Manager. This is the second time I’m doing this. I initially followed the official instructions that are now archived, and managed to successfully flash the system to a NVMe. When developing with python cv2 i faced troubles with a version of the library I was using as it was built with Gstreamer disabled. This led me to issue I’m trying to solve now.
I am trying to flash the Jetson once again, but this time I want to include the Jetson Runtime Components which, as I understand contain built OpenCV library with Gstreamer. I am not able to flash the system manually as the Jetson does not seem to enter recovery mode when shorting pin 9 and 10. The Flash button in the SDK Manager is simply grayed out and I am not able to follow. When trying to flash using automatic mode I get following error:
16:18:13 INFO: inet 192.168.55.100/24 brd 192.168.55.255 scope global dynamic noprefixroute enxc6321ab2f7d0
16:18:13 DEBUG: command finished successfully
16:18:13 INFO: Validated default IP available.
16:18:13 INFO: Start to check if IP and ssh up...
16:18:13 DEBUG: running command < nc -z -w 5 192.168.55.1 22 >
16:18:13 DEBUG: command finished successfully
16:18:13 INFO: Connection to the device via SSH is available.
16:18:13 INFO: Start to check if right credentials...
16:18:13 DEBUG: running command < ssh -F /dev/null -o PreferredAuthentications=password -o PubkeyAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=ERROR -o ConnectTimeout=5 -o NumberOfPasswordPrompts=1 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 m1@192.168.55.1 "echo hello" >
16:18:13 INFO: [target] m1@192.168.55.1's password:
16:18:13 INFO: hello
16:18:13 DEBUG: command finished successfully
16:18:13 INFO: Validated its username and password.
16:18:13 INFO: Start to check the selected storage device availability...
16:18:13 DEBUG: ssh -t m1@192.168.55.1 lsblk | grep -i nvme
16:18:14 INFO: nvme0n1 259:0 0 931,5G 0 disk
16:18:14 INFO: ├─nvme0n1p1 259:1 0 930,1G 0 part /
16:18:14 INFO: ├─nvme0n1p2 259:2 0 128M 0 part
16:18:14 INFO: ├─nvme0n1p3 259:3 0 768K 0 part
16:18:14 INFO: ├─nvme0n1p4 259:4 0 31,6M 0 part
16:18:14 INFO: ├─nvme0n1p5 259:5 0 128M 0 part
16:18:14 INFO: ├─nvme0n1p6 259:6 0 768K 0 part
16:18:14 INFO: ├─nvme0n1p7 259:7 0 31,6M 0 part
16:18:14 INFO: ├─nvme0n1p8 259:8 0 80M 0 part
16:18:14 INFO: ├─nvme0n1p9 259:9 0 512K 0 part
16:18:14 INFO: ├─nvme0n1p10 259:10 0 64M 0 part /boot/efi
16:18:14 INFO: ├─nvme0n1p11 259:11 0 80M 0 part
16:18:14 INFO: ├─nvme0n1p12 259:12 0 512K 0 part
16:18:14 INFO: ├─nvme0n1p13 259:13 0 64M 0 part
16:18:14 INFO: ├─nvme0n1p14 259:14 0 400M 0 part
16:18:14 INFO: └─nvme0n1p15 259:15 0 479,5M 0 part
16:18:14 DEBUG: command finished successfully
16:18:14 INFO: The NVMe availability check passed.
16:18:14 DEBUG: ssh -t m1@192.168.55.1 sudo reboot forced-recovery
16:18:14 INFO: [target] [sudo] password for m1:
16:18:19 INFO: Start to check if in device recovery mode...
16:18:19 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:19 DEBUG: command finished successfully
16:18:19 ERROR: Can not find matching device in recovery mode.
16:18:19 : null - null: Could not get lsusbInfos in Jetson prechecks.
16:18:24 INFO: Start to check if in device recovery mode...
16:18:24 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:24 INFO: 003/012: 0955:7523;
16:18:24 DEBUG: command finished successfully
16:18:24 ERROR: Can not find matching device in recovery mode.
16:18:24 : null - null: Could not get lsusbInfos in Jetson prechecks.
16:18:24 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:24 INFO: 003/012: 0955:7523;
16:18:24 DEBUG: command finished successfully
16:18:24 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:24 INFO: 003/012: 0955:7523;
16:18:24 DEBUG: command finished successfully
16:18:29 INFO: Start to check if in device recovery mode...
16:18:29 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:29 INFO: 003/012: 0955:7523;
16:18:29 DEBUG: command finished successfully
16:18:29 ERROR: Can not find matching device in recovery mode.
16:18:29 : null - null: Could not get lsusbInfos in Jetson prechecks.
16:18:34 INFO: Start to check if in device recovery mode...
16:18:34 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:34 INFO: 003/012: 0955:7523;
16:18:34 DEBUG: command finished successfully
16:18:34 ERROR: Can not find matching device in recovery mode.
16:18:34 : null - null: Could not get lsusbInfos in Jetson prechecks.
16:18:39 INFO: Start to check if in device recovery mode...
16:18:39 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:39 INFO: 003/012: 0955:7523;
16:18:39 DEBUG: command finished successfully
16:18:39 ERROR: Can not find matching device in recovery mode.
16:18:39 : null - null: Could not get lsusbInfos in Jetson prechecks.
16:18:44 INFO: Start to check if in device recovery mode...
16:18:44 DEBUG: running command < lsusb | grep 0955: | awk '{printf $2 "/" $4 " " $6 ";"}' >
16:18:44 INFO: 003/012: 0955:7523;
16:18:44 DEBUG: command finished successfully
16:18:44 ERROR: Can not find matching device in recovery mode.
16:18:44 : null - null: Could not get lsusbInfos in Jetson prechecks.
16:18:44 ERROR: Failed to use 'Automatic setup'. Please try again or change to 'Manual Setup' to continue.
16:18:49 INFO: All done!
I am also not able to skip flashing the new system as there is a version mismatch with the Jetson Runtime Components. My main goal is to get the correct python OpenCV version, I have tried building it from source like couple topics here suggested but I had no success in doing so.
