No tty device on Ubuntu 16.04



  • I am trying to get my serial connection to the Expansion Dock with Omega2+ to show up on Ubuntu 16.04. I am successfully able to connect to other vendor dev boards and a /dev/tty/USBn shows up. However, I do not get one for the Expansion Dock.

    I have tried different cables all with the same result.

    I have cp210x installed:
    ~$ modinfo cp210x
    filename: /lib/modules/4.4.0-45-generic/kernel/drivers/usb/serial/cp210x.ko
    license: GPL
    description: Silicon Labs CP210x RS232 serial adaptor driver
    srcversion: B8FE0D3E76AFDE9370644DC
    alias: usb:v413Cp9500ddcdscdpiciscipin
    alias: usb:v3195pF281ddcdscdpiciscipin
    alias: usb:v3195pF280ddcdscdpiciscipin
    alias: usb:v3195pF190ddcdscdpiciscipin
    alias: usb:v2626pEA60ddcdscdpiciscipin
    alias: usb:v1FB9p0701ddcdscdpiciscipin
    ...
    alias: usb:v0846p1100ddcdscdpiciscipin
    alias: usb:v0745p1000ddcdscdpiciscipin
    alias: usb:v0489pE003ddcdscdpiciscipin
    alias: usb:v0489pE000ddcdscdpiciscipin
    alias: usb:v0471p066Addcdscdpiciscipin
    alias: usb:v045Bp0053ddcdscdpiciscipin
    depends: usbserial
    intree: Y
    vermagic: 4.4.0-45-generic SMP mod_unload modversions

    dmesg shows a bunch of errors when I plug in the cable to the Expansion Dock micro USB connection:
    usb 3-2: new full-speed USB device number 124 using xhci_hcd
    [9170098.059566] usb 3-2: device descriptor read/64, error -71
    [9170098.275577] usb 3-2: device descriptor read/64, error -71
    [9170098.491520] usb 3-2: new full-speed USB device number 125 using xhci_hcd
    [9170098.603520] usb 3-2: device descriptor read/64, error -71
    [9170098.819545] usb 3-2: device descriptor read/64, error -71
    [9170099.035485] usb 3-2: new full-speed USB device number 126 using xhci_hcd
    [9170099.035596] usb 3-2: Device not responding to setup address.
    [9170099.239643] usb 3-2: Device not responding to setup address.
    [9170099.443521] usb 3-2: device not accepting address 126, error -71
    [9170099.555474] usb 3-2: new full-speed USB device number 127 using xhci_hcd
    [9170099.555611] usb 3-2: Device not responding to setup address.
    [9170099.759628] usb 3-2: Device not responding to setup address.
    [9170099.963417] usb 3-2: device not accepting address 127, error -71
    [9170099.963477] usb usb3-port2: unable to enumerate USB device

    Do I need to add a rule to /etc/udev/rules.d to get it to map to the cp210x driver?

    Cheers,
    Dan



  • @Daniel-Petrie said in No tty device on Ubuntu 16.04:

    I am trying to get my serial connection to the Expansion Dock with Omega2+ to show up on Ubuntu 16.04. I am successfully able to connect to other vendor dev boards and a /dev/tty/USBn shows up. However, I do not get one for the Expansion Dock.

    I have tried different cables all with the same result.

    I have cp210x installed:
    ...
    dmesg shows a bunch of errors when I plug in the cable to the Expansion Dock micro USB connection:

    You should connect a simple Micro-USB to USB cable from the Omega's Expansion Dock to your PC.

    See also: official Onion Omega2 Documentation Connecting to the Omega’s Command Line Connecting via Serial

    # Ubuntu 17.04
    # connect Omega's Expansion Dock to your PC with a micro-USB to USB cable
    
    dmesg | tail -n 20
    ...
    [14478.516041] usb 2-2: new full-speed USB device number 2 using uhci_hcd
    [14478.725054] usb 2-2: New USB device found, idVendor=10c4, idProduct=ea60
    [14478.725059] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [14478.725062] usb 2-2: Product: CP2102 USB to UART Bridge Controller
    [14478.725065] usb 2-2: Manufacturer: Silicon Labs
    [14478.725068] usb 2-2: SerialNumber: 0001
    [14479.871309] usbcore: registered new interface driver usbserial
    [14479.871324] usbcore: registered new interface driver usbserial_generic
    [14479.871342] usbserial: USB Serial support registered for generic
    [14479.994681] usbcore: registered new interface driver cp210x
    [14479.994698] usbserial: USB Serial support registered for cp210x
    [14479.994724] cp210x 2-2:1.0: cp210x converter detected
    [14480.000140] usb 2-2: cp210x converter now attached to ttyUSB0
    
    
    ls -l /dev/ttyUSB*
    crw-rw---- 1 root dialout 188, 0 jan    9 06:59 /dev/ttyUSB0
    

    Good luck!



  • I would try in ubuntu 'lsusb' to see if it's connected and recognized.



  • @György-Farkas said in No tty device on Ubuntu 16.04:

    You should connect a simple Micro-USB to USB cable from the Omega's Expansion Dock to your PC.

    Yes, I am using a simple micro-usb to usb-A cable. As I said, I have tried several. I did this to be sure it was not a cable problem.

    See also: official Onion Omega2 Documentation Connecting to the Omega’s Command Line Connecting via Serial

    Yes, I followed those instructions before posting here.

    The cp210x module is loaded:
    $ lsmod | grep cp210
    cp210x 24576 1
    usbserial 53248 4 cp210x,pl2303

    However, no new /dev/ttyUSB* devices are present and as included in my original post there are errors shown by dmesg. It seems to be indicating that it cannot get device info from the Expansion Dock.



  • @Carlos-Sancho said in No tty device on Ubuntu 16.04:

    I would try in ubuntu 'lsusb' to see if it's connected and recognized.

    from dmesg:
    [9221247.924088] usb 3-2: new full-speed USB device number 2 using xhci_hcd
    [9221248.036092] usb 3-2: device descriptor read/64, error -71
    [9221248.252078] usb 3-2: device descriptor read/64, error -71
    [9221248.468043] usb 3-2: new full-speed USB device number 3 using xhci_hcd
    [9221248.580110] usb 3-2: device descriptor read/64, error -71
    [9221248.796028] usb 3-2: device descriptor read/64, error -71
    [9221249.012023] usb 3-2: new full-speed USB device number 4 using xhci_hcd
    [9221249.012149] usb 3-2: Device not responding to setup address.
    [9221249.216111] usb 3-2: Device not responding to setup address.
    [9221249.419984] usb 3-2: device not accepting address 4, error -71
    [9221249.532021] usb 3-2: new full-speed USB device number 5 using xhci_hcd
    [9221249.532158] usb 3-2: Device not responding to setup address.
    [9221249.736654] usb 3-2: Device not responding to setup address.
    [9221249.939958] usb 3-2: device not accepting address 5, error -71

    My read on this is that the Expansion Dock should show up on USB bus 003 device 002, 003, 004 or 005.

    $ lsusb
    Bus 002 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 005: ID 5986:02d2 Acer, Inc
    Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode)
    Bus 001 Device 013: ID 0b0e:0345 GN Netcom
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 087: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
    Bus 003 Device 086: ID 04d9:a070 Holtek Semiconductor, Inc.
    Bus 003 Device 091: ID 067b:2773 Prolific Technology, Inc. PL2773 SATAII bridge controller
    Bus 003 Device 083: ID 05e3:0608 Genesys Logic, Inc. Hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    From my interpretation, of the above it did not get connected or recognized and does not show up in lsusb.



  • @Daniel-Petrie Bad news.
    You should check

    • that Ubuntu host PC - try another PC - or try that PC with another CP210x module / cable
    • the USB cable
    • at least visually check the PCB and some parts of the Expansion Dock:
      micro USB connector; SILABS CP2102 IC; C115, C116 capacitors

    [Tip] Switch the Omega to VERBOSE by @fossette

    But first, something not (yet) mentioned in the docs, ground yourself and perform a thorough visual inspection of all hardware pieces that you receive. Look for non-aesthetic solder blob on the board. I personally found some. Pin solder weren't touching but they were too close for comfort, IMO. To fix that, I used a soldering iron with the pin over the heated tip of the iron to let gravity fix the solder blob. Also, perform this basic test to see if you have any short circuit between ground pins, power pins and the other pins. Statistics from my purchase, 33% of the Omega2+ were affected by solder blobs. I wouldn't say 'sloppy', but it's definitely disappointing. As, is there anything else wrong with those Omega2+?

    You should see those dmesg CP2102 related messages if there isn't Omega2(+) on the Dock and the POWER SWITCH ON or OFF.



  • @Daniel-Petrie "- try another PC -"
    If your Omega2+ and the Expansion Dock - apart from this issue - working well and you have an "Y" USB cable (micro USB --- two USB A)
    then connect to Omega via ssh and plug / unplug the second USB A into the Host port of the Expansion Dock.

    If the CP2102 is OK then you should see something similar messages:

    root@Omega-5BE1:~# dmesg | tail
    ...  
    [  638.799708] usb 2-1: new full-speed USB device number 2 using ohci-platform
    [  639.062198] cp210x 2-1:1.0: cp210x converter detected
    [  639.067696] usb 2-1: cp210x converter now attached to ttyUSB0
    [  677.002495] usb 2-1: USB disconnect, device number 2
    [  677.007927] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
    [  677.015048] cp210x 2-1:1.0: device disconnected
    


  • @Daniel-Petrie said in No tty device on Ubuntu 16.04:

    [9221247.924088] usb 3-2: new full-speed USB device number 2 using xhci_hcd
    [9221248.036092] usb 3-2: device descriptor read/64, error -71
    [9221248.252078] usb 3-2: device descriptor read/64, error -71
    [9221248.468043] usb 3-2: new full-speed USB device number 3 using xhci_hcd
    [9221248.580110] usb 3-2: device descriptor read/64, error -71
    [9221248.796028] usb 3-2: device descriptor read/64, error -71
    [9221249.012023] usb 3-2: new full-speed USB device number 4 using xhci_hcd
    [9221249.012149] usb 3-2: Device not responding to setup address.
    [9221249.216111] usb 3-2: Device not responding to setup address.
    [9221249.419984] usb 3-2: device not accepting address 4, error -71
    [9221249.532021] usb 3-2: new full-speed USB device number 5 using xhci_hcd
    [9221249.532158] usb 3-2: Device not responding to setup address.
    [9221249.736654] usb 3-2: Device not responding to setup address.
    [9221249.939958] usb 3-2: device not accepting address 5, error -71

    This sound bad. Seems is there, but is restarting continously. Maybe try another cable... and also another computer. Another try is to connect just the dock without the omega2 to see if works fine (usb power related problems).



  • @Carlos-Sancho said in No tty device on Ubuntu 16.04:

    This sound bad. Seems is there, but is restarting continously. Maybe try another cable... and also another computer. Another try is to connect just the dock without the omega2 to see if works fine (usb power related problems).

    It did indeed work fine on a Window 10 Lenovo laptop. Your statement got me thinking about power. So I plugged it in via a Charger Doctor (USB power meter) and it is drawing atleast 0.09 amp at 4.9 volts, but peaking at times around 0.14 amps, 0.69 watts (usb 2 limit is 0.5 watts). My Ubuntu laptop has a bunch of USB devices plugged in and drawing power. So I plugged a powered USB hub into my Ubuntu/Lenovo laptop and the Expansion Dock into the powered USB hub and it worked.

    Thanks for the ideas!

    It seems the Expansion Dock and Omega2+ are drawing more power than they should for usb 2.0



  • Just for the record, I tested mine and usually draws about 250mA, omega2p with WiFi AP, Mini Dock and OLED Display. Also, USB 2.0 has a standard defined power of 5V and 500mA (2.5W) so is fine for a Omega2 to power up from USB.



  • I have exactly this problem. I moved the omega2+ to a similar computer. Both have ubuntu 14.04 LTS. It works OK on one but not on the other.



Looks like your connection to Community was lost, please wait while we try to reconnect.