However, once I reach the step to flash the device, I choose option 5 - Manual setup of Jetson TX2, choose preconfig, and the SDK installer does not find the device, saying:
error: Could not detect correct NVIDIA Jetson device connected to USB. Verify that:
1. The device is connected to this host machine with a USB cable.
2. Correct target is selected in STEP 1. This can be validated by running the lsusb command on your host, and look for (NVIDIA Corp).
What could be the problem here? Any advice would be appreciated.
When your Jetson TX2 is connected and is in recovery mode, what is the exact output of the lsusb command? We need to know the recovery mode id for more investigation.
I fixed my issue by using Ubuntu 18.04 instead of Debian - this notably changed the name of the Jetson in lsusb from the above to just NVidia Corp. From here, I used the debian package for the SDK and completed flashing the OS image through the GUI (on Debian I used the docker installation). I’m now facing an issue with installing the Jetpack SDK which I’ll explain in a separate thread.
Well, that wasn’t my experience - flashing was pretty straightforward after using the Ubuntu 18.04 distro instead of Debian. And installing the SDK was also simple, since I just plugged it into an ethernet port, got its IP address, and didn’t have any issues after that.
I’ll also add that the GUI sdk manager was also more convenient to use, since the CLI would “forget” it had installed the host/target components if I reran the sdk manager.
WSL2 lacks loopback. If you already had an image, then you won’t notice this. However, loopback is used to generate an image. My understanding is that there is some required step to add loopback to WSL2, and it isn’t necessarily simple. What did you do to add loopback? Or did you already have a rootfs image?