Low Power Verification · All levels

Low Power Verification Cheatsheet

Dense reference for mechanism-first LPV debugging and signoff-ready closure decisions.

Debug order

diagram

SYMPTOM -> LPV CLASS -> ARTIFACT -> OWNER -> DECISION

SETUP: intent alignment, tool semantics, and run metadata
TRANSITIONS: PST legality, sequencing, and concurrent events
BOUNDARIES: isolation timing, clamp behavior, and level shifting
RETENTION: save/restore ordering and multi-cycle state integrity
X-PROP: actionable failures versus expected corruption behavior

Questions before proposing a fix

Which boundary fails first and is it reproducible?
Which artifact proves mechanism, not correlation?
Who owns the smallest reversible fix?
What validation and rollback gates close risk?
How do we prevent this LPV bug class from recurring?

Practice this lesson