agentleFS
mohitmishra786mohitmishra786/low-level-dev-skills/skills/baremetal/low-power-embedded/SKILL.md

low-power-embedded

Skill290 starsChanged 7 months agoMITView on GitHub

Low-power embedded skill for sleep modes and energy optimization. Use when configuring MCU sleep/stop/standby, peripheral clock gating, wake-up sources, or measuring firmware current draw. Activates on queries about WFI, STOP mode, STM32 PWR, nRF sleep, wake-up EXTI, or reducing embedded power consumption.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before shipping RTOS idle hook or bare-metal main loop sleep

    line 17
  2. Very specific:

    Ensure pending interrupts are cleared before WFI or wake may be immediate.

    line 43
  3. Distinctive:

    After Stop, re-init clocks and peripherals that lost their registers.

    line 66
  4. Distinctive:

    Use ammeter in series with VDDA/VDD.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Low-Power Embedded

Purpose

Guide agents through MCU low-power modes: sleep vs deep sleep (stop/standby), peripheral and bus clock gating, wake-up source configuration, and practical current measurement — with Cortex-M WFI/WFE and vendor PWR examples (STM32-focused patterns apply broadly).

When to Use

  • Battery-powered firmware missing power budget
  • Wake-up latency vs consumption tradeoffs
  • Debugging "device won't wake" or "current still mA in sleep"
  • Before shipping RTOS idle hook or bare-metal main loop sleep
  • Cross-linking with skills/baremetal/interrupts-and-exceptions-baremetal

Workflow

1. Power mode hierarchy (STM32-style)

ModeCPUPeripheralsRAMWake sourceRelative current
Runononon—highest
Sleepoffononany IRQmedium
Stopoffmost offonEXTI, RTC, UARTlow
Standbyoffofflost*WKUP pins, RTClowest

* Standby clears most SRAM; use backup domain or external EEPROM for state.

2. Enter Sleep (WFI)

/* Cortex-M — sleep until interrupt */
__disable_irq();
/* configure wake source (e.g. EXTI, RTC alarm) */
__enable_irq();
__WFI(); /* or __WFE() for event-based wake */

Ensure pending interrupts are cleared before WFI or wake may be immediate.

3. STM32 Stop mode pattern

#include "stm32f4xx.h"

void enter_stop_mode(void)
{
    /* Gate clocks you do not need */
    RCC->AHB1ENR &= ~RCC_AHB1ENR_GPIOAEN; /* example — only if safe */

    PWR->CR |= PWR_CR_CWUF;   /* clear wake flags */
    PWR->CR |= PWR_CR_PDDS;   /* deep sleep = Stop */
    SCB->SCR |= SCB_SCR_SLEEPDEEP_Msk;

    __WFI();

    /* After wake: re-enable HSE/PLL — clocks lost in Stop on many parts */
    SystemInit();
}

After Stop, re-init clocks and peripherals that lost their registers.

4. Clock gating checklist

Before sleep
├── Disable unused peripheral clocks (RCC xENR)
├── Disable ADC/DAC continuous modes
├── Stop DMA channels
├── Enter peripheral low-power (UART mute, SPI off)
└── Configure lowest viable regulator scale (Voltage Scale 2/3)

5. Wake-up sources

SourceConfig
EXTI GPIOSYSCFG + EXTI IMR, edge trigger
RTC alarmRTC WUT/WAKEUP
UARTStart bit detection (some MCUs)
IWDGNot a wake source — resets device

6. Measurement tips

  • Use ammeter in series with VDDA/VDD; short sampling window for uA
  • DWT cycle counter for wake latency benchmarking
  • Compare run vs sleep current with same clock tree documented

7. RTOS note

FreeRTOS configUSE_TICKLESS_IDLE maps to WFI/Stop — coordinate with skills/embedded/freertos.

8. Agent usage

/low-power-embedded Configure STM32 Stop mode with EXTI0 wake and PLL restore

Common Problems

SymptomCauseFix
Still mA in "sleep"Debug interface active (SWD)Disconnect debugger; disable DBGMCU
Immediate wake from WFIPending NVIC IRQClear flags before WFI
Lost state after wakeEntered Standby not StopUse Stop if RAM must persist
UART dead after wakeClock tree not restoredCall SystemInit() path
Higher than datasheet uAFloating GPIOSet unused pins analog or pull

Related Skills

  • skills/baremetal/interrupts-and-exceptions-baremetal — EXTI wake IRQs
  • skills/baremetal/gpio-baremetal — pin mode for leakage control
  • skills/baremetal/stm32-baremetal — RCC and PWR registers
  • skills/baremetal/timers-pwm-baremetal — stop timers before sleep
  • skills/embedded/freertos — tickless idle integration

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.