NextPreviousContentsCommon serial port names are /dev/ttyS0, /dev/ttyS1, etc. Thenaround the year 2000 came the USB bus with names like /dev/ttyUSB0 and/dev/ttyACM1 (for the ACM modem on the USB bus). Multiport serialcard used somewhat differnt names (depending on the brand) such as/dev/ttyE5.
Since DOS provided for 4 serial ports on the old ISA bus:COM1-COM4, or ttyS0-ttyS3 in Linux, most serial ports on the newer PCIbus used higher numbers such as ttyS4 or ttyS14 (prior to kernel2.6.13). But since most PCs only came with one or two serial ports,ttyS0 and possibly ttyS1 (for the second port) the PCI bus can now usettyS2 (kernel 2.6.15 on). All this permits one to have both ISAserial ports and PCI serial ports on the same PC with no nameconflicts. 0-1 (or 0-3) are reserved for the old ISA bus (or thenewer LPC bus) and 2-upward (or 4-upward or 14-upward) are used forPCI, where older schemes are shown in parentheses . It's not requiredto be this way but it often is.
I need a USB device I can use as a target in my Windows USB device driver course. The device needs to be reasonably powerful, and allow me to control how the device appears on the bus via firmware. I’ve used the Arduino in the past, but that thing is really horrible: Slow 8-bit microcontroller. The serial port ttySx (x=0,1,2, etc.) is major number 4. You can see this (and the minor numbers too) by typing: 'ls -l ttyS.' in the /dev directory. To find the device names for various devices, see the 'devices' file in the kernel documentation. There formerly was a 'cua' name for each serial port and it behaved just a little differently.
If you're using udev (which puts only the device you have on yourcomputer into the /dev directory at boottime) then there's an easy wayto change the device names by editing files in /etc/udev/. Forexample, to change the name of what the kernel detects as ttyS3 towhat you want to name it: ttyS14, add a line similar to this to/etc/udev/udev.rules
BUS'pci' KERNEL'ttyS3',NAME='ttyS14'
On-board serial ports on motherboards which have both PCI and ISAslots are likely to still be ISA ports. Even for all-PCI-slotmotherboards, the serial ports are often not PCI. Instead, they areeither ISA, on an internal ISA bus or on a LPC bus which is intendedfor slow legacy I/O devices: serial/parallel ports and floppy drives.
Devices in Linux have major and minor numbers. The serial portttySx (x=0,1,2, etc.) is major number 4. You can see this (and theminor numbers too) by typing: 'ls -l ttyS*' in the /dev directory. Tofind the device names for various devices, see the 'devices' file inthe kernel documentation.
There formerly was a 'cua' name for each serial port and it behavedjust a little differently. For example, ttyS2 would correspond tocua2. It was mainly used for modems. The cua major number was 5 andminor numbers started at 64. You may still have the cua devices inyour /dev directory but they are now deprecated. For details seeModem-HOWTO, section: cua Device Obsolete.
For creating the old devices in the device directory see:
Dos/Windows use the COM name while the messages from the serial driveruse ttyS00, ttyS01, etc. Older serial drivers (2001 ?) used justtty00, tty01, etc.
The tables below shows some examples of serial device names. TheIO addresses are the default addresses for the old ISA bus (not forthe newer PCI and USB buses).
For more info see the usb subdirectory in the kernel documentationdirectory for files: usb-serial, acm, etc.
On some installations, two extra devices will be created,/dev/modem for your modem and /dev/mouse for amouse. Both of these are symbolic links to the appropriatedevice in /dev.
Historical note: Formerly (in the 1990s) the use of/dev/modem (as a link to the modem's serial port) wasdiscouraged since lock files might not realize that it was really say/dev/ttyS2. The newer lock file system doesn't fall intothis trap so it's now OK to use such links.
Inspect the connectors
Inspecting the connectors may give some clues but is often notdefinitive. The serial connectors on the back side of a PC areusually DB connectors with male pins. 9-pin is the most common butsome are 25-pin (especially older PCs like 486s). There may be one9-pin (perhaps ttyS0 ??) and one 25-pin (perhaps ttyS1 ??). For two9-pin ones the top one might be ttyS0.
If you only have one serial port connector on the back of your PC,this may be easy. If you also have an internal modem, a program likewvdial may be able to tell you what port it's on (unless it's a PnPthat hasn't been enabled yet). A report from setserial (atboot-time or run by you from the command line) should help youidentify the non-modem ports.
If you have two serial ports it may be more difficult. You could haveonly one serial connector but actually have 2 ports, one of whichisn't used (but it's still there electronically). First check manuals(if any) for your computer. Look at the connectors for meaningfullabels. You might even want to take off the PC's cover and see ifthere are any meaningful labels on the card where the internal ribbonserial cables plug in. Labels (if any) are likely to say something like'serial 1', 'serial 2' or A, B. Which com port it actually is willdepend on jumper or PnP settings (sometimes shown in a BIOS setupmenu). But 1 or A are more likely to be ttyS0 with 2 or B ttyS1.
Send bytes to the port
Olimex Port Devices Driver Vga
Labels are not apt to be definitive so here's another method. Ifthe serial ports have been configured correctly per setserial, thenyou may send some bytes out a port and try to detect which connector(if any) they are coming out of. One way to send such a signal is tocopy a long text file to the port using a command like: cpmy_file_name /dev/ttyS1. A voltmeter connected to the DTR pin (seeSerial-HOWTO for Pinout) will display a positive voltage as soon asyou give the copy command.
The transmit pin should go from several volts negative to a voltagefluctuating around zero after you start sending the bytes. If it doesn't(but the DTR went positive) then you've got the right port but it'sblocked from sending. This may be due to a wrong IRQ, -clocal beingset, etc. The command 'stty -F /dev/ttyS1 -a' should showclocal (and not -clocal). If not, change it to clocal.
Another test is to jumper the transmit and receive pins (pins 2 and 3of either the 25-pin or 9-pin connector) of a test serial port. Thensend something to each port (from the PCs keyboard) and see if it getssent back. If it does it's likely the port with the jumper on it.Then remove the jumper and verify that nothing gets sent back. Notethat if 'echo' is set (per stty) then a jumper creates an infiniteloop. Bytes that pass thru the jumper go into the port and come rightback out of the other pin back to the jumper. Then they go back inand out again and again. Whatever you send to the port repeats itselfforever (until you interrupt it by removing the jumper, etc.). Thismay be a good way to test it as the repeating test messages halt whenthe jumper is removed.
As a jumper you could use a mini (or micro) jumper cable (sold in someelectronic parts stores) with mini alligator clips. A small scrap ofpaper may be used to prevent the mini clips from making electricalcontact where it shouldn't. Metal paper clips can sometimes be bentto use as jumpers. Whatever you use as a jumper take care not to bendor excessively scratch the pins. To receive something from a port,you can go to a virtual terminal (for example Alt-F2 and login) andtype something like 'cp /dev/ttyS2 /dev/tty'. Then at another virtualterminal you may send something to ttyS2 (or whatever) by 'echotest_message > /dev/ttyS2'. Then go back to the receive virtualterminal and look for the test_message. See Serial Electrical Test Equipment for more info.
Connect a device to the connector
Another way to try to identify a serial port is to connect somephysical serial device to it and see if it works. But a problem hereis that it might not work because it's not configured right. A serialmouse might get detected at boot-time if connected.
You may put a device, such as a serial mouse (use 1200 baud), on a portand then use minicom or picocom to communicate with that port. Thenby clicking on the mouse, or otherwise sending characters with thedevice, see if they get displayed. It not you may have told picocomthe wrong port (such as ttyS0 instead of ttyS1) so try again.
Missing connectors
If the software shows that you have more serial ports than youhave connectors for (including an internal modem which counts as aserial port) then you may have a serial port that has no connector.Some motherboards come with a serial port with no cable or externalserial DB connector. Someone may build a PC from this and decide notto use this serial port. There may be a 'serial' connector and labelon the motherboard but no ribbon cable connects to its pins. To usethis port you must get a ribbon cable and connector. I've seendifferent wiring arrangements for such ribbon cables so beware.
If you don't use devfs (which automatically creates such devices) anddon't have a device 'file' that you need, you will have to create it.Use the mknod command or with the MAKEDEV shell script.Example, suppose you needed to create ttyS0:
ttyS0 you would just type:If the above command doesn't work (and you are the root user), lookfor the MAKEDEV script in the /dev directory and run it.
This handles the devices creation and should set the correct permissions.For making multiport devices see Making multiport devices in the /dev directory.
NextPreviousContents≡3-IN-1 fast USB ARM JTAG, USB-to-RS232 virtual port and power supply 5-9-12VDC device (supported by OpenOCD ARM debugger software)| Price | 54.95EUR |
|---|---|
| 10 - 49 pcs | 49.46EUR |
| 50 - 10000 pcs | 43.96EUR |
FEATURES
- First on market three-in-one USB JTAG debugger - offers JTAG + RS232 (full modem signals supported) port + power supply all in one compact device
- Adds virtual RS232 port to your computer with all modem signals like: DTR, DSR, DCD, RTS, CTS, Rx, Tx
- Debugs all ARM microcontrollers with JTAG interface supported by OpenOCD
- Can be used to power your target board with three jumper-selectable power supplies: 5V, 9V and 12VDC; USB source current is limited with resetable fuse at 300mA, at the different output voltages the maximum current is different: 5V/200mA, 9V/100mA, 12V/70mA, note that this also depends on your USB host current capabilities, if other USB devices are attached to your computer or if the laptop is running on batteries these figures may be different and would depend on your computer USB host. Cable for the external powering included - 2.1x5.5x14mm female connectors at both ends
- Uses ARM's standard JTAG connector (2 rows × 10 pins at 0.1' step)
- Supports ARM targets working in voltage range 2.0 – 5.0 V DC
- Supported by the open-source community and OpenOCD debugger software
- Downloadable Windows installer for full featured and open source tools as alternative to the commercial ARM development packages: GCC C compiler, OpenOCD debugger and Eclipse IDE.
- Works with IAR EW for ARM via GDB server
- Works with Rowley Crossworks IDE
- Works with CooCox IDE
- Supported in Windows, Linux and Mac
- Dimensions 50x40mm ~ (2x1.6)' + 20cm ~ 8' JTAG cable - ribbon cable included
HARDWARE
SOFTWARE
- Additional resources: tutorials, instructions, demo software, customer projects, older drivers and more might be found at the wiki page: ARM-USB-OCD article
FAQ
- Can I use ARM-USB-OCD with EW-ARM?
- IAR EW has support for GDB and works with ARM-USB-OCD.
- I am currently using operating system X. It has FTDI drivers, how should I alter them to work with my installation?
- FTDI provide drivers and instructions at their web site, download them and use our ARM-USB-OCD PID: 0x0003, VID: 0x15BA to install the drivers.
- I have LPC1227 board and can't program it with your OpenOCD debugger. What do I do wrong?
- LPC1227 lacks JTAG according to the microcontroller's datasheet. The board can be programmed only via SWD (Serial Wire Debug) interface. Olimex OpenOCD debuggers have JTAG by default. You would need an addiitonal adapter – ARM-JTAG-SWD.
- How to install ARM-USB-OCD to work with CrossWorks
Test with the FTDI drivers. The FTDI drivers can be downloaded from the following address:
https://www.olimex.com/Products/ARM/JTAG/_resources/OLIMEX-FTDI-drivers-2-12-04.zip
There is already profile for ARM-USB-OCD in CrossWorks but if you want to use it as 'Generic FTD2232' target interface you have to do as follows:- Right click on a blank space in the targets window and select 'New Target Interface > Generic FT2232 Device'.
- Right click on the new target interface and select 'Properties' - set the following properties:
Connected LED Inversion Mask 0x0000
Connected LED Mask = 0x0800
nSRST Inversion Mask = 0x0200
nSRST Mask = 0x0200
nTRST Inversion Mask = 0x0000
nTRST Mask = 0x0100
Output Pins = 0x0F1B
Output Value = 0x0D08
Running LED Inversion Mask = 0x0000
Running LED Mask = 0x0800
PID: 0x0003
VID: 0x15BAIn CrossWorks 1.7 there are Target interfaces for Olimex JTAGs, note that RTCK is not used with a FT2232 design so your JTAG clock should not exceed 1/6 of your target MCU clock or the JTAG will lock up. Start with JTAG divider 10 and decrease until you are able to debug to find your own value for your target.
- Can I debug high voltage targets with ARM-USB-OCD?
- ARM-USB-OCD is not isolated, but you can use a USB-ISO isolator device to protect your PC while debugging high voltage targets.
- Howdy, guys. I can't program my MSP430 and PIC16 boards with your robust debugger. I need help ASAP.
- Technically, it is possible to program targets different than ARM using our OpenOCD debugger. Practically, almost all users use the debugger for ARM programming and only ARM targets are officially supported. There is a reason that the prefix in the name of the debugger is 'ARM-'.
- I am the maintainer of a commercial IDE with custom debugger code. I want to include support for your OpenOCD tools in my software, however I can't find specific information. It is obviously a win-win situation for both parties. Is it possible to provide me with more specific technical information for your debuggers?
- Olimex can provide the necessary information and cooperate with interested parties if they want to add low-cost USB debugger support to their C compilers and IDEs.
Related Products - People who bought this product also bought
ARM debugger with JTAG and SWD interfaces, based on CoLinkEX
High-speed 3-IN-1 fast USB ARM JTAG, USB-to-RS232 virtual port and power supply 5VDC device (supported by OpenOCD arm debugger)
Olimex Port Devices Driver
Olimex Port Devices Driver Device
Low-cost high-speed ARM USB JTAG (supported by the OpenOCD arm debugger)