Low-power design patterns in Embedded C

Introduction

Low-power design patterns help save battery life in embedded devices by reducing energy use. They make devices run longer without charging.

When building battery-powered sensors that need to last months or years.

In wearable devices like fitness trackers to extend usage time.

For remote IoT devices where changing batteries is hard.

In portable gadgets like handheld meters to save power.

When designing smart home devices that run continuously.

Syntax

Embedded C

void enter_low_power_mode(void) {
    // Prepare device for low power
    disable_unused_peripherals();
    set_sleep_mode(SLEEP_MODE_PWR_DOWN);
    sleep_enable();
    sleep_cpu();
    sleep_disable();
    // Wake up and resume normal operation
}

This example shows a common pattern to enter a low-power sleep mode.

Functions like disable_unused_peripherals() help reduce power by turning off parts not needed.

Examples

Disabling peripherals that are not needed reduces power consumption.

Embedded C

void disable_unused_peripherals(void) {
    // Turn off ADC, timers, etc. to save power
    ADCSRA &= ~(1 << ADEN); // Disable ADC
    TIMSK0 = 0; // Disable Timer0 interrupts
}

Using a lighter sleep mode lets the CPU wake up faster but saves less power.

Embedded C

void enter_sleep_mode(void) {
    set_sleep_mode(SLEEP_MODE_IDLE); // Light sleep mode
    sleep_enable();
    sleep_cpu();
    sleep_disable();
}

Interrupts can wake the device from sleep to handle events.

Embedded C

void wake_up_isr(void) {
    // Interrupt service routine to wake up from sleep
    // Usually empty, just needed to exit sleep
}

Sample Program

This program puts the device into a deep sleep mode to save power. It wakes up only when an external interrupt occurs (like a button press). This is a common low-power design pattern in embedded systems.

Embedded C

#include <avr/sleep.h>
#include <avr/interrupt.h>

volatile int awake = 0;

ISR(INT0_vect) {
    awake = 1; // Set flag when interrupt occurs
}

void disable_unused_peripherals(void) {
    ADCSRA &= ~(1 << ADEN); // Disable ADC
    TIMSK0 = 0; // Disable Timer0 interrupts
}

void enter_low_power_mode(void) {
    disable_unused_peripherals();
    set_sleep_mode(SLEEP_MODE_PWR_DOWN);
    sleep_enable();
    sei(); // Enable interrupts
    sleep_cpu();
    sleep_disable();
}

int main(void) {
    // Configure INT0 pin as input with interrupt
    EIMSK |= (1 << INT0); // Enable INT0 interrupt
    EICRA |= (1 << ISC01); // Falling edge triggers INT0

    while (1) {
        if (!awake) {
            enter_low_power_mode();
        } else {
            // Device woke up, do work
            // ...
            awake = 0; // Reset flag
        }
    }
    return 0;
}

Important Notes

Always disable peripherals you don't need before sleeping to save maximum power.

Choose the sleep mode based on how much power you want to save and how fast you need to wake up.

Interrupts are essential to wake the device from low-power modes.

Summary

Low-power design patterns help embedded devices save battery by sleeping when idle.

Disabling unused parts and using sleep modes reduces energy use.

Interrupts wake the device to handle important events without wasting power.

Practice

1. Which of the following best describes the purpose of low-power design patterns in embedded C programming?

easy

A. To reduce battery consumption by putting the CPU and peripherals into sleep modes

B. To increase the clock speed of the CPU for faster processing

C. To add more features to the embedded device

D. To improve the graphical user interface responsiveness

Solution

1. Step 1: Understand low-power design patterns

   These patterns focus on saving battery by reducing power use in the CPU and peripherals.

2. Step 2: Compare options to the purpose

   Only To reduce battery consumption by putting the CPU and peripherals into sleep modes talks about reducing battery consumption by sleep modes, which matches the purpose.

3. Final Answer:

   To reduce battery consumption by putting the CPU and peripherals into sleep modes -> Option A

4. Quick Check:

   Low-power design = save battery by sleep modes [OK]

Hint: Low-power means saving battery by sleeping parts [OK]

Common Mistakes:

• Confusing low-power with performance improvement
• Thinking it adds features instead of saving power
• Assuming it improves UI responsiveness

2. Which of the following is the correct way to put the CPU into sleep mode using a standard instruction in embedded C?

easy

A. enter_sleep_mode();

B. sleep();

C. power_down();

D. __WFI();

Solution

1. Step 1: Identify the standard CPU sleep instruction

   The __WFI() instruction is a common CPU instruction to wait for interrupt and enter sleep mode safely.

2. Step 2: Check other options

   Other options like sleep(), power_down(), enter_sleep_mode() are not standard embedded C instructions.

3. Final Answer:

   __WFI(); -> Option D

4. Quick Check:

   Use __WFI() to sleep CPU [OK]

Hint: Use __WFI() to enter CPU sleep mode [OK]

Common Mistakes:

• Using non-standard function names
• Forgetting the double underscore in __WFI()
• Confusing sleep() with standard CPU instructions

3. Consider the following code snippet in embedded C:

void enter_low_power() {
    disable_peripherals();
    __WFI();
    enable_peripherals();
}

What is the expected behavior when this function runs?

medium

A. The CPU sleeps until an interrupt occurs, peripherals are disabled before sleep and enabled after wake-up

B. The CPU runs continuously without sleeping, peripherals remain disabled

C. The CPU sleeps but peripherals stay enabled, causing high power use

D. The function causes a syntax error and does not compile

Solution

1. Step 1: Analyze the function steps

   First, peripherals are disabled to save power, then __WFI() puts CPU to sleep waiting for interrupt, finally peripherals are re-enabled after waking.

2. Step 2: Understand expected behavior

   The CPU sleeps until an interrupt wakes it, peripherals are off during sleep to save power, then turned back on.

3. Final Answer:

   The CPU sleeps until an interrupt occurs, peripherals are disabled before sleep and enabled after wake-up -> Option A

4. Quick Check:

   Disable peripherals + __WFI() = sleep with low power [OK]

Hint: Disable peripherals before __WFI() to save power during sleep [OK]

Common Mistakes:

• Assuming peripherals stay enabled during sleep
• Thinking CPU does not sleep after __WFI()
• Confusing function behavior with syntax errors

4. The following code is intended to put the CPU into low-power mode, but it does not work as expected:

void sleep_mode() {
    __WFI;
}

What is the error and how to fix it?

medium

A. The function should disable peripherals before __WFI; add disable_peripherals();

B. __WFI is not a valid instruction; replace with sleep();

C. __WFI is missing parentheses; fix by writing __WFI();

D. The function needs a return statement; add return 0;

Solution

1. Step 1: Identify syntax error in __WFI usage

   The code uses __WFI without parentheses, which is incorrect syntax for a function-like instruction.

2. Step 2: Correct the syntax

   Add parentheses to call __WFI as a function: __WFI(); fixes the error.

3. Final Answer:

   __WFI is missing parentheses; fix by writing __WFI(); -> Option C

4. Quick Check:

   __WFI() needs parentheses to call [OK]

Hint: Always use parentheses with __WFI() instruction [OK]

Common Mistakes:

• Omitting parentheses on __WFI
• Replacing __WFI with non-standard functions
• Ignoring peripheral disable step (not syntax error here)

5. You want to design a low-power routine that puts the CPU to sleep only if no peripherals are active. Given the functions are_peripherals_active() returning 1 if active, 0 if not, and __WFI() to sleep, which code snippet correctly implements this logic?

hard

A. if (are_peripherals_active()) { __WFI(); }

B. if (!are_peripherals_active()) { __WFI(); }

C. while (are_peripherals_active()) { __WFI(); }

D. do { __WFI(); } while (are_peripherals_active());

Solution

1. Step 1: Understand the condition to sleep

   The CPU should sleep only if no peripherals are active, so condition is peripherals inactive (0).

2. Step 2: Match condition with code

   Using if (!are_peripherals_active()) means if peripherals are not active, then call __WFI() to sleep.

3. Final Answer:

   if (!are_peripherals_active()) { __WFI(); } -> Option B

4. Quick Check:

   Sleep only if peripherals inactive = if (!active) [OK]

Hint: Sleep only when peripherals inactive: use if (!are_peripherals_active()) [OK]

Common Mistakes:

• Sleeping when peripherals are active
• Using loops causing repeated sleep calls
• Confusing condition negation