Receiving a byte over UART in Embedded C - Time & Space Complexity

Time Complexity: Receiving a byte over UART

O(n)

Understanding Time Complexity

When receiving a byte over UART, it's important to understand how the time to get data changes as more data arrives.

We want to know how the program's waiting or processing time grows when receiving bytes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Wait until data is received
while (!(UART_STATUS_REG & DATA_READY_FLAG)) {
    // waiting
}
// Read the received byte
uint8_t received_byte = UART_DATA_REG;
    

This code waits for one byte to arrive on UART and then reads it.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The while loop checking the data ready flag repeatedly.
• How many times: It repeats until one byte arrives, which depends on the data arrival speed.

How Execution Grows With Input

Each byte requires waiting until it arrives, so time grows linearly with the number of bytes.

Input Size (n bytes)	Approx. Operations (wait loops)
10	About 10 times the wait for one byte
100	About 100 times the wait for one byte
1000	About 1000 times the wait for one byte

Pattern observation: The waiting time grows directly with the number of bytes received.

Final Time Complexity

Time Complexity: O(n)

This means the time to receive bytes grows in a straight line as more bytes come in.

Common Mistake

[X] Wrong: "Receiving one byte always takes the same fixed time regardless of data."

[OK] Correct: The code waits actively until data arrives, so if data is slow, waiting time grows and is not fixed.

Interview Connect

Understanding how waiting for hardware data scales helps you reason about program responsiveness and efficiency in embedded systems.

Self-Check

"What if we used an interrupt instead of polling the data ready flag? How would the time complexity change?"

Practice

1. What does receiving a byte over UART typically involve in embedded C programming?

easy

A. Reading one character sent from another device

B. Sending multiple bytes to another device

C. Configuring the UART baud rate only

D. Resetting the microcontroller

Solution

1. Step 1: Understand UART communication basics

   UART communication involves sending and receiving data one byte at a time between devices.

2. Step 2: Identify receiving action

   Receiving a byte means reading one character sent from another device, not sending or configuring settings.

3. Final Answer:

   Reading one character sent from another device -> Option A

4. Quick Check:

   Receiving byte = Reading one character [OK]

Hint: Receiving means reading data sent from another device [OK]

Common Mistakes:

• Confusing receiving with sending data
• Thinking configuration is receiving
• Assuming multiple bytes are received at once

2. Which of the following is the correct way to check if a byte is ready to be read from UART in embedded C?

easy

A. UART_DATA = UART_STATUS & RX_READY;

B. if (UART_DATA == RX_READY) { byte = UART_STATUS; }

C. if (UART_STATUS & RX_READY) { byte = UART_DATA; }

D. while (UART_DATA != RX_READY) { }

Solution

1. Step 1: Understand UART status checking

   To check if data is ready, we test a status register bit (e.g., RX_READY) using bitwise AND.

2. Step 2: Correct syntax for reading byte

   If data is ready, read the byte from the data register. if (UART_STATUS & RX_READY) { byte = UART_DATA; } correctly does this.

3. Final Answer:

   if (UART_STATUS & RX_READY) { byte = UART_DATA; } -> Option C

4. Quick Check:

   Status & RX_READY then read data [OK]

Hint: Check status with bitwise AND before reading data [OK]

Common Mistakes:

• Comparing data register to status bits
• Assigning instead of checking bits
• Using wrong registers for status or data

3. What will be the output of this code snippet if UART_DATA contains 0x41 ('A') and UART_STATUS has RX_READY set?

char received_byte;
if (UART_STATUS & RX_READY) {
    received_byte = UART_DATA;
}
printf("%c", received_byte);

medium

A. Error

B. A

C. 0

D. No output

Solution

1. Step 1: Check condition for data ready

   UART_STATUS & RX_READY is true, so the if block executes.

2. Step 2: Assign and print received byte

   received_byte is assigned UART_DATA value 0x41, which is ASCII 'A'. printf prints 'A'.

3. Final Answer:

   A -> Option B

4. Quick Check:

   UART_DATA 0x41 = 'A' printed [OK]

Hint: If RX_READY set, read UART_DATA and print it [OK]

Common Mistakes:

• Assuming no output if condition true
• Confusing hex 0x41 with zero
• Expecting error without syntax issues

4. Identify the error in this UART receive code snippet:

char byte;
if (UART_STATUS & RX_READY);
{
    byte = UART_DATA;
}

medium

A. Semicolon after if condition causes unconditional block execution

B. UART_DATA should be UART_STATUS

C. Missing initialization of byte variable

D. RX_READY should be checked with equality operator

Solution

1. Step 1: Analyze if statement syntax

   The semicolon after if condition ends the if statement prematurely.

2. Step 2: Effect of semicolon on code block

   The block following runs always, ignoring the if condition, causing logic error.

3. Final Answer:

   Semicolon after if condition causes unconditional block execution -> Option A

4. Quick Check:

   Semicolon after if = unconditional block [OK]

Hint: No semicolon immediately after if(condition) [OK]

Common Mistakes:

• Ignoring semicolon after if
• Confusing data and status registers
• Thinking variable must be initialized before if

5. You want to receive a byte over UART without blocking your program if no data is available. Which approach is best in embedded C?

hard

A. Reset UART peripheral before every read

B. Use a blocking read function that waits until data arrives

C. Read UART_DATA directly without checking status

D. Check UART status register for RX_READY before reading data

Solution

1. Step 1: Understand non-blocking UART receive

   Non-blocking means program continues if no data; so check status first.

2. Step 2: Choose correct method

   Checking RX_READY bit before reading ensures data is available and avoids waiting.

3. Final Answer:

   Check UART status register for RX_READY before reading data -> Option D

4. Quick Check:

   Check status before read to avoid blocking [OK]

Hint: Always check RX_READY before reading UART_DATA [OK]

Common Mistakes:

• Using blocking read causing program to wait
• Reading data without checking status
• Resetting UART unnecessarily