Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.2 Serial communication :: missing info for Linux #27

Open
steelx opened this issue Oct 29, 2020 · 1 comment
Open

4.2 Serial communication :: missing info for Linux #27

steelx opened this issue Oct 29, 2020 · 1 comment

Comments

@steelx
Copy link

steelx commented Oct 29, 2020

The tooling section has no information or help for Linux. Im using PopOs 20.04
also by running
dmesg | grep -i tty command I dont see /dev/ttyUSB0

but I get following result

❯ sudo dmesg | grep -i tty
[    0.016786] ACPI: SSDT 0x0000000062E07E78 001014 (v02 _ASUS_ TbtTypeC 00000000 INTL 20160527)
[    0.161808] printk: console [tty0] enabled
[   33.928897] Bluetooth: RFCOMM TTY layer initialized
[ 1048.976117] cdc_acm 1-13.3:1.1: ttyACM0: USB ACM device
❯ ls -l /dev/ttyUSB0
ls: cannot access '/dev/ttyUSB0': No such file or directory
@Eragonfr
Copy link

Your Micro:Bit is on /dev/ttyACM0 not on /dev/ttyUSB0
It's a common result on linux, in fact evry Linux I have is doing that, a connected board with serial over usb ends on /dev/ttyACM0If I have second board I get a /dev/ttyACM1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants