RPi Serial Connection
Back to RPi Advanced Setup.
The Serial Port is a low-level way to send data between the Raspberry Pi and another computer system. There are two main ways in which it can be used:
- Connecting to a PC to allow access to the Linux console. This can help to fix problems during boot, or to log in to the Pi if the video and network are not available.
- Connecting to a microcontroller or other peripheral which has a serial interface. This can be useful if you want the Pi to control another device.
Connection to a PC
Note that the Raspberry Pi cannot be wired directly to an RS232 serial port. To do so, some additional electronics are required!
A UART is available in the Broadcom SoC, and its RxD and TxD lines are available on the GPIO header. However, these use 0 and 3.3V logic levels, not the +/-12V used by RS-232 serial ports. If you wish to connect one of these, you need a board or adapter to convert the signal levels. See this tutorial for one example on how to build a 3.3V to RS-232 level converter with a breadboard, a MAX3232CPE IC and five 0.1 uF capacitors.
If you have a serial connection using 5V logic levels, you should ideally have a circuit to convert between the voltage levels. See this tutorial for an example circuit. For prototyping work, provided the connections are kept short you may connect the GPIO TxD directly to the 5V RxD, and the 5V TxD can be connected via a voltage divider to the GPIO RxD. A 5V to 3V resistor divider can be built from a 2K2 (top) and a 3K3 (bottom) resistor.
When this is done, you will need to set up a terminal emulator program on your PC as described below.
Console serial parameters
The following parameters are needed to connect to the Pi console, and apply on both Linux and Windows.
- Speed (baud rate): 115200
- Bits: 8
- Parity: None
- Stop Bits: 1
- Flow Control: None
Linux terminal set up
You will need to know the port name of your PC's serial port. On Linux this will be:
- Built-in (standard) Serial Port: the Linux standard is /dev/ttyS0, /dev/ttyS1, and so on, but on the raspberry pi, it is /dev/ttyAMA0
- USB Serial Port Adapter: /dev/ttyUSB0, /dev/ttyUSB1, and so on.
- Some types of USB serial adapter may appear as /dev/ttyACM0 ...
You will need to be a member of the dialout group to access this port (for later releases the required group is tty). You can check which is needed with:
ls -l /dev/ttyAMA0
and you will see something like "crw-rw----T 1 root dialout ..." which says root can 'create,read,write' and the group xxx can 'read,write' to the port and everyone else cannot access it.
To find out if you, the current user, is in the group dialout, use the command:
If you do not see dialout listed, add yourself with the command
sudo usermod -a -G dialout username
You then have a choice of terminal emulation programs:
- Super Easy Way Using GNU Screen
Enter the command below into a terminal window
screen port_name 115200
To exit GNU screen, type Control-A k.
- Super Easy Way Using Minicom
Run minicom with the following parameters:
minicom -b 115200 -o -D Port_Name
You can exit minicom with Control-A x
- Tedious Old-Fashioned Way Using Minicom
Another method to setup minicom is described in the Tincantools Minicom Tutorial
- GUI method with GtkTerm
Start GtkTerm, select Configuration->Port and enter the values above in the labeled fields.
Windows terminal set-up
You will need to know the number of your serial (COM) port. Built-in ports are COM0 to COM3, and USB-attached ports are COM4 and upwards.
If you get the prompt below, you are connected to the Raspberry Pi shell!
First command you might want try is "help":
prompt> # help
If you get some output, you are correctly connected to the Raspberry Pi! Congratulations!
Unwanted serial garbage input
Note that on older software by accident the internal pullups of the RxD GPIO pins were not enabled, this could lead to lots of serial garbage being picked up if the GPIO pin was touched, or even if a finger was nearby. In extreme case this could lead to kernel warnings and other problems.
Connection to a microcontroller or other peripheral
The TxD and RxD signals can also be connected directly to similar signals on a microcontroller board like the Arduino provided the signals are all at 3V3 levels. It's still a good idea to put 2K2 series resistors in the lines to prevent damage when two outputs are connected together, which could also happen if a GPIO input pin is accidentally programmed as output.
If your microcontroller uses 5V logic levels, level conversion is usually necessary - see 'Connecting to a PC' for details.
Preventing Linux using the serial port
The Broadcom UART appears as
/dev/ttyAMA0 under Linux. There are several minor things in the way if you want to have dedicated control of the serial port on a Raspberry Pi.
Firstly, the kernel will use the port to output messages during boot, and for kernel debugging. These are caused by the kernel parameter console=ttyAMA0,115200 set in /boot/cmdline.txt
next is the login prompt, set in /etc/inittab with the line T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
kernel debuging is also on the serial port and i dont know what effect it may have on the end-use, so you may want to turn that off also in cmdline.txt, just remove kgdboc=ttyAMA0,115200
once all of those are off, you can use /dev/ttyAMA0 like any normal linux serial port, and you wont get any unwanted traffic confusing the attached devices
some distro's may be setup differently, just double check 'ps aux|grep ttyAMA0' and 'cat /proc/cmdline' to verify ttyAMA0 is not in use anywhere
You can have the RTS0 signal on GPIO 17 (P1-11) if you set it to ALT function 3. Likewise, the CTS0 is available on GPIO 30 (P5-05), if it is set to ALT function 3. You can control the settings of IOs with gpio_setfunc