doc: Add guide for dev setup on Windows

[maribu]

Contribution description

This adds a detailed instruction on how to get a working development setup on Windows.

State

• Installation of WSL/Ubuntu
• Cloning RIOT + first steps
• Installation of VS Code
• Integration of VS Code to WSL + IntelliSense
• Working and compiling from VS Code
• Working on real hardware via USB IP

Testing procedure

Check here for a rendering of the added README.md

Issues/PRs references

#20388

[dylad]

@maribu Note that you can also use .exe directly from WSL so one can install JLinkExe.exe (for example) into windows, symlink the .exe binary to JLinkExe within WSL then use good old make flash from WSL console to flash a board. This could be an interesting alternative to USBIP.
Of course, it will only work if the tool has a Windows version of it.

[maribu]

With USB-IP also make term works and it is actually quite straight forward. I just need to prepare the screen shots

[dylad]

Let me know when the full tutorial is ready. I'll give it a try on my W10 laptop.

[maribu]

Should be good now :)

[Teufelchen1]

Awesome! Please be patient for a couple of days, maybe one or two weeks. I'm drowning in work rn.

[dylad]

Followed the whole tutorial. I was able to successfully flash p-nucleo-wb55 and nrf5340dk-app on W10 with WSL2.

The only issue is with DAP programmer which rely on USB HID. This is not supported by the default WSL Linux Kernel.
For now, I suggest to add a note in the tutorial to warn users.
We can add a specific workaround (using edbg windows binary) in a followup PR. Maybe this will be fix in a future WSL release.

For now, I think this PR is already in good shape !

[maribu]

Thanks. I added the info about USB HID programmers.

I do get why Microsoft disabled CONFIG_USB_HIDDEV, as users are not expected to forward their Mouse and Keyboard directly to WSL.

The thing is that HID devices are the only USB device class that works on Windows without any driver being installed. (Which also makes sense: Installing your Mouse and Keyboard driver without using a Mouse and Keyboard on Windows will be a challenge.)

Abusing HID as transport for debuggers only became popular because of the desire to have the smooth driver-less experience Linux users are familiar with also on Windows. It's quite ironic that this decision resulted in the experience now being less smooth for Windows users wanting to use RIOT.

[riot-ci]

Murdock results

✔️ PASSED

8b088c8 doc: Add guide for dev setup on Windows

Success	Failures	Total	Runtime
1	0	1	19s

Artifacts

[dylad]

Spotted a typo in the newly added text.
You can squash directly.

[dylad]

Looking good !

[maribu]

Thx :)