APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS











(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Home > FAQ > What do the terms UART, 8250, 16450 and 16550 mean?
Printer Friendly Version




SCO Unix ® FAQ section

Serial Communications and UUCP



This article is from a FAQ concerning SCO operating systems. While some of the information may be applicable to any OS, or any Unix or Linux OS, it may be specific to SCO Xenix, Open Desktop or Openserver.

There is lots of Linux, Mac OS X and general Unix info elsewhere on this site: Search this site is the best way to find anything.

What do the terms UART, 8250, 16450 and 16550 mean?



UART means Universal Asynchronous Receiver/Transmitter. This is a chip which receives and transmits data serially; each serial port you have will use one, though it is possible that several may be integrated into one chip.

8250, 16450 and 16550 are all common types of UARTs. The 8250 is an old chip which cannot run at high speed. The 16450 is similar to the 8250 except that it supports data communications at higher speeds. Both of these chips generate an interrupt for every character that is sent or received, which basically tells the CPU either "Here is some data for you" or "Feed me!" This is all very well, except that at high speed, the number of interrupts (nearly 4000 per port per second at 38 400 bps) can overwhelm a CPU, bringing system performance way down. Also, if the CPU is busy servicing another interrupt at the time, the serial port's interrupt may not be serviced in time, which will cause a character to be lost.

The 16550 is pin-compatible with the 16450 and, by default, runs in 16450 mode. This makes it compatible with software which is not 16550-aware. If your software is 16550-aware, it can turn on a special mode in which the 16550 buffers all data with 16-byte internal buffers. This not only allows the CPU to deal with far more bytes at a time, increasing efficiency, but also means that if the CPU can't service the interrupt before the next character comes in, there's still space in the buffer for it.



16550 support was introduced in Xenix 2.3.4, ODT 1.1 and Unix 3.2.2. If you have these, or later, versions, your operating system will automatically detect 16550-equipped ports and will enable their buffering. A third-party serial driver called FAS includes 16550 awareness in its feature set; you may wish to investigate this as well. FAS can be found at ftp://ftp.fu-berlin.de/pub/unix/driver/fas/.

Note that the above is not really applicable to intelligent multiport serial cards. While these cards may well use 16550s, it is the processor on the serial card which is responsible for dealing with the serial ports it controls, and the main CPU has nothing to do with the UARTs.

If this page was useful to you, please click to help others find it:  

Your +1's can help friends, contacts, and others on the web find the best stuff when they search.

Comments?



Click here to add your comments


---August 11, 2004

Hi. Is there anyone who wants to let me know why the FIFO is useful when getting data with the UART? Thanks in advance. --Guest




---August 11, 2004

It's a buffer that allows the cpu the luxury of not responding to every single incoming character. Basically, at high speeds, the characters come too quickly for the cpu to guarantee that it won't be busy doing something else when the serial port gets the bytes. The buffer stores the characters.


--TonyLawrence





Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



Auto FTP Manager

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!


book graphic unix and linux troubleshooting guide




 I sell and support
 Kerio Mail server
g_face.jpg

This post tagged:

       - FAQ
       - Serial




Unix/Linux Consultants

Skills Tests

Guest Post Here