LED-based debugging patterns in Embedded C - Mini Project: Build & Apply

LED-based Debugging Patterns

📖 Scenario: You are working with a microcontroller that has a single LED connected to a digital output pin. You want to use the LED to show different debugging patterns to understand the program flow without a serial monitor.

🎯 Goal: Create a simple embedded C program that uses the LED to blink in different patterns based on a configuration variable. You will set up the LED pin, define a pattern selector, implement the blinking logic for each pattern, and finally output the blinking pattern.

📋 What You'll Learn

Define a variable for the LED pin number

Define a variable called pattern to select the blinking pattern

Use a switch statement on pattern to control LED blinking

Implement three patterns: steady ON, slow blink, and fast blink

Use a function delay_ms(int ms) to create delays

Print the current pattern number to the console (simulate output)

💡 Why This Matters

🌍 Real World

Using LEDs to debug embedded systems is common when serial output is unavailable or limited.

💼 Career

Embedded developers often use LED patterns to quickly identify program states or errors during hardware testing.

1

Setup LED pin variable

Create an integer variable called led_pin and set it to 13 to represent the LED pin number.

Embedded C

int led_pin = 0;  // Your code here

Hint

The LED is connected to pin 13. Use int led_pin = 13;.

2

Add pattern selector variable

Add an integer variable called pattern and set it to 2 to select the blinking pattern.

Embedded C

int led_pin = 13;
int pattern = 0;  // Your code here

Hint

Set pattern to 2 to test the slow blink pattern.

3

Implement LED blinking patterns

Write a switch statement on pattern with cases 1, 2, and 3. For case 1, turn the LED ON steadily. For case 2, blink the LED slowly (turn ON, delay 1000 ms, turn OFF, delay 1000 ms). For case 3, blink the LED fast (turn ON, delay 200 ms, turn OFF, delay 200 ms). Use functions digitalWrite(led_pin, HIGH), digitalWrite(led_pin, LOW), and delay_ms(int ms).

Embedded C

int led_pin = 13;
int pattern = 2;

// Your code here

Hint

Use switch (pattern) and implement each case with the correct delays and LED states.

4

Print the current pattern

Add a printf statement to print "Current pattern: " followed by the value of pattern.

Embedded C

int led_pin = 13;
int pattern = 2;

switch (pattern) {
    case 1:
        digitalWrite(led_pin, HIGH); // LED ON steadily
        break;
    case 2:
        digitalWrite(led_pin, HIGH);
        delay_ms(1000);
        digitalWrite(led_pin, LOW);
        delay_ms(1000);
        break;
    case 3:
        digitalWrite(led_pin, HIGH);
        delay_ms(200);
        digitalWrite(led_pin, LOW);
        delay_ms(200);
        break;
    default:
        digitalWrite(led_pin, LOW); // LED OFF
        break;
}

// Your code here

Hint

Use printf("Current pattern: %d\n", pattern); to show the pattern number.

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