Hi,
I’m trying to flash a Jetson Orin Nano with a new version, specific 5.1.2.
Currently I’m getting the following error message in step 3 Step 3: Start the flashing process:
Waiting for target to boot-up...
Unknown device "/sys/class/net/bonding_masters": No such device
Unknown device "/sys/class/net/bonding_masters": No such device
Waiting for target to boot-up...
Timeout
Cleaning up...
Technically, no VM is supported. Each has its own setup, and the flash software cannot assist in any way (that is in fact one of the purposes of a VM: Security that cannot be modified by the software running in it).
Some people do get VMs to work. One problem is usually that USB disconnects and reconnects during a flash, but reconnect fails if the VM is not set up correctly. This does not appear to be the issue in this case.
Unless it has been set up properly (and how to set it up is beyond my ability), it is quite probably that the WSL2 kernel is missing a feature, e.g., loopback. Loopback mode is used when creating a rootfs image.
One other problem is that if you use this with a Windows filesystem type, e.g., NTFS or VFAT, that the flash will “appear” to succeed, but in reality the Jetson boot will be highly crippled.
Mostly you are advised to use an actual Ubuntu 20 install. Dual boot is reasonably easy to add if you already have the disk space. You could divide existing space, but adding a second drive makes installing Linux fairly easy.
It might also be possible to use a “live” distribution whereby you are trying out Ubuntu 20, and it runs in RAM, but doesn’t actually install it until you tell it to. You’d still need sufficient ext4 filesystem, and it does take a lot. After the operating system install you’d probably want at least another 100 GB of space before any kind of use in flashing (I’d personally suggest another 50 GB on top of that).
Someone else would have to answer the WSL2 conditions, it is something I don’t use. 100% of the older WSL2 installations required loopback customization of the kernel. I don’t know about the most recent versions.
I’m sorry but our documents only verifies cases with AGX Orin, which is to be flashed internally with flash.sh. For Orin NX/Nano that requires initrd flash, we don’t validate such use cases.
Anyway, seems like WSL kernel you use does not enable the bonding driver, which is required in the case of initrd flash.
For example, this is enabled on my Ubuntu 18.04 PC
The APX says it is likely a VM. The same answer as originally posted is that the VM probably lacks some feature, e.g., maybe it is not holding the USB for a disconnect/reconnect, or (in the original case) the VM kernel lacks a driver (that example is bonding). There is no way for the flash software to know about, nor to configure, a VM host. You’d have to figure out the VM configuration and kernel update yourself.
