These three header files are available in the arm-linux-gnueabi toolchain. Each has their own set of functions that, when put together, allow for the programmer to develop a program for serial communication.

To write your own serial communication program, there are three header files that you will need: fcntl.h, termios.h, unistd.h. program, I’ll just a mention couple things: the first is to define exactly which header files you’ll need and how they can help you the second is to provide a list of resources that helped me get started. After I go over the steps necessary for successful serial communication, I’ll leave you with an example on sending/receiving data using an XBee transceiver. Rather than go step-by-step on how to go about writing your own serial comm. Please take note that I have not been able to configure the communication ports for bi-directional use, only for one direction. If you’re using C/C++, you will need several particular header files to do so. Ports 1, 2, 4, and 5 can be programmed by the user. There are six ports: ttyO0 through ttyO5. In Linux, serial communication is done through ports labeled with the prefix “TTY”, and in the BeagleBone it will be no different. Programming a BeagleBone for serial communication is easy in C++, but may initially be a little confusing if you’re not familiar with the requirements. That means the UARTs are initialized in the omap_mux directory, which has been subsequently removed in the newer kernel versions. EDIT: I’ve moved the files to a Git repository, and included the function that initializes all UARTs that should be available to the user.

Linux c serial port example