Printf redirect to UART in Embedded C - Time & Space Complexity

Time Complexity: Printf redirect to UART

O(n)

Understanding Time Complexity

When we redirect printf to UART, we want to know how the time taken changes as we print more characters.

We ask: How does printing more data affect the time the program spends sending it?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

int _write(int file, char *ptr, int len) {
    for (int i = 0; i < len; i++) {
        while (!(UART_STATUS_REG & UART_TX_READY)) {
            ; // wait until UART is ready
        }
        UART_DATA_REG = ptr[i];
    }
    return len;
}
    

This code sends each character one by one over UART, waiting for the hardware to be ready before sending the next.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop over each character in the string to send.
• How many times: The loop runs once for every character in the input length.

How Execution Grows With Input

As the number of characters to print grows, the time spent sending grows in the same way.

Input Size (n)	Approx. Operations
10	About 10 waits and sends
100	About 100 waits and sends
1000	About 1000 waits and sends

Pattern observation: The time grows directly with the number of characters; doubling characters doubles the time.

Final Time Complexity

Time Complexity: O(n)

This means the time to send data grows linearly with the number of characters printed.

Common Mistake

[X] Wrong: "Sending more characters takes the same time as sending one."

[OK] Correct: Each character must be sent separately, and the code waits for UART readiness each time, so more characters mean more waiting and sending steps.

Interview Connect

Understanding how hardware communication time grows with data size helps you write efficient embedded code and explain your reasoning clearly in interviews.

Self-Check

What if we changed the code to send characters in larger blocks without waiting for each one? How would the time complexity change?

Practice

1. What is the main purpose of overriding the fputc function in embedded C when redirecting printf output to UART?

easy

A. To clear the UART receive buffer

B. To change the baud rate of the UART communication

C. To initialize the UART peripheral before use

D. To send each character from printf to the UART hardware for transmission

Solution

1. Step 1: Understand printf output mechanism

   The printf function sends characters one by one to fputc for output.

2. Step 2: Role of overriding fputc

   By overriding fputc, we redirect each character to UART transmit function, sending it out via UART.

3. Final Answer:

   To send each character from printf to the UART hardware for transmission -> Option D

4. Quick Check:

   Overriding fputc redirects output to UART [OK]

Hint: Remember: printf calls fputc for output [OK]

Common Mistakes:

• Confusing fputc with UART initialization
• Trying to change UART settings inside fputc
• Ignoring that printf uses fputc internally

2. Which of the following is the correct prototype for overriding fputc to redirect printf output to UART in embedded C?

easy

A. char fputc(int ch, FILE *f);

B. void fputc(char ch);

C. int fputc(FILE *f, char ch);

D. int fputc(char ch, FILE *f);

Solution

1. Step 1: Recall standard fputc signature

   The standard fputc function prototype is int fputc(int ch, FILE *stream);.

2. Step 2: Match options with correct signature

   char fputc(int ch, FILE *f); matches the correct order and types: returns char (though standard is int), takes int and FILE pointer.

3. Final Answer:

   char fputc(int ch, FILE *f); -> Option A

4. Quick Check:

   Correct fputc prototype returns int and takes int, FILE* [OK]

Hint: Prototype must match standard fputc signature [OK]

Common Mistakes:

• Swapping parameter order
• Using void return type
• Using wrong parameter types

3. Given the following code snippet, what will be the output on the UART terminal?

int fputc(int ch, FILE *f) {
    UART_SendChar((char)ch);
    return ch;
}

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

medium

A. Only 'H' is sent to UART

B. No output because UART_SendChar is not defined

C. Hi followed by a newline on UART terminal

D. Compilation error due to missing UART initialization

Solution

1. Step 1: Understand fputc role in printf

   Each character of "Hi\n" is sent to fputc, which calls UART_SendChar to send it.

2. Step 2: Output on UART terminal

   Characters 'H', 'i', and newline '\n' are sent sequentially, so "Hi" and a newline appear on UART terminal.

3. Final Answer:

   Hi followed by a newline on UART terminal -> Option C

4. Quick Check:

   printf output redirected via fputc to UART [OK]

Hint: Each printf char calls fputc, which sends via UART [OK]

Common Mistakes:

• Assuming no output without UART initialization code shown
• Thinking only first char is sent
• Confusing compile errors with runtime behavior

4. Identify the error in this fputc override code that tries to redirect printf to UART:

int fputc(int ch, FILE *f) {
    UART_SendChar(ch);
    return 0;
}

medium

A. Returning 0 instead of the character causes incorrect printf behavior

B. Passing ch directly to UART_SendChar causes type mismatch

C. Missing UART initialization before sending characters

D. Function should return void, not int

Solution

1. Step 1: Check return value of fputc

   The fputc function must return the character written on success, or EOF on failure.

2. Step 2: Analyze the code's return statement

   Returning 0 (null char) instead of the character can cause printf to misbehave or stop output prematurely.

3. Final Answer:

   Returning 0 instead of the character causes incorrect printf behavior -> Option A

4. Quick Check:

   Return written char from fputc to keep printf working [OK]

Hint: Always return the character from fputc [OK]

Common Mistakes:

• Returning 0 instead of the character
• Ignoring return value importance
• Assuming void return type is allowed

5. You want to redirect printf output to UART and also support multiple UART ports. Which approach correctly extends fputc to select UART port dynamically?

hard

A. Create separate fputc functions for each UART port and call them manually

B. Use a global variable to store current UART port and send chars accordingly inside fputc

C. Modify printf to accept UART port as parameter

D. Use interrupts to switch UART ports automatically during fputc

Solution

1. Step 1: Understand fputc limitation

   Only one fputc function can be linked, so multiple versions are not possible.

2. Step 2: Use global variable for UART selection

   By storing the current UART port in a global variable, fputc can send characters to the selected UART dynamically.

3. Step 3: Evaluate other options

   Modifying printf is complex; interrupts do not switch ports automatically; multiple fputc functions cause conflicts.

4. Final Answer:

   Use a global variable to store current UART port and send chars accordingly inside fputc -> Option B

5. Quick Check:

   Global UART selector enables dynamic port choice in fputc [OK]

Hint: Use global UART variable to select port inside single fputc [OK]

Common Mistakes:

• Trying multiple fputc functions
• Changing printf signature
• Relying on interrupts to switch UART ports