What is a "mode," in plain terms?
From PDVerse MMMC Interview Masterclass · pdVerse Mentor Series
Direct answer
A mode describes what the chip is doing right now — running its real function, shifting scan data during test, capturing a test response, or sitting in a low-power state. The netlist doesn't change between modes, but which clocks, which logic paths, and which constraints are actually valid does change.
Mentor explanation
Think about one physical netlist with a test-enable pin. When that pin is low, the chip behaves like a normal processor. When it's high, internal flops reorganize into scan chains and start shifting bits in and out for manufacturing test. Same silicon, same wires, same cells — completely different behavior. A mode is the label for one of those behaviors, and it matters because the timing constraints that are true in one mode (which clock is running, which paths are real, which values are frozen) can be false in another.
Example or conceptual chain
A CPU core might define Functional, Scan Shift, Scan Capture, and Low-Power as four separate modes on the exact same gate-level netlist.
Key takeaways
- A mode describes what the chip is doing right now — running its real function, shifting scan data during test, capturing a test response, or sitting in a low-power state.
- The netlist doesn't change between modes, but which clocks, which logic paths, and which constraints are actually valid does change.
Self-check: can you answer this aloud?
Try a 45-second answer using this structure:
- State the direct answer.
- Explain the timing or physical reason.
- Name one caveat.
- Say how you would verify it in a real flow.
Continue learning free
Get a practical low-power chapter
Receive the existing “Low Power and Multivoltage Fundamentals” PDF chapter and its download link by email.
Keep connecting concepts