Ubuntu Serial Terminal Client
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?
Minicom is a text-based serial port communications program. It is used to talk to external RS-232 devices such as mobile phones.
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: 805 usb 2-1: pl2303 converter now attached to ttyUSB0 Mar 13 23:34:44 ubuntu kernel: 829 usb 2-1: USB disconnect, address 7 Mar 13 23:34:44 ubuntu kernel: 821 pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 Mar 13 23:34:44 ubuntu kernel: 874 pl2303 2-1:1.0: device disconnected Mar 13 23:34:52 ubuntu kernel: 856 usb 2-1: new full speed USB device using uhcihcd and address 8 Mar 13 23:34:52 ubuntu kernel: 845 pl2303 2-1:1.0: pl2303 converter detected Mar 13 23:34:52 ubuntu kernel: 809 usb 2-1: pl2303 converter now attached to ttyUSB0. I get get the same minicom error, 'cannot open /dev/ttyUSB0: No such file or directory' Three notes:. I get the error when the device attached to the serial port end of my Prolific Technology PL2303 USB/Serial adapter is turned off. After turning on the device (an embedded controller running Linux) minicom connected fine. I have to run as super user (i.e sudo minicom). Sometimes I have to unplug and plug back in the USB/Serial adapter to get minicom to connect to it. I am running Ubuntu 10.04 LTS under VMWare (runing on Windows 7).
In this situation, make sure the device is attached to VM operating system by right clicking on the USB/Serial usb icon in the lower right of the VMWare window and select Connect (Disconnet from Host) Remember to press Ctrl-A to get minicoms prompt, type X to exit the program. Just exiting the terminal session running minicom, will leave the process running. I just got my GUC232A cable with molded in pl2302 converter chip. In additon to adding myself and br to group dialout, I found in the README.Debian file in /usr/share/doc/bottlerocket. This helpful tip: This package uses debconf to configure the /dev/firecracker symlink, should you need to change the symlink in the future run this command: dpkg-reconfigure -pmedium bottlerocket That will then prompt you for your new serial port and modify the symlink.
Ubuntu Developer Portal
This is required for proper use of bottlerocket. I did that and voila! Bottlerocket is able to communicate with my X-10 devices.
Ubuntu Serial Terminal
You should probably try this in three steps: 1. Setup a terminal emulator program on the Host side. Test the login program on the VM side. Setup Ubuntu to boot with a serial console.
Step #2 will verify that you have a working virtual serial link before attempting the more complex step #3. Otherwise step #2 is just a test, and not a required step in setting up a serial console. The first half of step #3 may suffice for your requirements (which you have not described) and then you won't have to do any boot parameter modifications.
Step 1: setup a terminal emulator program on the Host side. Follow the VMware guide that you mention for 'Connecting an Application on the Host to a Virtual Machine'. The 'application on the Host' will be a terminal emulator program such a HyperTerminal, Putty or TeraTerm (the later two are preferred and multi-platform). You are going to use only the bare essentials of the terminal emulator program; you do not need any SSH or telnet or even modem capability. Configure the Host's terminal emulator for VT102 emulation and the port to 115200 baud, 8 data bits, no parity, 1 stop bit. Use the lowest numbered serial port (e.g. COM1 or ttyS0) from VMware.
Step 2: test the login program on the VM (Ubuntu) side. Use the lowest numbered serial port, /dev/ttyS0. Make sure your username is a member of group 'dialout' (which should own /dev/ttyS0). Configure the virtual serial port at the Ubuntu shell prompt: $ stty -F /dev/ttyS0 cs8 -parenb -cstopb 115200 $ echo Hello world /dev/ttyS0 Inspect the terminal emulator program for output. Execute the login program for the serial connection.
$ sudo getty -8L 115200 ttyS0 VT102 Try to login at the terminal emulator program. Step 3: setup Ubuntu to boot with a serial console. If you get this far, then you should use the.
The 'Configuring the console login process' will use the same getty that was tested in the previous step. This configuration is to ensure that getty is re-executed (or 'respawned') at the appropriate runlevels and after each logoff. Note that there are different startup procedures depending on the version of Ubuntu, so I won't bother trying to reiterate that here.
Configuring grub(or whatever virtual bootloader) might be optional for you. At this point you would have a setup that provides the serial port as a user login terminal.
If you proceed to make changes to the boot parameters for the kernel command line, then all you will get is make visible the kernel output during boot.