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
    • 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

←SoC Design
  1. Topics
  2. SoC Design
  3. Power Architecture

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

Power Architecture

Power domains, isolation, sequencing, supply, thermal and DVFS on NanoSoC: the integrator's view of power.

  • 7topics
  • 21lessons

Software sees power as three states and a wake latency; the integrator sees everything underneath: which blocks share a switch, which signals need clamping, what order the rails, clocks and resets come up in, and what happens when any of it is wrong by one cycle. NanoSoC keeps the physics small — two power domains, one 0.9 V supply, 114 isolation clamps, a 14.073 µs wake and a single always-on controller — but it contains every classic power-integration problem: a switchable domain that must be isolated before it is reset and powered off, a sequencer that must handshake with the reset controller, a cold start where the crystal, the PLL and three resets line up in one 53.948 µs timeline, a board supply that can brown out under load, an 82.74 mW RUN budget that becomes heat, and a voltage-frequency ordering rule that must never be inverted. This section teaches power as the integrator owns it: domains and states first, then the circuitry that makes them safe, then the sequences, the supply, the heat, and the operating points. Every number about NanoSoC is a NanoSoC teaching value used consistently across the course; any other number is labelled illustrative.

Topic

What it covers

After it you can...

Power Domains and States

PD_AON and PD_SW, the RUN, IDLE and SLEEP table, what is retained

Place every NanoSoC block in its domain and cost each power state in milliwatts.

Isolation and Retention Integration

Where the 114 clamps go, enable timing, save and restore, the UPF view

Check every crossing from PD_SW into PD_AON and review an isolation sequence.

PMU and Power Sequencer

The sequencer state machine, handshakes with the reset controller, timeouts

Read the NanoSoC power sequence as an FSM and size its timeouts.

Cold-Start Power-Up Sequence

Supply ramp, POR, crystal, PLL lock, reset release and boot as one timeline

Recompute the 53.948 µs hardware timeline and say where boot time really goes.

Supply Sequencing and PMIC

Rail order, power-good, PMIC handshake, brown-out, the package and board view

Specify a rail order with power-good checks and a brown-out response.

Thermal and Power Envelope

From milliwatts to degrees, throttling policy, sensors

Turn the NanoSoC power table into a temperature and a throttling plan.

DVFS Integration

Voltage and frequency ordering, clock switching, safe operating points

Review a voltage-frequency transition for ordering, crossing and regulator risk.

Suggested order: top to bottom. Domains and states define what must be built; isolation and the sequencer build it; cold start strings every wait into one timeline; supply sequencing zooms out to the board; thermal and DVFS close the loop on what the chip may do once it is running. Readers chasing a wake failure can start at the sequencer topic and follow the links back to isolation; readers sizing a product start at thermal. For the low-power vocabulary and mechanism behind these lessons see Power Domain Basics; for the reset side of every sequence see Reset Is a System Contract.

Check yourself Why does power architecture come before DVFS and thermal in this section?

Because DVFS and thermal manage a running chip, while domains, isolation, sequencing and supply decide whether the chip wakes at all. The operating points only make sense once the rails and the wake sequence are correct.

Be ready to draw the two NanoSoC domains with their blocks, recite the 114-clamp count by group, and walk the cold-start timeline with the NanoSoC numbers.

Related topics

  • Up: SoC Design course hub

  • NanoSoC Tour

  • Glossary

  • Low Power: Power Domain Basics

PreviousNext: Always-On Domain, Wake Policy and a Timer Extension

Up next

Up nextAlways-On Domain, Wake Policy and a Timer Extension

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • How to Use This Course
  • The NanoSoC Tour
  • Reading Path