[RESOLVED] Unable to Connect to ESP32

Framework Laptop 13 Linux
#1

I can connect to it with Thonny on my old laptop running Ubuntu but not on my Framework (also running Ubuntu)… Anyone have any ideas?

Syslog:
Jul 11 17:11:33 framework kernel: [ 1902.876026] usb 3-3: new full-speed USB device number 15 using xhci_hcd
Jul 11 17:11:34 framework kernel: [ 1903.125115] usb 3-3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Jul 11 17:11:34 framework kernel: [ 1903.125124] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 11 17:11:34 framework kernel: [ 1903.125127] usb 3-3: Product: CP2102 USB to UART Bridge Controller
Jul 11 17:11:34 framework kernel: [ 1903.125129] usb 3-3: Manufacturer: Silicon Labs
Jul 11 17:11:34 framework kernel: [ 1903.125132] usb 3-3: SerialNumber: 0001
Jul 11 17:11:34 framework kernel: [ 1903.134504] cp210x 3-3:1.0: cp210x converter detected
Jul 11 17:11:34 framework kernel: [ 1903.135460] usb 3-3: cp210x converter now attached to ttyUSB0
Jul 11 17:11:34 framework mtp-probe: checking bus 3, device 15: “/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3”
Jul 11 17:11:34 framework mtp-probe: bus: 3, device: 15 was not an MTP device
Jul 11 17:11:34 framework snapd[862]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Jul 11 17:11:34 framework snapd[862]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Jul 11 17:11:34 framework mtp-probe: checking bus 3, device 15: “/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3”
Jul 11 17:11:34 framework mtp-probe: bus: 3, device: 15 was not an MTP device
Jul 11 17:11:34 framework snapd[862]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Jul 11 17:11:35 framework brltty[524]: USB configuration set error 16: Device or resource busy
Jul 11 17:11:35 framework brltty[524]: brltty: USB configuration set error 16: Device or resource busy
Jul 11 17:11:35 framework brltty[524]: brltty: USB interface in use: 0 (cp210x)
Jul 11 17:11:35 framework brltty[524]: USB interface in use: 0 (cp210x)
Jul 11 17:11:35 framework kernel: [ 1904.762120] usb 3-3: usbfs: interface 0 claimed by cp210x while ‘brltty’ sets config #1
Jul 11 17:11:35 framework kernel: [ 1904.762845] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Jul 11 17:11:35 framework kernel: [ 1904.762878] cp210x 3-3:1.0: device disconnected
Jul 11 17:11:35 framework ModemManager[1015]: [base-manager] port ttyUSB0 released by device ‘/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3’
Jul 11 17:11:35 framework ModemManager[1015]: [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3’: Operation was cancelled

1 Like
#2

Seems like it may just be a difference of Ubuntu versions rather than the laptop doing anything.

Here’s a thread from the Arduino forums with a quite similar-looking report where the “brltty” package is interfering with the serial connection. Note that your logs also mention “brltty,” which seems to be installed by default on current Ubuntu versions.

3 Likes
#3

Removing brltty worked. Thanks!

1 Like
#4

just to summarize, that’s what I did to disable the brltty service:

systemctl stop brltty-udev.service
sudo systemctl mask brltty-udev.service
systemctl stop brltty.service
systemctl disable brltty.service

I’m not sure if this could have any side effect on oany other system context but after this and restarting the arduino ide I got a new port entry which is ttyUSB0, and the non working old one ttyS4 is still listed.

1 Like
#5

Delighted this has been resolved. I assume this was for BRLTTY, correct?

#6

In my case I’m still investigating some issues, slowly due to lack of time at the moment.

After stopping the brltty service I saw the usb connected to my esp-32 and the arduino ide saw it too, but after a while it disappeared.

Probably this has to do in my case because of the battery extension guide->usb-autosuspend. So probably I need to whitelist my esp-32 (and each one of them I work with) or I need to disable that part of the saving-battery policy.

Once I try this out I will come back and confirm!

#7

Yep, this would be the next step. :slight_smile: