In short: AXI (Advanced eXtensible Interface) is an on-chip bus from the AMBA family that moves data using five independent channels, address-first bursts, and a simple valid/ready handshake. Cache coherency keeps every cached copy of a memory address in agreement. This guide answers the AXI protocol and cache coherency interview questions the way an interviewer…
In short: The SoC verification flow is the end-to-end process of proving a whole chip works once all its blocks are stitched together. It moves through five stages: pull out the features to test, write a verification plan, build the environment and run tests, close functional and code coverage, then sign off. The focus at…
In short: This is a hands-on tour of SystemVerilog assertions examples using the most-used building blocks: the delay operator ##, overlapping |-> and non-overlapping |=> implication, delay ranges ##[m:n], and the edge detectors $rose and $fell. Each one is shown with a small property, when it passes, and, more importantly, when it fails. Good assertions…
In short: This is a set of the most common coverage interview questions with clear, LRM-correct answers: code vs functional coverage, the code-coverage types, what high-one-low-other numbers mean, covergroups vs cover properties, coverpoints and bins, ignore vs illegal bins, transition and wildcard bins, cross coverage, and the two ways to sample a covergroup. Coverage comes…
In short: Thinking like a verification engineer means you start from the specification and keep asking what can go wrong and why, long before you write a single line of code. Language and methodology are just tools. The real skill is turning a spec into a long list of scenarios, corner cases, and checks that…
In short: These SystemVerilog interview questions are grouped by topic and answered with real, worked code you can run. They cover data types, arrays, classes and OOP, randomization and constraints, threads and events, interfaces and clocking blocks, plus verification metrics. Each answer explains the why, not just the what, so you can defend it in…
In short: Good functional coverage guidelines keep your coverage honest and useful. The essentials: base coverage on the test plan and the spec, keep a traceability link from each scenario to a cover point, add controls to enable or disable coverage, turn coverage on after the early bug storm settles, collect coverage only from passing…
In short: A fork…join block runs its statements in parallel. The three flavours differ in when the parent thread continues: join waits for all spawned threads, join_any waits for the first one to finish, and join_none waits for none and moves on at once. Two helpers go with them: wait fork blocks until all child…
In short: A shallow copy duplicates only the top-level fields of an object. If the object holds a handle to another object, the copy shares that same inner object, so changing it through one handle affects both. A deep copy duplicates the top-level fields and also builds fresh copies of every nested object, so the…
In short: The this keyword is a built-in handle that refers to the current object, the specific instance whose method is running. Its most common use is inside a constructor or method when a parameter has the same name as a class field: this.x = x; means “set this object’s field x to the parameter…