Aug 14, 2016 - I solved this by using minicom. See, I had the same issue installing ubuntu on my pandaboard. Working with the serial console. From ArchWiki. Jump to: navigation, search. (PuTTY or Minicom, for example). The configuration instructions below will enable GRUB menu selection, boot messages, and terminal forwarding to the serial console. 1 Configuration.
![Minicom serial port Minicom serial port](http://blog-imgs-24.fc2.com/i/t/m/itmst/e00022_minicom_set02.png)
Over the weekend, I was showing Linux and Packet radio and for some reason I could not talk to my TNC, a KPC 3+. It was at this point that I realized I had forgotten more about Linux (and minicom) than I had about the commands needed to control the TNC. So, in the interest of helping save you some time, here is a quick write up on using minicom with a USB/Serial adapter to talk to your TNC, specifically, a KPC.
![Serial Serial](/uploads/1/2/5/6/125698044/766478649.png)
Minicom is an old school program that is available for most of the distributions but may not be installed by default. The good news: it is in all the repositories, so you can pull it down and install it quickly.
It is a serial terminal program that runs from the command line, but can sometimes be a little fussy to get working, and I will admit that I have not used minicom with a USB/Serial converter.
First, you have to know what tty port your USB/Serial converter is
on. So, plug it in, give it a minute and then type at a console port:
on. So, plug it in, give it a minute and then type at a console port:
dmesg | grep tty
You should get something like this back:
kg4giy@kauai:/$ dmesg | grep tty
[ 0.001982] console [tty0] enabled
[ 686.529224] usb 2-2: pl2303 converter now attached to ttyUSB0
In this case, the converter is attached to ttyUSB0, you when you
configure minicom, you want to use /dev/ttyUSB0 as the serial port
setting.
configure minicom, you want to use /dev/ttyUSB0 as the serial port
setting.
To start minicom then (assuming you have not configured it, but you
know the modem speed of the TNC) type:
know the modem speed of the TNC) type:
$ sudo minicom -s
Note that minicom requires root privileges. You will be prompted for
your password.
your password.
Select 'Serial port set up' from the list with the cursor keys and set
the serial device and the Bps/par/bits (8/N/1 and whatever the speed
of your TNC is). Press , Save setup as dfl to save your
settings and then select Exit to enter minicom.
the serial device and the Bps/par/bits (8/N/1 and whatever the speed
of your TNC is). Press , Save setup as dfl to save your
settings and then select Exit to enter minicom.
Turn on the TNC. Press once or twice if you do not get the
TNC cmd: prompt and you should now have control of the TNC.
TNC cmd: prompt and you should now have control of the TNC.
When you are done, A then Z will bring up the help menu and you
can exit by pressing Q or A Q to exit.
can exit by pressing Q or A Q to exit.
One thing to note. Minicom has a much smaller set of connection speeds. For overall interoperability, it is best to set the baud rate of your TNC to 9600, with 8-n-1 for parity. This will facilitate connectivity with a multitude of devices, including a simple VT220.
I hope this saves you all a few minutes!
It seems like I have been working with Mac OS X serial ports a lot lately. Since the Mac in question is hundreds of miles away, I've been doing all of this via the command line using tools like kermit and minicom. One error that we ran into recently was the following:
This error is the result of a lock file hanging around. If you don't know the location of the lock file, it might be helpful to check your local minicom configuration file to see if it has been moved:
As you can see, the configuration file indicates
/tmp
is the lock directory. Lo and behold:If the application is running, you should try to shut it down cleanly. If not, deleting the lock file should solve your problem.