LED-based debugging patterns in Embedded C - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output pattern of the LED after running this code?

Consider an embedded system where an LED is toggled every 500ms inside a loop. What pattern will the LED show?

Embedded C

void main() {
    while(1) {
        toggleLED(); // toggles LED state
        delay(500); // delay 500 milliseconds
    }
}

A LED blinks ON and OFF every 500ms continuously

B LED stays ON permanently

C LED stays OFF permanently

D LED blinks ON and OFF every 1000ms continuously

💡 Hint

Think about what toggle means and the delay duration.

The toggleLED() function changes the LED state from ON to OFF or OFF to ON each time it is called. Since it is called every 500ms, the LED changes state every 500ms, resulting in a blink every 500ms.

🧠 Conceptual

intermediate

Why use LED blinking patterns for debugging in embedded systems?

Which of the following is the main reason developers use LED blinking patterns for debugging embedded systems?

A To save power by turning LEDs on and off

B To test the LED hardware for manufacturing defects

C To improve the speed of the embedded processor

D To visually indicate system states or errors without a display or debugger

💡 Hint

Think about what is available when debugging embedded devices without screens.

LED blinking patterns provide a simple way to show system status or error codes visually when no screen or debugger is available.

❓ Predict Output

advanced

What is the LED output after running this code snippet?

This code uses a pattern to blink an LED twice quickly, then pause. What is the LED behavior?

Embedded C

void main() {
    while(1) {
        turnLEDOn();
        delay(200);
        turnLEDOff();
        delay(200);
        turnLEDOn();
        delay(200);
        turnLEDOff();
        delay(1000);
    }
}

A LED stays ON continuously

B LED blinks twice quickly, then stays off for 1 second, repeating

C LED blinks continuously with 200ms ON and 200ms OFF

D LED blinks once every 1 second

💡 Hint

Count the ON and OFF durations and the pause.

The LED turns ON for 200ms, OFF for 200ms, ON for 200ms, then OFF for 1000ms, creating two quick blinks followed by a longer pause.

🔧 Debug

advanced

What error does this LED blinking code cause?

This code is intended to blink an LED every second, but it does not work as expected. What error does it cause?

Embedded C

void main() {
    while(1) {
        turnLEDOn();
        delay(1000);
        turnLEDOff();
        delay(1000);
    }
}

A SyntaxError due to missing semicolon after delay(1000)

B Runtime error because turnLEDOff() is undefined

C LED stays ON permanently

D No error, code runs correctly

💡 Hint

Check punctuation carefully in C code.

The missing semicolon after delay(1000) causes a syntax error, preventing compilation.

🚀 Application

expert

How many unique LED blink states are shown by this code?

This code uses a 3-LED array to indicate system status by turning LEDs ON or OFF in a pattern. How many unique LED ON/OFF states does it produce in one full cycle?

Embedded C

void main() {
    int states[4][3] = {
        {1,0,0},
        {0,1,0},
        {0,0,1},
        {1,1,1}
    };
    int i = 0;
    while(1) {
        setLEDs(states[i][0], states[i][1], states[i][2]);
        delay(500);
        i = (i + 1) % 4;
    }
}

A 7 unique LED states

B 3 unique LED states

C 4 unique LED states

D 8 unique LED states

💡 Hint

Count the number of different LED ON/OFF combinations used.

The code cycles through 4 different LED states defined in the states array, so there are 4 unique states.

Practice

1. What is the main purpose of using LED-based debugging in embedded C programs?

easy

A. To improve the speed of the program execution

B. To visually indicate program status when no screen is available

C. To store data temporarily during program run

D. To replace the need for writing code comments

Solution

1. Step 1: Understand the role of LEDs in debugging

   LEDs are used to show simple signals like on/off or blinking to represent program states.

2. Step 2: Identify the scenario where LEDs are useful

   When no screen or serial output is available, LEDs provide a way to see program status visually.

3. Final Answer:

   To visually indicate program status when no screen is available -> Option B

4. Quick Check:

   LED debugging = visual status without screen [OK]

Hint: LEDs show program status visually without screens [OK]

Common Mistakes:

• Thinking LEDs speed up program execution
• Confusing LEDs with data storage
• Assuming LEDs replace code comments

2. Which of the following code snippets correctly turns on an LED connected to pin 5 in embedded C?

easy

A. PORT ^= (1 << 5); // Toggle bit 5

B. PORT &= ~(1 << 5); // Clear bit 5 to 0

C. PORT = 5; // Assign value 5 to PORT

D. PORT |= (1 << 5); // Set bit 5 to 1

Solution

1. Step 1: Understand bit manipulation for setting a pin

   To turn on an LED, set the specific bit to 1 using bitwise OR with (1 << pin_number).

2. Step 2: Analyze each option

   PORT |= (1 << 5); // Set bit 5 to 1 sets bit 5 to 1 correctly. PORT &= ~(1 << 5); // Clear bit 5 to 0 clears bit 5. PORT ^= (1 << 5); // Toggle bit 5 toggles bit 5. PORT = 5; // Assign value 5 to PORT assigns 5 to PORT, affecting all bits incorrectly.

3. Final Answer:

   PORT |= (1 << 5); // Set bit 5 to 1 -> Option D

4. Quick Check:

   Set bit = OR with (1 << pin) [OK]

Hint: Use OR with (1 << pin) to turn LED on [OK]

Common Mistakes:

• Using &= to turn LED on (actually clears bit)
• Using ^= which toggles instead of sets
• Assigning a number directly to PORT without bitmask

3. Consider this code snippet for blinking an LED connected to pin 2:

for(int i = 0; i < 3; i++) {
    PORT ^= (1 << 2); // Toggle LED
    delay(500); // Wait 500ms
}

How many times will the LED be ON during this loop?

medium

A. 1 time

B. 6 times

C. 2 times

D. 0 times

Solution

1. Step 1: Understand the toggle operation in the loop

   Each loop iteration toggles the LED state once, switching ON if OFF, or OFF if ON.

2. Step 2: Simulate the 3 iterations assuming LED starts OFF

   Iteration 1: toggle to ON, delay (ON 500ms). Iteration 2: toggle to OFF, delay (OFF 500ms). Iteration 3: toggle to ON, delay (ON 500ms). Thus, LED is ON twice during the loop.

3. Final Answer:

   2 times -> Option C

4. Quick Check:

   3 toggles starting OFF = 2 ON periods [OK]

Hint: Toggle flips LED state each loop iteration [OK]

Common Mistakes:

• Counting toggles as ON times incorrectly
• Assuming LED stays ON after first toggle
• Ignoring initial LED state

4. This code is intended to blink an LED connected to pin 1 three times, but it does not work as expected:

for(int i = 0; i < 3; i++) {
    PORT |= (1 << 1); // Turn LED ON
    delay(500);
    PORT &= ~(1 << 1); // Turn LED OFF
}

What is the main problem?

medium

A. Missing delay after turning LED OFF causes no visible blink

B. Using |= instead of &= to turn LED ON is incorrect

C. Loop counter should start from 1, not 0

D. Pin number 1 is invalid for LED control

Solution

1. Step 1: Analyze the LED ON/OFF sequence

   The LED is turned ON, delay 500ms, then turned OFF immediately without delay.

2. Step 2: Understand effect of missing delay after OFF

   Without delay after OFF, LED turns OFF instantly and loop repeats, so LED appears always ON or flickers too fast to see OFF.

3. Final Answer:

   Missing delay after turning LED OFF causes no visible blink -> Option A

4. Quick Check:

   Delay needed after OFF for visible blink [OK]

Hint: Add delay after OFF to see LED blink clearly [OK]

Common Mistakes:

• Thinking |= is wrong for turning LED ON
• Changing loop start index unnecessarily
• Assuming pin 1 is invalid without checking hardware

5. You want to use LED blinking patterns to indicate different error codes in your embedded system. Which approach is best to represent error code 5 using an LED connected to pin 0?

hard

A. Blink the LED 5 times quickly, then pause longer before repeating

B. Turn LED ON for 5 seconds continuously, then OFF

C. Toggle LED every 5 seconds without pause

D. Keep LED OFF and use a buzzer for error code

Solution

1. Step 1: Understand LED blinking as error code signals

   Blinking a number of times equal to the error code is a common, clear way to indicate errors.

2. Step 2: Evaluate options for clarity and usability

   Blinking 5 times quickly then pausing repeats the pattern clearly. Continuous ON or slow toggling is less clear. Using buzzer is outside LED debugging scope.

3. Final Answer:

   Blink the LED 5 times quickly, then pause longer before repeating -> Option A

4. Quick Check:

   Blink count = error code number [OK]

Hint: Blink LED count times to show error code [OK]

Common Mistakes:

• Using long ON time instead of blinking count
• Toggling too slowly to recognize pattern
• Ignoring LED use and switching to buzzer