Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • The NanoSoC Tour
  • Reading Path
  • SoC Glossary10
  • SoC Metrics Reference
  • SoC Cheatsheet
  • What SoC Integration Is12
  • Architecture and Budgets21
  • Memory Maps and Address Decode26
  • Interconnect and Bus Fabrics26
  • Clock and Reset Architecture24
  • Power Architecture21
    • Power Domains and States
    • Isolation and Retention Integration
    • PMU and Power Sequencer
      • The Sequencer State Machine
      • Handshakes with the Reset Controller
      • Timeouts, Watchdogs and Refusals
    • Cold-Start Power-Up Sequence
    • Supply Sequencing and PMIC
    • Thermal and Power Envelope
    • DVFS Integration
  • Interrupts, DMA and Peripherals15
  • Memories, Boot and Security21
  • IP Integration and Handoff21
  • Top-Level Verification and Bring-up21
  • Package, Pads and I/O18
  • Chip Signoff and Tapeout18
  • SoC Interview Prep16
  • Capstone: Integrate NanoSoC14
Loading lesson

←Power Architecture
  1. Topics
  2. SoC Design
  3. Power Architecture
  4. PMU and Power Sequencer

Part 6 of 14Part 6 of 14/Power ArchitectureAll levels

PMU and Power Sequencer

The always-on controller that sleeps and wakes the chip: its state machine, its reset handshakes, and its timeouts.

  • 3topics
  • 3lessons

Somebody has to own the 70-clock descent into SLEEP and the 14.073 µs climb out, trusting the driver to quiesce the DMA before it asks, and timing out waits that never complete. On NanoSoC that somebody is the power sequencer inside nano_rstpwr, an always-on finite state machine with reset-controller handshakes on both ends. This topic reads it as an FSM, wires it to the reset tree, and sizes every timeout so the chip can neither hang nor hurry.

Lesson

After it you can...

The Sequencer State Machine

Walk every state, transition and output of the NanoSoC power sequencer.

Handshakes with the Reset Controller

Trace SW_OFF_REQ to switch, and pgood to reset release, across the two controllers.

Timeouts, Watchdogs and Refusals

Size each timeout, handle a block that refuses to quiesce, and never hang a sleep request.

Suggested order: top to bottom. The FSM is the map, the handshakes are the borders with the reset controller, and the timeouts are what keeps both honest. Readers arriving from a wake failure should start at the handshake lesson and check RST_CAUSE first.

Check yourself Why must the sequencer live in PD_AON and not with the blocks it switches?

Because it has to act while PD_SW is dead: open the switch on entry and close it, wait out the ramp and relock the PLL on exit. Logic inside PD_SW cannot cause its own resurrection.

Expect to sketch a power FSM on a whiteboard with quiesce, isolate, reset and switch states plus timeout arcs. The NanoSoC machine below is the reference sketch to memorise.

PreviousNext: The Sequencer State Machine

Up next

Up nextThe Sequencer State Machine

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Power Domains and States
  • Isolation and Retention Integration
  • Cold-Start Power-Up Sequence