I am trying to flash the JetPack 4.6.3 to Jetson Xavier NX developer kit using SDKManager using WSL2. I am running an Ubuntu 18.04 in WSL2. Here is the error log for the same.
This is the error I get in the powershell terminal :-
cd Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Gtk-Message: 21:17:19.131: GtkDialog mapped without a transient parent. This is discouraged.
(sdkmanager-gui:9949): dconf-WARNING **: 21:17:19.176: failed to commit changes to dconf: The connection is closed
(sdkmanager-gui:9949): dconf-WARNING **: 21:17:19.247: failed to commit changes to dconf: The connection is closed
(sdkmanager-gui:9949): dconf-WARNING **: 21:17:19.324: failed to commit changes to dconf: The connection is closed
VMs in general can work, but are not supported. The first thing you have to get past is that USB will disconnect and reconnect during flash, and VMs will lose USB if not set up correctly. Every VM has different instructions.
For WSL2, if an image is being created, then you need loopback, and I don’t think WSL2 has loopback by default. Someone else might be able to tell you how to add that, but it is a bit more advanced topic. You’re going to have less frustration if you dual boot with a native Ubuntu.
I have flashed JetPack 5.1 version with the same WSL2 running Ubuntu 20.04, I did not encounter any such problems with that. I tried two or three times and then it flashed previously, but not now. So am I doing something wrong or is it anything that I am missing which stops it from flashing it? I do not have a standalone Ubuntu 18.04 machine so hence, the WSL route.
I have no way to suggest what configuration to check on WSL2. Basically, that’s the realm of Microsoft support, although I suppose it could be something related to Ubuntu 20.04 as well. However, if it is the same Ubuntu 20.04 installation, then I’d suspect it is a WSL2 issue. I don’t know how I could help, maybe someone who has worked on WSL2 could answer.