Button debouncing in software in Embedded C

Introduction

Buttons can send many quick signals when pressed or released. Debouncing helps to clean these signals so the program reads just one press or release.

When reading a physical button press on a microcontroller.

To avoid multiple actions from a single button press.

When you want stable and reliable button input in your device.

To prevent errors caused by noisy button signals.

When building user interfaces with buttons on embedded systems.

Syntax

Embedded C

void debounce_button() {
    static int button_state = 0;
    static int last_button_state = 0;
    static unsigned long last_debounce_time = 0;
    unsigned long debounce_delay = 50; // milliseconds

    int reading = read_button_pin();

    if (reading != last_button_state) {
        last_debounce_time = current_millis();
    }

    if ((current_millis() - last_debounce_time) > debounce_delay) {
        if (reading != button_state) {
            button_state = reading;
            if (button_state == PRESSED) {
                // Button pressed action
            }
        }
    }

    last_button_state = reading;
}

This example uses a timer to check if the button state is stable for a set time.

Use static variables to remember states between function calls.

Examples

This function returns a stable button state after debouncing.

Embedded C

int debounce(int raw_button_state) {
    static int stable_state = 0;
    static int last_state = 0;
    static unsigned long last_time = 0;
    unsigned long delay = 50;

    if (raw_button_state != last_state) {
        last_time = current_millis();
    }

    if ((current_millis() - last_time) > delay) {
        if (stable_state != raw_button_state) {
            stable_state = raw_button_state;
        }
    }

    last_state = raw_button_state;
    return stable_state;
}

Use the debounce function to check button press safely.

Embedded C

if (debounce(read_button_pin()) == PRESSED) {
    // Handle button press
}

Sample Program

This program simulates noisy button presses and uses software debouncing to detect a clean press.

Embedded C

#include <stdio.h>
#include <time.h>

#define PRESSED 1
#define RELEASED 0

// Simulated button readings with noise
int button_readings[] = {0, 1, 0, 1, 1, 1, 1, 1, 0, 0};
int index = 0;

unsigned long current_millis() {
    return (unsigned long)(clock() * 1000 / CLOCKS_PER_SEC);
}

int read_button_pin() {
    if (index < sizeof(button_readings)/sizeof(button_readings[0])) {
        return button_readings[index++];
    }
    return RELEASED;
}

int debounce() {
    static int button_state = RELEASED;
    static int last_button_state = RELEASED;
    static unsigned long last_debounce_time = 0;
    unsigned long debounce_delay = 50; // ms

    int reading = read_button_pin();

    if (reading != last_button_state) {
        last_debounce_time = current_millis();
    }

    if ((current_millis() - last_debounce_time) > debounce_delay) {
        if (reading != button_state) {
            button_state = reading;
            if (button_state == PRESSED) {
                return PRESSED;
            }
        }
    }

    last_button_state = reading;
    return RELEASED;
}

int main() {
    printf("Starting button debounce test...\n");
    while (index < sizeof(button_readings)/sizeof(button_readings[0])) {
        if (debounce() == PRESSED) {
            printf("Button pressed detected!\n");
        }
    }
    printf("Test finished.\n");
    return 0;
}

Important Notes

Debounce delay time (like 50 ms) can be adjusted depending on the button and hardware.

Using static variables inside the debounce function helps keep track of previous states.

Software debouncing is simple but may use CPU time; hardware debouncing is another option.

Summary

Button presses can be noisy and cause multiple signals.

Software debouncing waits for a stable signal before confirming a press.

This helps programs respond correctly to user button presses.

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