I am trying to connect minicom to a serial device that is connected via a USB-to-serial adapter. This is a PL2303 and from everything I've read no additional drivers are required. The device is recognised as a PL2303.
I'm a beginner at minicom. Is this the correct command to execute? Or do I need to configure something?
$ sudo minicom --device /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: No such file or directory
$ sudo lsusb -v
Bus 002 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
$ tail /var/log/syslog #then removed and attached the device.
Mar 13 23:31:49 ubuntu kernel: [807996.786805] usb 2-1: pl2303 converter now attached to ttyUSB0
Mar 13 23:34:44 ubuntu kernel: [808172.155129] usb 2-1: USB disconnect, address 7
Mar 13 23:34:44 ubuntu kernel: [808172.156321] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
Mar 13 23:34:44 ubuntu kernel: [808172.156374] pl2303 2-1:1.0: device disconnected
Mar 13 23:34:52 ubuntu kernel: [808179.497856] usb 2-1: new full speed USB device using uhci_hcd and address 8
Mar 13 23:34:52 ubuntu kernel: [808179.785845] pl2303 2-1:1.0: pl2303 converter detected
Mar 13 23:34:52 ubuntu kernel: [808179.872309] usb 2-1: pl2303 converter now attached to ttyUSB0
First check with
dmesg | grep tty
if system recognize your adapter. Then try to run minicom withsudo minicom -s
, go to "Serial port setup" and change the first line to/dev/ttyUSB0
.Don't forget to save config as default with "Save setup as dfl". It works for me on Ubuntu 11.04 on VirtualBox.
I had fix this with
adduser *username* dialout
. I never had this error again, even though previously the only way to get it to work was to reboot the PC or unplug and replug the usb to serial adapter.Long time reader, first time helper ;)
I'm going through the same
hellish
experience here with a Prolific USB <> Serial adapter and so far Linux is the easiest to get it to work.On CentOS, I didn't need to install any drivers etc.. That said,
dmesg | grep -i tty
ordmesg | grep -i usb
showed me /dev/ttyUSB0.screen ttyUSB0 9600
didn't do the trick for me like it did in OSXHowever, this helped: https://www.centos.org/forums/viewtopic.php?t=21271
So install minicom (
yum install minicom
) then enter its settings (minicom -s
).Then select
Serial Port Setup
and change the Serial Device (Option A) to /dev/ttyUSB0, or whatever your device file is as it slightly differs per distro.Then change the Bps (Option E) to 9600 and the rest should be default (8N1 Y N)
Save as default, then simply
minicom
and Bob's your uncle.HTH.
I had the exact same problem, and it was fixed by doing a
chmod 777 /dev/ttyUSB0
. I never had this error again, even though previously the only way to get it to work was to reboot the VM or unplug and replug the USB-to-serial adapter. I am running Ubuntu 10.04 (Lucid Lynx) VM on OS X.Putty on ubuntu There is no need to install the driver for PL2303 So only type the command to enable the putty Sudo chmod 666 /dev/ttyUSB0 Done Open the putty.
The serial port communication programs
moserial
orgtkterm
provide an easy way to check connectivity and modify/dev/ttyUSB0
(or/dev/ttyUSB1
!) settings. Even though there maybe only a single USB to RS232 adapter, then
designation/dev/ttyUSBn
can and does change periodically! Bothmoserial
andgtkterm
will show what port designation is relevant in their respective pull down menus when selecting an appropriateport
to use.Check out help.ubuntu.com/community/Minicom for details on
minicom
.