UART protocol fundamentals in Embedded C - Step-by-Step Execution

Concept Flow - UART protocol fundamentals

Idle Line

↓

Start Bit Detected

↓

Read Data Bits (usually 8)

↓

Check Parity Bit (optional)

↓

Read Stop Bit(s)

↓

Frame Complete -> Data Ready

↓

Back to Idle Line

UART communication starts with an idle line, detects a start bit, reads data bits, optional parity, stop bits, then completes the frame and returns to idle.

Execution Sample

Embedded C

void uart_receive() {
  if (start_bit_detected()) {
    uint8_t data = read_8_bits();
    if (check_parity(data)) {
      process_data(data);
    }
  }
}

This code waits for a start bit, reads 8 data bits, checks parity, and processes the data if parity is correct.

Execution Table

Step	Signal Detected	Action	Data Value	Status
1	Idle line (high)	Wait for start bit	-	Waiting
2	Start bit (low)	Start reading data bits	-	Start bit detected
3	Data bit 0	Read bit	1	Reading data
4	Data bit 1	Read bit	0	Reading data
5	Data bit 2	Read bit	1	Reading data
6	Data bit 3	Read bit	1	Reading data
7	Data bit 4	Read bit	0	Reading data
8	Data bit 5	Read bit	0	Reading data
9	Data bit 6	Read bit	1	Reading data
10	Data bit 7	Read bit	0	Reading data
11	Parity bit	Check parity	-	Parity OK
12	Stop bit (high)	Frame complete	0b01011001	Data ready
13	Idle line	Wait for next start bit	-	Waiting

💡 Stop bit received and parity checked, frame complete, ready for next frame.

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7	After Step 8	After Step 9	After Step 10	Final
data_bits	-	1	10	101	1011	10110	101100	1011001	10110010	0b01011001

Key Moments - 3 Insights

Why does UART start with a low start bit instead of high?

The start bit is low to signal the beginning of data transmission clearly because the idle line is high; this contrast helps the receiver detect the start (see execution_table step 2).

What happens if parity check fails?

If parity fails, the data is considered corrupted and usually discarded or flagged; in the example, process_data() is only called if parity is OK (see execution_table step 11).

Why do we read data bits one by one instead of all at once?

UART sends bits serially over one wire, so the receiver reads each bit in sequence to reconstruct the byte (see variable_tracker showing bits accumulating step by step).

Visual Quiz - 3 Questions

Look at the execution_table at step 5, what is the data_bits value after reading data bit 2?

A 101

B 10

C 1

D 0

💡 Hint

Check the 'Data Value' and 'Action' columns at step 5 in execution_table.

At which step does the UART frame become ready for processing?

A Step 11

B Step 12

C Step 10

D Step 13

💡 Hint

Look for 'Frame complete' and 'Data ready' status in execution_table.

If the parity bit was incorrect, what would change in the execution flow?

A Data bits would be skipped

B Start bit would be ignored

C process_data() would not be called

D Stop bit would be read twice

💡 Hint

Refer to key_moments about parity check and execution_table step 11.

Concept Snapshot

UART sends data serially with:
- Idle line high
- Start bit low to begin
- 8 data bits sent one by one
- Optional parity bit for error check
- Stop bit(s) high to end frame
Receiver detects start, reads bits, checks parity, then processes data.

Full Transcript

UART protocol works by keeping the line idle high. When data is sent, a low start bit signals the beginning. Then 8 data bits are sent one after another. Optionally, a parity bit is sent to check errors. Finally, stop bit(s) high mark the end of the frame. The receiver watches the line, detects the start bit, reads each data bit in order, checks parity, and when the stop bit arrives, the data is ready to use. This step-by-step process ensures reliable serial communication.