Arch Linux

Davini

Member

Registered: 2010-04-29

Posts: 43

USB to Serial issue

Hey,

I'm having some trouble setting up a USB to Serial Adapter. When I get it all set up, my terminal is getting spammed with 0x0162.  Here's what I'm doing.

First plug in USB.

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0644:0200 TEAC Corp. All-In-One Multi-Card Reader CA200/B/S
Bus 002 Device 003: ID 04d8:9009 Microchip Technology, Inc. 
Bus 003 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 003 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 007 Device 014: ID 0403:f020 Future Technology Devices International, Ltd 

Modprobe it

#modprobe usbserial vendor=0x0403 product=0xf020

Look at dmesg to make sure the device was actually set.

#dmesg
...
[ 6265.986107] usb 7-1: new full speed USB device number 14 using uhci_hcd
[ 6266.188790] usbserial_generic 7-1:1.0: generic converter detected
[ 6266.188900] usb 7-1: generic converter now attached to ttyUSB0

Create  Symlink to use a serial port

ln -s /dev/ttyUSB0 /dev/ttyS4

When I connect to /dev/ttyS4 in minicom, the port is getting spammed. The same behavior occurs when I use /dev/ttyUSB0. My device does not require handshaking or any parity bits.

I'm not sure what's the problem.  I was hoping someone on these forums would be familiar enough with serial devices to help me understand and possibly diagnose the problem. Any help would be much appreciated.

Thanks.

Davini

Member

Registered: 2010-04-29

Posts: 43

Re: USB to Serial issue

Nevermind, I was wrong. This is a hardware issue.