Page 1 of 1

Sparkfun ESP32 Thing ttyusb0 device 'frame counter not updating; disabled'

Posted: Mon Nov 21, 2016 4:19 pm
by beefok
Hello all,

I am trying to get the Sparkfun ESP32 Thing to connect in this setup:

Windows 10 Professional hosting a Virtual Box with a freshly installed Ubuntu 16.10.
I have USB 2.0 set up with the FTDI device being routed through to Ubuntu in Virtual Box.

dmesg reports:

[ 10.638958] usbcore: registered new interface driver usbserial
[ 10.638971] usbcore: registered new interface driver usbserial_generic
[ 10.638978] usbserial: USB Serial support registered for generic
[ 10.663720] usbcore: registered new interface driver ftdi_sio
[ 10.663730] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 10.663759] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
[ 10.663789] usb 2-2: Detected FT-X
[ 10.682297] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0

...

[ 21.176859] ohci-pci 0000:00:06.0: frame counter not updating; disabled
[ 21.176867] ohci-pci 0000:00:06.0: HC died; cleaning up
[ 21.177456] usb 2-1: USB disconnect, device number 2
[ 21.253821] usb 2-2: USB disconnect, device number 3
[ 21.254071] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0

This shows that the device is being detected and being attached to ttyUSB0. This actually appears to be related to this bug: https://www.mail-archive.com/ubuntu-bug ... 63723.html

Anyone else having this issue?

Thanks for your time!

Re: Sparkfun ESP32 Thing ttyusb0 device 'frame counter not updating; disabled'

Posted: Tue Nov 22, 2016 7:06 am
by uhrheber
No, but then I don't use Ubuntu but Mint, both native and in a Virtualbox running on Windows 7, and all of them have a kernel < 4.8.10.
I'd try to downgrade to an older kernel.

Re: Sparkfun ESP32 Thing ttyusb0 device 'frame counter not updating; disabled'

Posted: Tue Nov 22, 2016 4:01 pm
by beefok
Yes I was actually able to fix this issue yesterday later in the day, my post just didn't arrive to the forum quick enough. :)
The issue goes away in 16.04!