Button debouncing in software in Embedded C - Mini Project: Build & Apply

Button Debouncing in Software

📖 Scenario: You are working on a small embedded system with a push button connected to a microcontroller. When the button is pressed, the microcontroller reads the input pin. However, mechanical buttons often cause multiple rapid on/off signals called "bouncing" when pressed or released. This can cause the system to register multiple presses instead of one.To fix this, you will write a simple software debounce routine that waits for the button signal to stabilize before confirming a press.

🎯 Goal: Build a simple button debouncing program in C that reads a button input, waits for the signal to stabilize for a short time, and then confirms a single button press.

📋 What You'll Learn

Create a variable to simulate the button input state

Create a debounce delay constant

Write a function to check the button state with debouncing

Print the confirmed button press state

💡 Why This Matters

🌍 Real World

Button debouncing is essential in embedded systems to ensure reliable user input from mechanical buttons, avoiding multiple unwanted triggers.

💼 Career

Understanding button debouncing is important for embedded software developers working on hardware interfaces, IoT devices, and consumer electronics.

1

Create a variable to simulate the button input

Create an integer variable called button_state and set it to 1 to simulate the button being pressed (1 means pressed, 0 means not pressed).

Embedded C

# Create an integer variable called button_state and set it to 1
# Your code here

Hint

Use int button_state = 1; to create the variable.

2

Create a debounce delay constant

Create a constant integer called DEBOUNCE_DELAY and set it to 50 to represent 50 milliseconds debounce delay.

Embedded C

int button_state = 1;
// Create a constant integer DEBOUNCE_DELAY set to 50
# Your code here

Hint

Use const int DEBOUNCE_DELAY = 50; to create the delay constant.

3

Write a function to check the button state with debouncing

Write a function called debounce_button that takes no parameters and returns an integer. Inside the function, create a local variable stable_state and set it to the current button_state. Then simulate waiting for DEBOUNCE_DELAY milliseconds (you can just comment this as // wait DEBOUNCE_DELAY ms). Finally, return the stable_state.

Embedded C

int button_state = 1;
const int DEBOUNCE_DELAY = 50;

// Write the debounce_button function below
# Your code here

Hint

Define the function with int debounce_button(). Use a local variable stable_state to hold button_state. Simulate delay with a comment.

4

Print the confirmed button press state

Call the debounce_button() function and store its return value in an integer variable called confirmed_state. Then print the text "Button state after debounce: " followed by the value of confirmed_state using printf.

Embedded C

int button_state = 1;
const int DEBOUNCE_DELAY = 50;

int debounce_button() {
    int stable_state = button_state;
    // wait DEBOUNCE_DELAY ms
    return stable_state;
}

// Call debounce_button and print the result
# Your code here

Hint

Use int confirmed_state = debounce_button(); and printf("Button state after debounce: %d\n", confirmed_state);.

Practice

1. What is the main purpose of button debouncing in software?

easy

A. To ignore rapid, unwanted signals caused by mechanical button noise

B. To speed up the button press detection process

C. To increase the voltage of the button signal

D. To disable the button after first press

Solution

1. Step 1: Understand button signal noise

   Mechanical buttons often create multiple quick on/off signals when pressed, called noise or bouncing.

2. Step 2: Purpose of debouncing

   Debouncing waits for the signal to stabilize before confirming a press, ignoring these unwanted rapid signals.

3. Final Answer:

   To ignore rapid, unwanted signals caused by mechanical button noise -> Option A

4. Quick Check:

   Debouncing = Ignore noise [OK]

Hint: Debouncing filters noisy signals to detect one press [OK]

Common Mistakes:

• Thinking debouncing speeds up detection
• Confusing debouncing with hardware voltage changes
• Assuming debouncing disables buttons

2. Which of the following code snippets correctly implements a simple software debounce delay in embedded C?

easy

A. if(button_pressed()) { delay_ms(0); if(button_pressed()) { /* valid press */ } }

B. if(button_pressed()) { delay_ms(50); if(button_pressed()) { /* valid press */ } }

C. if(button_pressed()) { delay_ms(-50); if(button_pressed()) { /* valid press */ } }

D. if(button_pressed()) { delay_ms(5000); if(button_pressed()) { /* valid press */ } }

Solution

1. Step 1: Understand debounce delay

   A typical debounce delay is around 20-50 milliseconds to wait for signal stabilization.

2. Step 2: Analyze code options

   if(button_pressed()) { delay_ms(50); if(button_pressed()) { /* valid press */ } } uses 50 ms delay, which is correct. if(button_pressed()) { delay_ms(0); if(button_pressed()) { /* valid press */ } } uses 0 ms (no delay), C uses negative delay (invalid), D uses 5000 ms (too long).

3. Final Answer:

   if(button_pressed()) { delay_ms(50); if(button_pressed()) { /* valid press */ } } -> Option B

4. Quick Check:

   Debounce delay ~50ms = if(button_pressed()) { delay_ms(50); if(button_pressed()) { /* valid press */ } } [OK]

Hint: Use ~50ms delay to confirm button press [OK]

Common Mistakes:

• Using zero or negative delay
• Using too long delay causing slow response
• Not checking button state after delay

3. Consider this code snippet for debouncing a button press:

int debounce_button() {
  if (read_button_pin() == 0) {
    delay_ms(40);
    if (read_button_pin() == 0) {
      return 1;
    }
  }
  return 0;
}

What will debounce_button() return if the button is pressed and held steadily?

medium

A. 0

B. Random value

C. 1

D. Function will not return

Solution

1. Step 1: Check initial button state

   The function checks if the button pin reads 0 (pressed).

2. Step 2: Wait and re-check

   After 40 ms delay, it checks again. If still 0, it returns 1 indicating a valid press.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   Stable press returns 1 [OK]

Hint: Stable press returns 1 after delay check [OK]

Common Mistakes:

• Assuming immediate return without delay
• Confusing 0 and 1 as pressed/released
• Thinking function loops infinitely

4. This code is intended to debounce a button press but sometimes registers multiple presses. What is the likely problem?

if (read_button_pin() == 0) {
  delay_ms(10);
  if (read_button_pin() == 0) {
    button_pressed_flag = 1;
  }
}

medium

A. Delay of 10 ms is too short to filter bouncing

B. Button pin reading logic is inverted

C. Missing a delay after setting the flag

D. Using delay_ms instead of delay_us

Solution

1. Step 1: Analyze debounce delay duration

   10 ms delay is often too short to filter mechanical bouncing which can last up to 50 ms.

2. Step 2: Effect of short delay

   Short delay allows noise to pass, causing multiple press detections.

3. Final Answer:

   Delay of 10 ms is too short to filter bouncing -> Option A

4. Quick Check:

   Too short delay causes multiple presses [OK]

Hint: Use at least 20-50ms delay to debounce [OK]

Common Mistakes:

• Assuming logic inversion causes multiple presses
• Thinking delay after flag needed
• Confusing delay units (ms vs us)

5. You want to implement a software debounce that counts how many times a button is pressed without counting bounces. Which approach below best achieves this?

hard

A. Increment count immediately on button press without delay

B. Increment count only when button is released

C. Use a 1ms delay and increment count on every read

D. Check button state, wait 50ms, check again; if still pressed, increment count and wait until release

Solution

1. Step 1: Understand debounce counting logic

   To count presses without bounces, confirm stable press with delay, then count once.

2. Step 2: Avoid multiple counts during one press

   Waiting until release before next count prevents multiple increments from one press.

3. Final Answer:

   Check button state, wait 50ms, check again; if still pressed, increment count and wait until release -> Option D

4. Quick Check:

   Stable press + wait release = correct count [OK]

Hint: Confirm press, count once, wait release before next count [OK]

Common Mistakes:

• Counting immediately without debounce
• Using too short delay causing multiple counts
• Counting on release only misses presses