Senior verification work is judgment more than syntax. This part covers systematic debug, code review, verification strategy, interview preparation, and a FIFO capstone from spec to sign-off.
Topic | Lessons | What it covers | Path | Time |
|---|---|---|---|---|
4 | Triage, waveform, testbench, and X and race methods with worked cases for senior debug. | Required | 30 min | |
4 | Testbenches fail by passing: checklists for stimulus, components, assertions, and review process. | Recommended | 30 min | |
4 | Turn a spec into a plan, pick the method mix, track honest metrics, and drive risk to sign-off. | Required | 30 min | |
5 | Revision: senior interview questions on language, plumbing, classes, checks and design scenarios, with links back to the lessons that teach them. | Optional | 40 min | |
6 | A complete verification environment for a parameterized FIFO, from spec and plan to a run that catches a planted bug. It extends the PacketFIFO project. | Recommended | 45 min |
Path: Required is the core first pass for senior judgment, Recommended is what most learners should read, and Optional is reference, specialist or revision material you can skip on a first pass.
Failure Triage Method and Waveform Debug Strategy: the first-error habit and pin-level evidence.
Spec to Verification Plan and Risk, Schedule, and Sign-Off: what to build and when the evidence is enough.
Review Process & Checklist: the three-pass review method.
Spec Analysis and Verification Plan: the plan the whole capstone traces back to.
Hunting X's and Races and Debugging the Testbench: when a real failure needs them.
The three artifact reviews in Reviewing Verification Code, when you review a teammate's pull request.
Choosing the Methodology Mix and Milestones and Progress Metrics: before you own a plan.
The Interview Q&A Bank: in the final week before interviews.
Because most intermittent failures come from stimulus, seeds, or checker races rather than the RTL. Rule out the testbench with a minimal repeatable seed first. Taught in Failure Triage Method.
The compare count and the leftover expected-queue depth. Zero compares, or a nonempty queue at the end, means the run checked nothing. Taught in Reviewing TB Components.
No. It names no stimulus and no check. Split it until each row pairs one behavior with one check and one coverage point. Taught in Spec to Verification Plan.
A zero-delay loop: combinational feedback or a wait that never yields time. Pause the simulator and look at the spinning process. If time keeps advancing instead, look for a blocked wait. The timeout-or-hang signature is in Failure Triage Method, heartbeats are in Debugging the Testbench, and the frozen-time question is drilled in Q&A: Scenario and Design Questions.
No. Sign-off needs coverage merged across the whole soak and the configs, written dispositions for every hole, and a converged bug rate. One seed proves the mechanisms run. Taught in Regression, Holes and Sign-off.