Production-scale extensions
Four additions for production-scale verification.
These practices close common gaps between a technically sound block-level plan and a system program that remains portable, reproducible, and auditable.01 · PortabilityScenario intent across engines
Keep the scenario graph above pin-level implementation so the same use case can target simulation, emulation, FPGA prototypes, and post-silicon—with engine-specific drivers and checkers.
- Portable Stimulus
- UVM virtual sequences
- Firmware tests
- Capability guards
02 · ObservabilityCorrelation IDs and causal traces
Give a transaction one identity from source request through routing, buffering, retry, completion, interrupt, and firmware acknowledgement. Preserve bounded trace history around failure.
- Accept/commit timestamps
- Config snapshots
- Credit snapshots
- Checkpoint + replay
03 · Fault campaignsInjection is only half the test
Cross fault type and injection point with detection mechanism, detection latency, containment boundary, software-visible status, recovery action, and post-recovery data integrity.
- Detected
- Contained
- Reported
- Recovered
04 · ReproducibilityMake every failure replayable
Record seed, binary, RTL build, topology, register programming, traffic constraints, clock and power schedules, injected faults, and reference-model version as one immutable run manifest.
- Run manifest
- Deterministic seed replay
- Minimal reproducer
- Failure clustering
Portable execution referenceAccellera's Portable Test and Stimulus Standard 3.0 defines a single scenario representation that can produce implementations for simulation, emulation, FPGA prototyping, and post-silicon execution.