Linux - cannot connect to WarpX through the interposer's ttyUSB1

23 views
Skip to first unread message

Csaba Toth

unread,
Sep 3, 2017, 7:48:05 PM9/3/17
to >warpx.io
I'm using 17.04 Ubuntu now.

dmesg when I connect the interposer:

[13475.113106] usb 1-14: new full-speed USB device number 42 using xhci_hcd
[13475.282780] usb 1-14: New USB device found, idVendor=10c4, idProduct=ea70
[13475.282784] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[13475.282786] usb 1-14: Product: REVO Interposer
[13475.282788] usb 1-14: Manufacturer: Silicon Labs
[13475.282789] usb 1-14: SerialNumber: 005D7D02
[13475.312167] usbcore: registered new interface driver usbserial
[13475.312198] usbcore: registered new interface driver usbserial_generic
[13475.312215] usbserial: USB Serial support registered for generic
[13475.318496] usbcore: registered new interface driver cp210x
[13475.318538] usbserial: USB Serial support registered for cp210x
[13475.318556] cp210x 1-14:1.0: cp210x converter detected
[13475.320820] usb 1-14: cp210x converter now attached to ttyUSB0
[13475.320835] cp210x 1-14:1.1: cp210x converter detected
[13475.322697] usb 1-14: cp210x converter now attached to ttyUSB1
[13476.835088] cp210x ttyUSB1: failed set req 0x1e size 4 status: -32
[13476.835114] cp210x ttyUSB1: failed to set baud rate to 300
[13490.245414] cp210x ttyUSB1: failed set req 0x1e size 4 status: -32
[13490.245422] cp210x ttyUSB1: failed to set baud rate to 300

I don't know why it'd set the baud rate to 300, that sounds too low. But when I `minicom -D /dev/ttyUSB1`, nothing comes through.
So far I used /dev/ttyACM0, connected directly to the WARP board, but now I'd like to update the Yocto on it.
How could I debug this further and solve it?

Thanks,
Csaba

Csaba Toth

unread,
Sep 3, 2017, 8:03:14 PM9/3/17
to >warpx.io
Sorry, /dev/ttyUSB1 might be the WarpX board and /dev/ttyUSB0 is the interposer. Nevertheless, when I connect to either of them through minicom, nothing happens. I press enter but no response.
In the YT video https://www.youtube.com/watch?v=_3R1UZwNe8Y I see the error message about the baud rate, but not the `failed set req 0x1e size 4 status: -32`

Csaba Toth

unread,
Sep 3, 2017, 8:33:30 PM9/3/17
to >warpx.io
Weird, I was able to connect to the console with picocom. I saw they used that in a Warp7 board's tutorial I got to while Googling.
Reply all
Reply to author
Forward
0 new messages