I am manually flashing Jetpack 35.6 and followed process on NVIDIA flash instruction, but I have still stuck in error.
the device is Jetson Orin Nano Developer Kits 8GB and the process I followed with command is below:
$ tar xf Jetson_Linux_R35.6.0_aarch64.tbz2
$ sudo tar xpf Tegra_Linux_Sample-Root-Filesystem_R35.6.0_aarch64.tbz2 -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./apply_binaries.sh
$ sudo ./tools/l4t_flash_prerequisites.sh
Then, force recovery mode with jumper and connect to the host computer to device, then put the power on.
The device is perfectly connected to the host PC on recovery mode.
Then, I enter the command (flash with SD card):
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk1p1
-c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml”
–showlogs --network usb0 jetson-orin-nano-devkit internal
[ 0.2330 ] Sending bct_br
[ 0.2802 ] ERROR: might be timeout in USB write.
Error: Return value 3
The “APX” in the lsusb usually means it is a virtualization. Virtual environments are out of the control of the NVIDIA software, so you would be on your own to make sure that USB not only connects at the start, but that as the Jetson disconnects and reconnects, that the VM reacquires the USB. Is this a VM?
In that case I would not expect an error. The older systems which used a micro-B USB cable (a “charger” or “OTG” port) would fail like this due to cable (this is a “charger” cable, and if you use one which was not intended for data, then the data quality was so poor about 2 out of 3 would fail and you’d need a new brand).
Not sure what to say in this case (incidentally, I normally expect APX on a VM).