Serial Programming HOWTO PDF
Serial Programming HOWTO PDF
Gary Frerking
gary@frerking.org
Peter Baumann
Revision History Revision 1.01 20010826 New maintainer, converted to DocBook Revision 1.0 19980122 Initial document release Revised by: glf Revised by: phb
This document describes how to program communications with devices over a serial port on a Linux box.
Table of Contents
1. Introduction.....................................................................................................................................................1 1.1. Copyright Information......................................................................................................................1 1.2. Disclaimer.........................................................................................................................................1 1.3. New Versions....................................................................................................................................2 1.4. Credits...............................................................................................................................................2 1.5. Feedback...........................................................................................................................................2 2. Getting started.................................................................................................................................................3 2.1. Debugging.........................................................................................................................................3 2.2. Port Settings......................................................................................................................................3 2.3. Input Concepts for Serial Devices....................................................................................................4 2.3.1. Canonical Input Processing..............................................................................................4 2.3.2. NonCanonical Input Processing.....................................................................................4 2.3.3. Asynchronous Input..........................................................................................................4 2.3.4. Waiting for Input from Multiple Sources.........................................................................4 3. Program Examples ..........................................................................................................................................6 3.1. Canonical Input Processing ...............................................................................................................6 3.2. NonCanonical Input Processing.....................................................................................................8 3.3. Asynchronous Input..........................................................................................................................9 3.4. Waiting for Input from Multiple Sources.......................................................................................11 4. Other Sources of Information......................................................................................................................13
1. Introduction
This is the Linux Serial Programming HOWTO. All about how to program communications with other devices / computers over a serial line under Linux. Different techniques are explained: Canonical I/O (only complete lines are transmitted/received), asyncronous I/O, and waiting for input from multiple sources. This is the first update to the initial release of the Linux Serial Programming HOWTO. The primary purpose of this update is to change the author information and convert the document to DocBook format. In terms of technical content, very little if anything has changed at this time. Sweeping changes to the technical content aren't going to happen overnight, but I'll work on it as much as time allows. If you've been waiting in the wings for someone to take over this HOWTO, you've gotten your wish. Please send me any and all feedback you have, it'd be very much appreciated. All examples were tested using a i386 Linux Kernel 2.0.29.
1.2. Disclaimer
No liability for the contents of this documents can be accepted. Use the concepts, examples and other content at your own risk. As this is a new edition of this document, there may be errors and inaccuracies, that may of course be damaging to your system. Proceed with caution, and although this is highly unlikely, the author(s) do not take any responsibility for that. All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. 1. Introduction 1
Serial Programming HOWTO Naming of particular products or brands should not be seen as endorsements. You are strongly recommended to take a backup of your system before major installation and backups at regular intervals.
1.4. Credits
The original author thanked Mr. Strudthoff, Michael Carter, Peter Waltenberg, Antonino Ianella, Greg Hankins, Dave Pfaltzgraff, Sean Lincolne, Michael Wiedmann, and Adrey Bonar.
1.5. Feedback
Feedback is most certainly welcome for this document. Without your submissions and input, this document wouldn't exist. Please send your additions, comments and criticisms to the following email address : <gary@frerking.org>.
2. Getting started
2.1. Debugging
The best way to debug your code is to set up another Linux box, and connect the two computers via a nullmodem cable. Use miniterm (available from the LDP programmers guide (ftp://sunsite.unc.edu/pub/Linux/docs/LDP/programmersguide/lpg0.4.tar.gz in the examples directory) to transmit characters to your Linux box. Miniterm can be compiled very easily and will transmit all keyboard input raw over the serial port. Only the define statement #define MODEMDEVICE "/dev/ttyS0" has to be checked. Set it to ttyS0 for COM1, ttyS1 for COM2, etc.. It is essential for testing, that all characters are transmitted raw (without output processing) over the line. To test your connection, start miniterm on both computers and just type away. The characters input on one computer should appear on the other computer and vice versa. The input will not be echoed to the attached screen. To make a nullmodem cable you have to cross the TxD (transmit) and RxD (receive) lines. For a description of a cable see sect. 7 of the SerialHOWTO. It is also possible to perform this testing with only one computer, if you have two unused serial ports. You can then run two miniterms off two virtual consoles. If you free a serial port by disconnecting the mouse, remember to redirect /dev/mouse if it exists. If you use a multiport serial card, be sure to configure it correctly. I had mine configured wrong and everything worked fine as long as I was testing only on my computer. When I connected to another computer, the port started loosing characters. Executing two programs on one computer just isn't fully asynchronous.
/* /* /* /* /* /*
input mode flags */ output mode flags */ control mode flags */ local mode flags */ line discipline */ control characters */
This file also includes all flag definitions. The input mode flags in c_iflag handle all input processing, which means that the characters sent from the device can be processed before they are read with read. Similarly c_oflag handles the output processing. c_cflag contains the settings for the port, as the 2. Getting started 3
Serial Programming HOWTO baudrate, bits per character, stop bits, etc.. The local mode flags stored in c_lflag determine if characters are echoed, signals are sent to your program, etc.. Finally the array c_cc defines the control characters for end of file, stop, etc.. Default values for the control characters are defined in <asm/termios.h>. The flags are described in the manual page termios(3). The structure termios contains the c_line (line discipline) element, which is not used in POSIX compliant systems.
Serial Programming HOWTO The approach presented below seems rather complex, but it is important to keep in mind that Linux is a multiprocessing operating system. The select system call will not load the CPU while waiting for input, whereas looping until input becomes available would slow down other processes executing at the same time.
3. Program Examples
All examples have been derived from miniterm.c. The type ahead buffer is limited to 255 characters, just like the maximum string length for canonical input processing (<linux/limits.h> or <posix1_lim.h>). See the comments in the code for explanation of the use of the different input modes. I hope that the code is understandable. The example for canonical input is commented best, the other examples are commented only where they differ from the example for canonical input to emphasize the differences. The descriptions are not complete, but you are encouraged to experiment with the examples to derive the best solution for your application. Don't forget to give the appropriate serial ports the right permissions (e. g.: chmod a+rw /dev/ttyS1)!
/* baudrate settings are defined in <asm/termbits.h>, which is included by <termios.h> */ #define BAUDRATE B38400 /* change this definition for the correct port */ #define MODEMDEVICE "/dev/ttyS1" #define _POSIX_SOURCE 1 /* POSIX compliant source */ #define FALSE 0 #define TRUE 1 volatile int STOP=FALSE; main() { int fd,c, res; struct termios oldtio,newtio; char buf[255]; /* Open modem device for reading and writing and not as controlling tty because we don't want to get killed if linenoise sends CTRLC. */ fd = open(MODEMDEVICE, O_RDWR | O_NOCTTY ); if (fd <0) {perror(MODEMDEVICE); exit(1); } tcgetattr(fd,&oldtio); /* save current serial port settings */ bzero(&newtio, sizeof(newtio)); /* clear struct for new port settings */ /* BAUDRATE: Set bps rate. You could also use cfsetispeed and cfsetospeed. CRTSCTS : output hardware flow control (only used if the cable has all necessary lines. See sect. 7 of SerialHOWTO) CS8 : 8n1 (8bit,no parity,1 stopbit)
3. Program Examples
*/ newtio.c_cflag = BAUDRATE | CRTSCTS | CS8 | CLOCAL | CREAD; /* IGNPAR ICRNL : ignore bytes with parity errors : map CR to NL (otherwise a CR input on the other computer will not terminate input) otherwise make device raw (no other input processing) */ newtio.c_iflag = IGNPAR | ICRNL; /* Raw output. */ newtio.c_oflag = 0; /* ICANON : enable canonical input disable all echo functionality, and don't send signals to calling program */ newtio.c_lflag = ICANON; /* initialize all control characters default values can be found in /usr/include/termios.h, and are given in the comments, but we don't need them here */ newtio.c_cc[VINTR] newtio.c_cc[VQUIT] newtio.c_cc[VERASE] newtio.c_cc[VKILL] newtio.c_cc[VEOF] newtio.c_cc[VTIME] newtio.c_cc[VMIN] newtio.c_cc[VSWTC] newtio.c_cc[VSTART] newtio.c_cc[VSTOP] newtio.c_cc[VSUSP] newtio.c_cc[VEOL] newtio.c_cc[VREPRINT] newtio.c_cc[VDISCARD] newtio.c_cc[VWERASE] newtio.c_cc[VLNEXT] newtio.c_cc[VEOL2] /* now clean the modem line and activate the settings for the port */ tcflush(fd, TCIFLUSH); tcsetattr(fd,TCSANOW,&newtio); /* terminal settings done, now handle input In this example, inputting a 'z' at the beginning of a line will exit the program. */ while (STOP==FALSE) { /* loop until we have a terminating condition */ /* read blocks program execution until a line terminating character is input, even if more than 255 chars are input. If the number of characters read is smaller than the number of chars available, = = = = = = = = = = = = = = = = = 0; 0; 0; 0; 4; 0; 1; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* Ctrlc */ Ctrl\ */ del */ @ */ Ctrld */ intercharacter timer unused */ blocking read until 1 character arrives */ '\0' */ Ctrlq */ Ctrls */ Ctrlz */ '\0' */ Ctrlr */ Ctrlu */ Ctrlw */ Ctrlv */ '\0' */
3. Program Examples
/* set input mode (noncanonical, no echo,...) */ newtio.c_lflag = 0; newtio.c_cc[VTIME] newtio.c_cc[VMIN] = 0; = 5; /* intercharacter timer unused */ /* blocking read until 5 chars received */
while (STOP==FALSE) { /* loop for input */ res = read(fd,buf,255); /* returns after 5 chars have been input */ buf[res]=0; /* so we can printf... */ printf(":%s:%d\n", buf, res); if (buf[0]=='z') STOP=TRUE; } tcsetattr(fd,TCSANOW,&oldtio); }
volatile int STOP=FALSE; void signal_handler_IO (int status); int wait_flag=TRUE; main() { int fd,c, res; struct termios oldtio,newtio; struct sigaction saio; char buf[255]; /* definition of signal handler */ /* TRUE while no signal received */
/* open the device to be nonblocking (read will return immediatly) */ fd = open(MODEMDEVICE, O_RDWR | O_NOCTTY | O_NONBLOCK); if (fd <0) {perror(MODEMDEVICE); exit(1); } /* install the signal handler before making the device asynchronous */ saio.sa_handler = signal_handler_IO; saio.sa_mask = 0; saio.sa_flags = 0; saio.sa_restorer = NULL; sigaction(SIGIO,&saio,NULL); /* allow the process to receive SIGIO */ fcntl(fd, F_SETOWN, getpid()); /* Make the file descriptor asynchronous (the manual page says only O_APPEND and O_NONBLOCK, will work with F_SETFL...) */ fcntl(fd, F_SETFL, FASYNC); tcgetattr(fd,&oldtio); /* save current port settings */ /* set new port settings for canonical input processing */ newtio.c_cflag = BAUDRATE | CRTSCTS | CS8 | CLOCAL | CREAD; newtio.c_iflag = IGNPAR | ICRNL; newtio.c_oflag = 0; newtio.c_lflag = ICANON; newtio.c_cc[VMIN]=1; newtio.c_cc[VTIME]=0; tcflush(fd, TCIFLUSH); tcsetattr(fd,TCSANOW,&newtio); /* loop while waiting for input. normally we would do something useful here */ while (STOP==FALSE) { printf(".\n");usleep(100000); /* after receiving SIGIO, wait_flag = FALSE, input is available and can be read */ if (wait_flag==FALSE) { res = read(fd,buf,255); buf[res]=0; printf(":%s:%d\n", buf, res); if (res==1) STOP=TRUE; /* stop loop if only a CR was input */ wait_flag = TRUE; /* wait for new input */ } } /* restore old port settings */ tcsetattr(fd,TCSANOW,&oldtio); } /*************************************************************************** * signal handler. sets wait_flag to FALSE, to indicate above loop that * * characters have been received. * ***************************************************************************/ void signal_handler_IO (int status) { printf("received SIGIO signal.\n"); wait_flag = FALSE; }
10
/* /* /* /*
input sources 1 and 2 */ file descriptor set */ maximum file desciptor used */ loop while TRUE */
/* open_input_source opens a device, sets the port correctly, and returns a file descriptor */ fd1 = open_input_source("/dev/ttyS1"); /* COM2 */ if (fd1<0) exit(0); fd2 = open_input_source("/dev/ttyS2"); /* COM3 */ if (fd2<0) exit(0); maxfd = MAX (fd1, fd2)+1; /* maximum bit entry (fd) to test */ /* loop for input */ while (loop) { FD_SET(fd1, &readfs); /* set testing for source 1 */ FD_SET(fd2, &readfs); /* set testing for source 2 */ /* block until input becomes available */ select(maxfd, &readfs, NULL, NULL, NULL); if (FD_ISSET(fd1)) /* input from source 1 available */ handle_input_from_source1(); if (FD_ISSET(fd2)) /* input from source 2 available */ handle_input_from_source2(); } }
The given example blocks indefinitely, until input from one of the sources becomes available. If you need to timeout on input, just replace the select call by:
int res; struct timeval Timeout; /* set timeout value within input loop */ Timeout.tv_usec = 0; /* milliseconds */ Timeout.tv_sec = 1; /* seconds */ res = select(maxfd, &readfs, NULL, NULL, &Timeout); if (res==0) /* number of file descriptors with input = 0, timeout occurred. */
11
Serial Programming HOWTO This example will timeout after 1 second. If a timeout occurs, select will return 0, but beware that Timeout is decremented by the time actually waited for input by select. If the timeout value is zero, select will return immediatly.
12
13