Functional constraints were loaded into test mode. What evidence exposes it?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
Compare scenario-mode associations, clocks, case analysis, I/O delays, and exception membership across modes.
Technical Explanation
Treat this as a readiness check. It should produce named objects and a result that another engineer can repeat from the same handoff.
What To Check
• Warning sign: Test analysis inherits functional constants or functional interfaces disappear. • Inspect: Keep at least two possible causes open, then use one named object and the active mode or scenario to separate them. • Correct: Reload constraints in their intended mode context and compare mode-specific reports before proceeding.
Command Checks & Actions
• report_scenarios: shows the MCMM scenario matrix and analysis status
• report_clocks: shows clock definitions and relationships
• report_case_analysis: shows constants applied for the active mode
• report_exceptions: shows timing exceptions and their scope
Run the commands in order. Each line answers a separate part of the check.Healthy, Suspicious & Hard-stop Results
• Expected: Compare scenario-mode associations, clocks, case analysis, I/O delays, and exception membership across modes. • Investigate: Test analysis inherits functional constants or functional interfaces disappear. • Stop before floorplanning when required logic or timing coverage is missing or unexplained. Reload constraints in their intended mode context and compare mode-specific reports before proceeding.
Common Mistake
Do not assume the check passed just because ICC2 continued: Test analysis inherits functional constants or functional interfaces disappear. Fix or narrowly justify the named objects, then rerun the same command.
What The Interviewer Is Testing
Be ready to explain why this matters before floorplanning: Test analysis inherits functional constants or functional interfaces disappear.
Follow-up Question & Model Response
Model response: “I would save the report, inspect one affected object in the correct block and scenario, and make or request this correction: Reload constraints in their intended mode context and compare mode-specific reports before proceeding. Then I would reopen the clean checkpoint and rerun the same evidence.”
Practical Example
Symptom: Test analysis inherits functional constants or functional interfaces disappear. Corrective path: Reload constraints in their intended mode context and compare mode-specific reports before proceeding.
Continue practising