Printf debugging over UART in Embedded C - Time & Space Complexity

Time Complexity: Printf debugging over UART

O(n)

Understanding Time Complexity

When using printf debugging over UART, it's important to know how the time to send messages grows as you print more data.

We want to understand how the program's running time changes when printing more debug messages.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

void debug_print(const char* messages[], int count) {
    for (int i = 0; i < count; i++) {
        printf("%s\n", messages[i]);
    }
}
    

This code sends multiple debug messages over UART by printing each string one by one.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that calls printf for each message.
• How many times: Exactly once per message, so 'count' times.

How Execution Grows With Input

As you increase the number of messages, the total time grows roughly in direct proportion.

Input Size (n)	Approx. Operations
10	10 printf calls
100	100 printf calls
1000	1000 printf calls

Pattern observation: Doubling the number of messages doubles the total time spent printing.

Final Time Complexity

Time Complexity: O(n)

This means the time to print grows linearly with the number of debug messages sent.

Common Mistake

[X] Wrong: "Printing multiple messages takes the same time as printing one message."

[OK] Correct: Each printf call sends data over UART, which takes time. More messages mean more calls and more time.

Interview Connect

Understanding how loops and I/O operations affect running time helps you explain performance in embedded systems clearly and confidently.

Self-Check

"What if we buffered all messages and sent them in one printf call? How would the time complexity change?"

Practice

1. What is the main purpose of using printf debugging over UART in embedded C?

easy

A. To store data permanently in memory

B. To increase the speed of the embedded device

C. To send debug messages from the embedded device to a computer or terminal

D. To control hardware pins directly

Solution

1. Step 1: Understand UART communication

   UART allows serial communication between the embedded device and external devices like a PC.

2. Step 2: Role of printf debugging

   Using printf over UART sends text messages to the PC for debugging and monitoring program behavior.

3. Final Answer:

   To send debug messages from the embedded device to a computer or terminal -> Option C

4. Quick Check:

   UART + printf = debug messages [OK]

Hint: Printf over UART sends messages to PC for debugging [OK]

Common Mistakes:

• Thinking printf speeds up the device
• Confusing UART with memory storage
• Assuming printf controls hardware pins

2. Which of the following is the correct way to redirect printf output to UART in embedded C?

easy

A. Call printf directly without UART initialization

B. Set a GPIO pin high to enable printf

C. Use scanf to read UART data

D. Implement a custom _write function that sends characters via UART

Solution

1. Step 1: Understand printf redirection

   Standard printf sends output to stdout, which must be redirected to UART by implementing a low-level write function.

2. Step 2: Custom _write function role

   Implementing _write sends each character to UART transmit, enabling printf output over UART.

3. Final Answer:

   Implement a custom _write function that sends characters via UART -> Option D

4. Quick Check:

   Redirect printf by custom _write [OK]

Hint: Redirect printf by writing _write function sending UART chars [OK]

Common Mistakes:

• Calling printf without UART setup
• Using scanf instead of printf for output
• Trying to enable printf by GPIO pin

3. Given the code below, what will be the output sent over UART?

void UART_SendChar(char c);

int _write(int file, char *ptr, int len) {
  for (int i = 0; i < len; i++) {
    UART_SendChar(ptr[i]);
  }
  return len;
}

int main() {
  printf("Temp: %d C\n", 25);
  return 0;
}

medium

A. Temp: 25 C\n

B. Temp: %d C\n

C. Temp: 25 C

D. No output because UART_SendChar is not defined

Solution

1. Step 1: Understand _write function

   The _write function sends each character of the printf string to UART_SendChar, which transmits it over UART.

2. Step 2: Analyze printf output

   printf formats the string "Temp: 25 C\n" and _write sends it character by character.

3. Final Answer:

   Temp: 25 C\n -> Option A

4. Quick Check:

   Formatted printf string sent via UART [OK]

Hint: Printf formats string, _write sends chars via UART [OK]

Common Mistakes:

• Thinking %d prints literally
• Ignoring newline character
• Assuming UART_SendChar undefined means no output

4. What is the main problem in this code snippet for printf debugging over UART?

void UART_SendChar(char c) {
  while (!(UART->SR & UART_SR_TXE));
  UART->DR = c;
}

int _write(int file, char *ptr, int len) {
  for (int i = 0; i < len; i++) {
    UART_SendChar(ptr[i]);
  }
  return len;
}

int main() {
  printf("Hello UART\n");
  return 0;
}

medium

A. UART peripheral is not initialized before use

B. UART_SendChar does not wait for TXE flag

C. _write function returns wrong length

D. printf is not called in main

Solution

1. Step 1: Check UART_SendChar function

   UART_SendChar waits for TXE flag and writes data, so it is correct.

2. Step 2: Check UART initialization

   The code does not show UART initialization, which is required before sending data.

3. Final Answer:

   UART peripheral is not initialized before use -> Option A

4. Quick Check:

   Missing UART init causes no transmission [OK]

Hint: Always initialize UART before sending data [OK]

Common Mistakes:

• Ignoring UART initialization step
• Thinking TXE flag wait is missing
• Believing _write return value is incorrect

5. You want to debug a sensor reading using printf over UART. The sensor value is an integer that can be zero or negative. Which printf format specifier and UART setup is best to correctly display the value including negatives?

hard

A. Use %f in printf without UART redirection

B. Use %d in printf and ensure UART is initialized and _write redirects output

C. Use %x in printf and send data directly to GPIO pins

D. Use %u in printf and skip UART initialization

Solution

1. Step 1: Choose correct format specifier

   %d prints signed integers including zero and negatives correctly, unlike %u (unsigned) or %x (hex).

2. Step 2: Ensure UART setup

   UART must be initialized and printf output redirected via _write to UART for messages to appear on terminal.

3. Final Answer:

   Use %d in printf and ensure UART is initialized and _write redirects output -> Option B

4. Quick Check:

   Signed int format + UART init + _write = correct debug [OK]

Hint: Use %d and proper UART init with _write for signed values [OK]

Common Mistakes:

• Using %u which can't show negatives
• Skipping UART initialization
• Sending data to GPIO instead of UART