0% found this document useful (0 votes)

2 views49 pages

UART

The document provides an overview of serial communication, detailing its types, including synchronous and asynchronous transmission, and the specifics of protocols like UART. It explains how data is transmitted and received, error detection methods, and the software structure for handling serial communications. Additionally, it covers the UART's operational parameters and its role in converting data between parallel and serial formats.

Uploaded by

pasqualed70

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

2 views49 pages

UART

Uploaded by

pasqualed70

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Serial Communications

Ing. Gianni Cario

Serial Communication
▪ Serial communication
▪ Transmits data one bit at a time, in a sequential fashion
▪ In contrast to parallel communication, in which multiple bits are sent as a whole at the same time
▪ Commonly used for long-haul communication, modems and non-networked communication between
devices
▪ Example are UART, SPI, I2C, USB, Ethernet PCI Express etc.

1 1
0 0
1 1
1 1
10111001 1
1 0 1 1 1 0 0 1 1 0
0 0
0 1
1
Serial communication Parallel communication
Types of Serial Communication
▪ Synchronous Serial Transmission

➢ A common clock is shared by both the sender and the receiver

➢ More efficient transmission, since one wire is dedicated for data transfer

➢ Costly if an extra clock wire is required

▪ Asynchronous Serial Transmission

➢ The sender does not have to send a clock signal

➢ Both sender and receiver agree on timing parameters in advance

➢ Special bits are added to synchronize transmission

Synchronous Serial Data Transmission
Parallel Data In
D3 D2 D1 D0

Serial Serial
D Q D Q D Q D Q Data In D Q D Q D Q D Q
Data Out

Clk Clk

D3 D2 D1 D0
Parallel Data Out

Transmitting Device Receiving Device

Clock
Serial Data
Data Sampling Time at Receiver

▪ Use shift registers and a clock signal to convert between serial and parallel formats
▪ Synchronous: an explicit clock signal is along with the data signal
Synchronous Full-Duplex Serial Data Bus

Select Select Select Select

Peripheral Peripheral Peripheral Peripheral
Clk DIn DOut DIn DOut DIn DOut DIn DOut
MCU

▪ Now can use two serial data lines - one for reading, one for writing.
▪ Allows simultaneous send and receive full-duplex communication
Synchronous Half-Duplex Serial Data Bus

Select Select Select Select

Peripheral Peripheral Peripheral Peripheral
Clk Data Clk Data Clk Data Clk Data
MCU

▪ Share the serial data line

▪ Doesn’t allow simultaneous send and receive - is half-duplex communication
Asynchronous Serial Communication
Data bits
Start bit Stop bit

Time Zero

Tbit*1.5

Tbit*2.5

Tbit*3.5

Tbit*4.5

Tbit*5.5

Tbit*6.5

Tbit*7.5

Tbit*8.5

Tbit*9.5
Data Sampling
Time at Receiver

▪ Eliminate the clock line!

▪ Transmitter and receiver must generate clock locally
▪ Transmitter must add start bit (always same value) to indicate start of each data frame
▪ Receiver detects leading edge of start bit, then uses it as a timing reference for sampling
data line to extract each data bit N at time Tbit*(N+1.5)
▪ Stop bit is also used to detect some timing errors
Serial Communication Specifics

▪ Data frame fields Start bit Data bits Stop bit

▪ Start bit (one bit)
▪ Data (LSB first or MSB, and
size – 7, 8, 9 bits) Message
▪ Optional parity bit is used to make total number of ones in data even or odd
▪ Stop bit (one or two bits)
▪ All devices must use the same communications parameters
▪ E.g. communication speed (300 baud, 600, 1200, 2400, 9600, 14400, 19200, etc.)
▪ Sophisticated network protocols have more information in each data frame
▪ Medium access control – when multiple nodes are on bus, they must arbitrate for permission to transmit
▪ Addressing information – for which node is this message intended?
▪ Larger data payload
▪ Stronger error detection or error correction information
▪ Request for immediate response (“in-frame”)
Error Detection

▪ Can send additional information to verify data was received correctly

▪ Need to specify which parity to expect: even, odd or none.
▪ Parity bit is set so that total number of “1” bits in data and parity is even (for even
parity) or odd (for odd parity)
▪ 01110111 has 6 “1” bits, so parity bit will be 1 for odd parity, 0 for even parity
▪ 01100111 has 5 “1” bits, so parity bit will be 0 for odd parity, 1 for even parity
▪ Single parity bit detects if 1, 3, 5, 7 or 9 bits are corrupted, but doesn’t detect an even
number of corrupted bits
▪ Stronger error detection codes (e.g. Cyclic Redundancy Check) exist and use multiple
bits (e.g. 8, 16), and can detect many more corruptions.
▪ Used for CAN, USB, Ethernet, Bluetooth, etc.
Software Structure

▪ Communication is asynchronous to program

▪ Don’t know what code the program will be executing …
◦ when the next item arrives
◦ when current outgoing item completes transmission
◦ when an error occurs
▪ Need to synchronize between program and serial communication interface somehow
▪ Options
▪ Polling
◦ Wait until data is available
◦ Simple but inefficient of processor time
▪ Interrupt
◦ CPU interrupts program when data is available
◦ Efficient, but more complex
Serial Communications and Interrupts
Main Program or
other threads
▪ Want to provide multiple threads of control in the
program
send_string get_string
▪ Main program (and subroutines it calls)
▪ Transmit ISR – executes when serial interface is ready to
send another character
▪ Receive ISR – executes when serial interface receives a
character
▪ Error ISR(s) – execute if an error occurs
tx_isr rx_isr

▪ Need a way of buffering information between threads

▪ Solution: circular queue with head and tail pointers Serial
Interface
▪ One for tx, one for rx
Enabling and Connecting Interrupts to ISRs
▪ ARM Cortex-M4 void USART2_IRQHandler(){
provides various IRQs
for all communication if (transmitter ready) {
interface’s events if (more data to send) {
▪ I2C1EVENT get next byte
▪ I2C1ERROR send it out transmitter
▪ I2C2EVENT }
▪ I2C2ERROR }
▪ SPI1 if (received data) {
▪ SPI2 get byte from receiver
▪ USART1 save it
▪ USART2 }
▪ USART3 if (error occurred) {
handle error
▪ Decide which } }
operation to take in
each IRQ
Decoding Messages

▪ Two types of messages

▪ Actual binary data sent
◦ First identify message type
◦ Second, based on this message type, copy binary data from message fields into variables
◦ May need to use pointers and casting to get code to translate formats correctly and safely
▪ ASCII text characters representing data sent
◦ First identify message type
◦ Second, based on this message type, translate (parse) the data from the ASCII message format into a binary
format
◦ Third, copy the binary data into variables
Example Binary Serial Data: TSIP

switch (id) {
case 0x84:
lat = *((double *)(&msg[0]));
lon = *((double *)(&msg[8]));
alt = *((double *)(&msg[16]));
clb = *((double *)(&msg[24]));
tof = *((float *)(&msg[32]));
break; Report Packet (0x84) Data Structure
case 0x4A: … Type sizeof(Type) Item Units
default: Double 8 Latitude Radians; + for
break; north, - for south
} Double 8 Longitude Radians; + for east,
- for west
Double 8 Altitude Meters
Double 8 Clock Bias Meters
Single 4 Time-of-fix Seconds
Example ASCII Serial Data: NMEA-0183

$IDMSG,D1,D2,D3,D4,…,Dn*CS\r\n
▪ $ denotes the start of a message
▪ ID is a two letter mnemonic to describe the source of data,
e.g. GP signifies GPS
▪ MSG is a three letter mnemonic to describe the message
content.
▪ Commas are used to delaminate the data fields.
▪ Dn represents each of the data fields.
▪ * is used to separate the data from the checksum.
▪ CS contains two ASCII characters representing the hex
value of the checksum.
▪ \r\n is the carriage return character followed by the new line
character to denote the end of a message.
State Machine for Parsing NMEA-0183
Any char. except *, \r or \n
Start $ Append char to buf.
Append char to buf. Talker + Inc. counter
*, \r or \n, Sentence
non-text, or Type
buf==$SDDBT, $VWVHW, or $YXXDR
counter>6 Enqueue all chars. from buf

/r or /n
Sentence
Body Any char. except *
Enqueue char
*
Enqueue char

Checksum
1
Any char.
Save as checksum1
Checksum
2
Any char.
Save as checksum2
Universal Asynchronous
Receiver/Transmitter (UART)
UART Overview
▪ Universal Asynchronous Receiver/Transmitter (UART)

▪ Asynchronous communication, no clock wire required, pre-agreed baud rate

▪ Separate transmit and receive wires

▪ UART communication

▪ Converts data from parallel to serial

▪ Sequential data is transferred through serial cable

▪ Receives the sequential data and reassembles it back to parallel

tx rx
device1 device2
rx tx
Transmitter Basics
Data
bits

Data Sampling

Time Zero
Time at Receiver

Tbit
Tbit

Tbit

Tbit
▪ If no data to send, keep sending 1 (stop bit) – idle line
▪ When there is a data word to send
▪ Send a 0 (start bit) to indicate the start of a word
▪ Send each data bit in the word (use a shift register for the transmit buffer)
▪ Send a 1 (stop bit) to indicate the end of the word
Receiver Basics
Data
bits

Data Sampling

Zero
Time

Tbit*10.5
Tbit*1.5

Tbit*2.5

Tbit*3.5

Tbit*4.5

Tbit*5.5

Tbit*6.5

Tbit*7.5

Tbit*8.5

Tbit*9.5
Time at
Receiver

▪ Wait for a falling edge (beginning of a Start bit)

▪ Then wait ½ bit time
▪ Do the following for as many data bits in the word
◦ Wait 1 bit time
◦ Read the data bit and shift it into a receive buffer (shift register)

▪ Wait 1 bit time

▪ Read the bit
◦ if 1 (Stop bit), then OK
◦ if 0, there’s a problem!
For this to work…

▪ Transmitter and receiver must agree on several things (protocol)

▪ Order of data bits
▪ Number of data bits
▪ What a start bit is (1 or 0)
▪ What a stop bit is (1 or 0)
▪ How long a bit lasts
◦ Transmitter and receiver clocks must be reasonably close, since the only timing reference is the start of the
start bit
Input Data Oversampling

▪ When receiving, UART oversamples incoming data line

▪ Extra samples allow voting, improving noise immunity
▪ Better synchronization to incoming data, improving noise immunity

▪ Configurable oversampling from 8x to 16x

USART
▪ Like other modules, USART in the STM32F4 families is capable to operate in
many modes.

ARM University Program

USART Block Diagram

STM32F4
How the STM32F4 works
▪ Transmitter and receiver must agree on several things (protocol)
▪ Order of data bits
▪ LSB will be transmitted first
▪ Number of data bits
▪ Can be configured as 8 or 9 bits
▪ What a start bit is (1 or 0)
▪ 0
▪ What a stop bit is (1 or 0)
▪ 1
▪ Configurable length (0.5, 1, 1.5 or 2)
▪ How long a bit lasts
▪ Software programmable phase and polarity

ARM University Program

Copyright © ARM Ltd 2013 25
UART transmission parameters
The following parameters must be set in the UART hardware:
• transmission speed, in bps = Bit Per Second or baud
• number of bits per character, usually 8
• presence/absence of partity bit, usually absent
• number of stop bits, usually 1
Corrado Santoro

A setting 19200,8,N,1 means:

• speed = 19200 bit-per-second;
• bits = 8;
• parity = None;
• stop bits = 1.
Simplified Schematics of UART