You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you're doing and what's happening:
I have two machines with WSL, a professional laptop with WSL and an old Windows 10 build which saw my FTDI cable. I have my personal computer with WSL2 which stops ttyS node at 3 while my FTDI is COM5.
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.
Your Windows build number: version 10.0.19041.207
What you're doing and what's happening:
I have two machines with WSL, a professional laptop with WSL and an old Windows 10 build which saw my FTDI cable. I have my personal computer with WSL2 which stops ttyS node at 3 while my FTDI is COM5.
ls /dev -l | grep ttyS
crw------- 1 root root 4, 64 Apr 15 19:20 ttyS0 crw------- 1 root root 4, 65 Apr 15 19:20 ttyS1 crw------- 1 root root 4, 66 Apr 15 19:20 ttyS2 crw------- 1 root root 4, 67 Apr 15 19:20 ttyS3
I tried to manually create the node for ttyS5 but I am still not able to get logs from my board through the FTDI cable.
On my other machine, I have up to 106 ttyS nodes and I also noticed they belong to the dialout group and not the root one.
Unfortunately, I didn't find a similar case... Any hint?
Thanks
The text was updated successfully, but these errors were encountered: