Q: Explain AXI ordering with IDs and where a bridge can break assumptions.
A strong answer names the layer, transaction identity, metric, artifact, and regression plan.
Trap: buzzwords without waveform/log/counter evidence.Q: How do you debug DDR bandwidth collapse when peak bus width looks sufficient?
A strong answer names the layer, transaction identity, metric, artifact, and regression plan.
Trap: buzzwords without waveform/log/counter evidence.Q: What evidence separates PCIe link training failure from firmware enumeration failure?
A strong answer names the layer, transaction identity, metric, artifact, and regression plan.
Trap: buzzwords without waveform/log/counter evidence.Q: How do VIP, assertions, and scoreboards divide protocol verification responsibility?
A strong answer names the layer, transaction identity, metric, artifact, and regression plan.
Trap: buzzwords without waveform/log/counter evidence.Q: What is the difference between protocol correctness and product performance?
A strong answer names the layer, transaction identity, metric, artifact, and regression plan.
Trap: buzzwords without waveform/log/counter evidence.LAYER -> TRANSACTION -> METRIC -> ARTIFACT -> FIX -> REGRESSIONintent -> transaction -> channel -> physicalName layer
Name ID
Name artifact
Connect every protocol claim to a transaction identity and measurable metric.
Store the artifact (waveform, log, counter) next to every signoff decision.
Debugging timeouts without finding the first bad transaction.
Quoting peak bus width without payload efficiency and retry overhead.
Treating VIP compliance as a substitute for system integration replay.