I’ve been very successful in getting Kepler development going on Windows with WSL, except one small part of the development process, which is enabling tcpip mode on a new device. The problem seems to be that Windows only recognizes the connected device as a valid USB device for a few seconds during device boot, after which it disappears. Even if I very quickly bind and attach the device to WSL during these few seconds, vda on WSL doesn’t find it.
Even in non-WSL situations, attaching a device to a workstation via can be inconvenient just to do this one step.
Describe the solution you’d like
Add an option to the device’s developer menu to enable tcpip mode, similar to running ‘vda tcpip 5555’.
Is this a blocker? Describe alternatives you’ve considered
Thanks for the feature request! I understand the USB connection challenge with Windows/WSL during device boot.
Your suggestion to add a tcpip mode toggle in the Developer menu (similar to vda tcpip 5555) would definitely streamline the development workflow and eliminate the need for USB attachment just for this configuration step.
I’ve passed this along to our engineering team for evaluation. Appreciate your contribution to improving the Vega development experience!
This Feature Request has been recorded and we are working on this at the moment.
We’ll let you know via an announcement once we are ready with it.
Thanks for sharing this awesome feature request!