[SOLVED] how do I access/enable the ttyUSB0 port in the /dev directory of Fedora 17 ?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
how do I access/enable the ttyUSB0 port in the /dev directory of Fedora 17 ?
I need to access the ttyUSB0 port on my labtop. I am using minicom and Fedora 17. When I check the /dev directory there is a listing of all the other ports (i.e. tty0, ttyS0, usbmon0, usbmon1 etc ...) but no listing for ttyUSB0. What do I have to do enable and access it ? Your help would be much appreciated.
I have a mini2440 (i.e. target) attached to one of my usb ports.
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 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines E730, Acer sub-brand)
Bus 002 Device 003: ID 045e:0053 Microsoft Corp. Optical Mouse
I am using a NFS to download executable images to the target. In order to achieve this objective I need to establish communication through one of my USB ports. The user guide accompanying the ELLK kit requires one to configure a port and suggests ttyS0, ttyS1, or if you are using USB to serial convertor, the correct device is most likely ttyUSB0. Based on this I surmise that I am after ttyUSB0 ? I have tried all the others listed in /dev including usbmon0, usbmon1, usbmon2, and ttyS0, ttyS1. At best I got a stream of characters (i.e. gibberish) when configuring the port as usbmon0 this occured when I hit the reset button on the target. I take this as a good sign although I have since come to understand that usbmon0 port is special port and although it is behaving as it should it is not the one that I am after. On a further note my mouse also produces the same gibberish that occurs with the reset button. I really appreciate your efforts here.
I'm not real familiar with the mini2440. The documentation found indicates the serial cable is not USB. Is their a nine pin connector on your device? The 9 pin connector would connect to a real serial port (ttyS0) or USB adapter (ttyUSB0) on the PC.
I have the serial port cable that came with the kit connected to the console port on the mini2440 and at the other end I have the cable connected directly the usb port on my computer.
What do the two ends of the cable look like? From what it looks like on their site, the console port is your typical DE9 RS-232 port, not USB, and it doesn't look like they provide a USB to serial adapter, you would need to purchase one yourself. It's going to have a DE9 connector on one side and a USB-A connector on the other side.
/dev/ttyUSB0 won't be created until you plug in a USB to serial adapter. Since you're not seeing it, that tells me you're not using a USB to serial adapter currently, or it's not being recognized by the system (this would be rare, I've used tons of different USB to serial adapters in Linux and have never found one that didn't work immediately out of the box).
Last edited by suicidaleggroll; 12-14-2013 at 10:42 AM.
The serial cable that I have connected to the labtop is illustrated in the USB-A pictures. The end that is connected to usb port on my labtop is the one second from the right with the other end connected directly to the target 1st from the right. I am not familiar with the term console that you were refering to and I had mistakenly thought it was the port on the target that the 1st from the right plugged into. No matter my bad.
The user guide is rather vague, and it mentions at one point that I am to connect the serial cable to the workstation port selected in the minicom setup and plug the other end into the target. There is no mention of the need for a usb to serial adapter as it goes on to say be sure to use the cable that came with the kit. Most female-to-female serial cables ae crossovers (null modem) but the cable for the Mini2440 is straight through. Do I still require a usb to serial adapter ? Again I really appreciate the efforts that you have made.
That's not a serial cable, that's a USB cable. You need a 9 pin (DE9) RS-232 serial cable (I'm guessing the board came with one of these too?). If your computer does not have a 9 pin DE9 serial port, then you need a USB to serial adapter like this one: http://www.amazon.com/Tripp-Lite-Ser...serial+adapter
As for crossover (null modem) versus straight, you probably need null modem, but I usually find it's easiest to just get a null modem adapter and then use it or not with either type of cable (it turns straight through into null modem and null modem into straight through). Something like this: http://www.monoprice.com/Product?c_i...seq=1&format=2
Also be advised
Fedora 17 is and has been UNSUPPORTED for the last 6 months
Fedora 18 will hit it's End of Life in a month or so
you might want to install fedora 19
And/or in about 30 days install fedora 20