Common embedded bugs and fixes in Embedded C - Mini Project: Build & Apply

Common embedded bugs and fixes

📖 Scenario: You are working on a small embedded system that controls a simple LED and a button. The system should turn the LED on when the button is pressed and turn it off when released. However, some common bugs can happen in embedded C code, such as incorrect variable initialization, missing volatile keyword, or wrong logic in the loop.

🎯 Goal: You will write a simple embedded C program that reads a button input and controls an LED output correctly. You will fix common bugs step-by-step to make the program work as expected.

📋 What You'll Learn

Create variables to represent the button input and LED output states

Add a configuration variable to simulate the button pressed state

Write a loop that sets the LED state based on the button state

Print the LED state to verify the output

💡 Why This Matters

🌍 Real World

Embedded systems often control hardware like buttons and LEDs. Writing correct code to read inputs and control outputs is essential.

💼 Career

Understanding common bugs and fixes in embedded C helps in developing reliable firmware for devices like microcontrollers and IoT gadgets.

1

DATA SETUP: Create variables for button and LED states

Create two integer variables called button_state and led_state. Initialize button_state to 0 and led_state to 0.

Embedded C

# Create variables button_state and led_state initialized to 0
// Your code here

Hint

Use int type and set both variables to 0.

2

CONFIGURATION: Add a variable to simulate button press

Add an integer variable called button_pressed and set it to 1 to simulate the button being pressed.

Embedded C

int button_state = 0;
int led_state = 0;
// Add variable button_pressed set to 1
// Your code here

Hint

This variable will simulate the button being pressed (1 means pressed).

3

CORE LOGIC: Update button_state and led_state based on button_pressed

Write code to set button_state equal to button_pressed. Then set led_state equal to button_state.

Embedded C

int button_state = 0;
int led_state = 0;
int button_pressed = 1;
// Update button_state and led_state based on button_pressed
// Your code here

Hint

Assign button_pressed to button_state, then assign button_state to led_state.

4

OUTPUT: Print the LED state

Write a printf statement to print the text "LED state: " followed by the value of led_state.

Embedded C

int button_state = 0;
int led_state = 0;
int button_pressed = 1;

button_state = button_pressed;
led_state = button_state;
// Print the LED state
// Your code here

Hint

Use printf("LED state: %d\n", led_state); to print the LED state.

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