Clarify serial REPL access from WSL2 when the CIRCUITPY drive is visible #46529

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.circuitpython.org/en/latest/docs/workflows.html

What part(s) of the article would you like to see updated?

I suggest adding a troubleshooting section for users accessing the CircuitPython serial REPL from Windows Subsystem for Linux 2 (WSL2).

During my setup, I used an Adafruit Feather Bluefruit Sense running CircuitPython 10.0.3 on Windows with WSL2 Ubuntu. Although the CIRCUITPY drive was visible, my development environment's serial monitor only listed /dev/ttyS0 to /dev/ttyS7, and I could not identify the board's serial connection.

A troubleshooting section could explain how to:

• Distinguish between access to the CIRCUITPY filesystem and access to the serial REPL.
• Check whether the board's USB serial device is accessible from WSL2.
• Identify the correct serial port and configure the development environment.
• Determine whether the problem comes from USB device access, the host environment, or the serial monitor.

These additions would help beginners troubleshoot serial connection issues when using CircuitPython tools in a Windows and WSL2 environment.

Additional information

I encountered this issue while setting up my development environment for a CircuitPython lab. The CIRCUITPY drive was accessible, but I could not identify the board's serial port in the available serial monitor devices.

I have not confirmed whether this issue affects other WSL2 users, but a troubleshooting note could help users facing similar problems.