Why timers are needed in Embedded C - Performance Analysis

Time Complexity: Why timers are needed

O(n)

Understanding Time Complexity

Timers help control when and how often certain actions happen in embedded systems.

We want to understand how the cost of using timers changes as we adjust their settings or use.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Simple timer delay loop
void delay_ms(int ms) {
  for (int i = 0; i < ms; i++) {
    for (int j = 0; j < 1000; j++) {
      // wait roughly 1 microsecond
    }
  }
}

int main() {
  delay_ms(500); // delay 500 milliseconds
  return 0;
}
    

This code creates a delay by running loops to wait a certain number of milliseconds.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Nested loops that run to create delay.
• How many times: Outer loop runs 'ms' times; inner loop runs 1000 times each outer loop.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (ms)	Approx. Operations
10	10,000
100	100,000
1000	1,000,000

Pattern observation: The number of operations grows directly with the delay time; doubling delay doubles work.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the delay grows linearly with the input delay value.

Common Mistake

[X] Wrong: "The delay time stays the same no matter the input value."

[OK] Correct: The loops run more times as the input increases, so the delay grows longer.

Interview Connect

Understanding how timers affect program timing helps you write reliable embedded code that works well in real devices.

Self-Check

"What if we replaced the nested loops with a hardware timer interrupt? How would the time complexity change?"

Practice

1. Why do embedded C programs often use timers?

easy

A. To change the program language automatically

B. To make the program run faster

C. To measure time intervals without stopping the program

D. To increase memory size

Solution

1. Step 1: Understand the role of timers in embedded systems

   Timers allow the program to keep track of time without pausing or stopping other tasks.

2. Step 2: Compare other options

   Options A, B, and C do not relate to timing or program control.

3. Final Answer:

   To measure time intervals without stopping the program -> Option C

4. Quick Check:

   Timers track time without stopping = D [OK]

Hint: Timers track time without pausing program flow [OK]

Common Mistakes:

• Thinking timers speed up the program
• Confusing timers with memory management
• Believing timers change programming language

2. Which of the following is the correct way to start a timer in embedded C?

easy

A. timer_start();

B. start_timer();

C. TimerStart();

D. timer.begin();

Solution

1. Step 1: Recognize common embedded C timer function naming

   Functions in embedded C often use lowercase with underscores, like timer_start().

2. Step 2: Check other options for syntax

   start_timer() and TimerStart() are possible but less common; timer.begin() looks like C++ or Arduino style.

3. Final Answer:

   timer_start(); -> Option A

4. Quick Check:

   Embedded C uses lowercase with underscores = A [OK]

Hint: Embedded C uses lowercase_underscore style functions [OK]

Common Mistakes:

• Using C++ style method calls
• Capitalizing function names incorrectly
• Mixing Arduino style with embedded C

3. What will be the output of this embedded C code snippet?

volatile int flag = 0;
void timer_interrupt() {
  flag = 1;
}
int main() {
  while(flag == 0) {
    // wait
  }
  printf("Timer done\n");
  return 0;
}

medium

A. Timer done

B. Runtime error

C. Compilation error

D. No output, program stuck in loop

Solution

1. Step 1: Analyze the flag variable and interrupt

   The flag is set to 1 only inside timer_interrupt(), which is not called in main.

2. Step 2: Understand program flow

   Main waits in while(flag == 0) forever because flag never changes.

3. Final Answer:

   No output, program stuck in loop -> Option D

4. Quick Check:

   Interrupt not triggered = infinite wait = B [OK]

Hint: Interrupt must be triggered to change flag [OK]

Common Mistakes:

• Assuming interrupt runs automatically
• Expecting output without interrupt call
• Ignoring volatile keyword purpose

4. Identify the error in this timer usage code snippet:

int timer_flag = 0;
void timer_ISR() {
  timer_flag = 1;
}
int main() {
  while(timer_flag == 0) {
    // wait
  }
  printf("Timer expired\n");
  return 0;
}

medium

A. printf() cannot be used in embedded C

B. timer_flag should be declared volatile

C. timer_ISR() should return int

D. while loop condition is incorrect

Solution

1. Step 1: Check variable shared with interrupt

   timer_flag is changed in ISR and read in main, so it must be volatile to prevent optimization.

2. Step 2: Review other options

   ISR return type can be void; printf() can be used if supported; while condition is logically correct.

3. Final Answer:

   timer_flag should be declared volatile -> Option B

4. Quick Check:

   Shared variable with ISR needs volatile = C [OK]

Hint: Use volatile for variables changed by interrupts [OK]

Common Mistakes:

• Ignoring volatile keyword
• Changing ISR return type unnecessarily
• Thinking printf is always disallowed

5. You want to blink an LED every 1 second without stopping other tasks. Which timer approach is best in embedded C?

hard

A. Use a timer interrupt to toggle LED flag every 1 second

B. Use a blocking delay loop for 1 second

C. Use a recursive function to blink LED

D. Use a global variable incremented in main loop

Solution

1. Step 1: Understand blinking without stopping other tasks

   Blocking delay (Use a blocking delay loop for 1 second) stops other tasks; recursive function (Use a recursive function to blink LED) is inefficient; global variable incremented in main (Use a global variable incremented in main loop) may not be precise.

2. Step 2: Use timer interrupt for precise, non-blocking control

   Timer interrupt toggles LED flag every 1 second without blocking main program.

3. Final Answer:

   Use a timer interrupt to toggle LED flag every 1 second -> Option A

4. Quick Check:

   Timer interrupt enables non-blocking blinking = A [OK]

Hint: Use timer interrupts for non-blocking periodic tasks [OK]

Common Mistakes:

• Using blocking delays that freeze program
• Trying recursion for timing
• Relying on main loop variable without timer