Common embedded bugs and fixes in Embedded C

Introduction

Embedded systems often have small memory and strict timing. Bugs can cause crashes or wrong behavior. Knowing common bugs helps fix problems faster.

When your embedded device resets unexpectedly.

When sensor readings are incorrect or noisy.

When communication with other devices fails.

When the system uses too much memory or runs slowly.

When debugging hardware-related issues.

Syntax

Embedded C

/* Example: Fixing a common bug - uninitialized variable */
int sensor_value;

void read_sensor() {
    sensor_value = 0; // Initialize before use
    // code to read sensor
}

Always initialize variables before using them to avoid unpredictable values.

Check hardware connections and timing carefully in embedded code.

Examples

This can cause wrong count values because 'count' starts with garbage data.

Embedded C

/* Bug: Using uninitialized variable */
int count;

void loop() {
    count = count + 1; // count was never set first
}

Initializing 'count' to 0 ensures it counts correctly.

Embedded C

/* Fix: Initialize variable */
int count = 0;

void loop() {
    count = count + 1; // now count starts at 0
}

If the interrupt flag is not cleared, the interrupt may keep firing repeatedly.

Embedded C

/* Bug: Forgetting to clear interrupt flag */
void ISR() {
    // handle interrupt
    // missing code to clear flag
}

Clearing the flag stops repeated interrupts.

Embedded C

/* Fix: Clear interrupt flag */
void ISR() {
    // handle interrupt
    CLEAR_INTERRUPT_FLAG();
}

Sample Program

This program shows how to initialize variables and clear interrupt flags to avoid bugs.

Embedded C

/* Example: Fixing a common embedded bug - uninitialized variable and interrupt flag */
#include <stdio.h>

volatile int count = 0;
volatile int interrupt_flag = 0;

void ISR() {
    interrupt_flag = 0; // Clear interrupt flag
    count++;
}

int main() {
    // Simulate interrupt
    interrupt_flag = 1;
    if (interrupt_flag) {
        ISR();
    }
    printf("Count after interrupt: %d\n", count);
    return 0;
}

Important Notes

Always initialize variables before use to avoid unpredictable behavior.

Clear hardware interrupt flags inside interrupt service routines.

Check for buffer overflows when reading data from sensors or communication.

Summary

Uninitialized variables cause unpredictable values; always set them before use.

Interrupt flags must be cleared to prevent repeated interrupts.

Careful memory and timing management is key in embedded programming.

Practice

1. What is a common cause of unpredictable behavior in embedded C programs related to variables?

easy

A. Using uninitialized variables before setting a value

B. Using too many comments in the code

C. Writing functions with too many parameters

D. Using global variables only

Solution

1. Step 1: Understand variable initialization

   Uninitialized variables contain garbage values, causing unpredictable behavior.

2. Step 2: Recognize the impact in embedded systems

   Embedded systems rely on precise values; uninitialized variables can cause errors or crashes.

3. Final Answer:

   Using uninitialized variables before setting a value -> Option A

4. Quick Check:

   Uninitialized variables = unpredictable values [OK]

Hint: Always initialize variables before use to avoid surprises [OK]

Common Mistakes:

• Assuming variables start at zero automatically
• Ignoring compiler warnings about uninitialized variables
• Thinking only pointers need initialization

2. Which of the following is the correct way to clear an interrupt flag in embedded C?

easy

A. interrupt_flag++;

B. interrupt_flag = 1;

C. interrupt_flag = 0;

D. interrupt_flag = -1;

Solution

1. Step 1: Identify interrupt flag clearing method

   Interrupt flags are cleared by setting them to 0 to indicate the interrupt is handled.

2. Step 2: Understand why other options fail

   Setting to 1 or incrementing does not clear the flag; negative values are invalid.

3. Final Answer:

   interrupt_flag = 0; -> Option C

4. Quick Check:

   Clear interrupt flag = 0 [OK]

Hint: Clear interrupt flags by setting them to zero [OK]

Common Mistakes:

• Setting flag to 1 instead of 0
• Incrementing flag instead of clearing
• Ignoring the need to clear flags causing repeated interrupts

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

volatile int flag = 0;
void ISR() {
  flag = 1;
}
int main() {
  while(flag == 0) {
    // wait
  }
  return 0;
}

medium

A. Program waits until ISR sets flag to 1, then exits

B. Program exits immediately

C. Compilation error due to volatile keyword

D. Program runs indefinitely without stopping

Solution

1. Step 1: Understand volatile keyword usage

   Volatile tells compiler the variable can change anytime, so it won't optimize the loop away.

2. Step 2: Analyze program flow

   Main waits in loop until ISR sets flag to 1, then loop ends and program exits.

3. Final Answer:

   Program waits until ISR sets flag to 1, then exits -> Option A

4. Quick Check:

   Volatile flag updated by ISR = loop ends [OK]

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

Common Mistakes:

• Ignoring volatile causing infinite loop
• Assuming ISR runs automatically without setup
• Thinking volatile causes compile errors

4. Identify the bug in this embedded C code and the best fix:

int counter;
void setup() {
  // No initialization of counter
}
void loop() {
  counter++;
  if(counter > 10) {
    counter = 0;
  }
}

medium

A. Change counter to volatile

B. Initialize counter to 0 in setup()

C. Remove the if condition

D. Declare counter as static

Solution

1. Step 1: Identify uninitialized variable usage

   Counter is used without initialization, causing unpredictable start value.

2. Step 2: Fix by initializing counter

   Set counter = 0 in setup() to ensure predictable counting behavior.

3. Final Answer:

   Initialize counter to 0 in setup() -> Option B

4. Quick Check:

   Initialize variables before use = correct count [OK]

Hint: Always initialize counters before incrementing [OK]

Common Mistakes:

• Assuming global variables start at zero
• Using volatile without need
• Ignoring initialization causing wrong counts

5. You have a sensor reading stored in a variable that updates via interrupt. Which combination of fixes ensures safe and correct reading in main code?

volatile int sensor_value;
int safe_value;

void ISR() {
  sensor_value = read_sensor();
}

int main() {
  // What should be done here?
}

hard

A. Make sensor_value non-volatile and copy it

B. Directly use sensor_value without copying

C. Use a delay loop before reading sensor_value

D. Disable interrupts, copy sensor_value to safe_value, enable interrupts

Solution

1. Step 1: Understand volatile and interrupt safety

   Volatile ensures compiler reads fresh value, but reading multi-byte data can be interrupted causing corruption.

2. Step 2: Use interrupt disable-copy-enable pattern

   Disable interrupts, copy sensor_value to safe_value, then enable interrupts to get consistent snapshot.

3. Final Answer:

   Disable interrupts, copy sensor_value to safe_value, enable interrupts -> Option D

4. Quick Check:

   Disable interrupts to safely copy volatile data [OK]

Hint: Disable interrupts when copying multi-byte volatile data [OK]

Common Mistakes:

• Reading volatile multi-byte data without protection
• Making volatile variable non-volatile
• Using delay instead of disabling interrupts