Work it through
A completion arrives after timeout
Reusing the buffer immediately can let a late DMA write corrupt unrelated work.
Test the recovery protocol with a late completion and a new request using the same address.
Your next page is on its way.
End-to-end integration
Model real boot, interrupt, mailbox, doorbell, timeout, and recovery behavior without waiting for a full firmware image to execute in a slow RTL simulator.

A worked mechanism
A doorbell transfers responsibility for a descriptor; elapsed time alone cannot prove hardware stopped using it.
CPU prepares → device owns
Perform the required mapping, cache maintenance and ordering for this platform before the doorbell.
status unknown; device may still run
Record the timeout without reusing the descriptor or payload storage.
abort/reset acknowledged → reclaim
Only the documented stop and drain guarantee permits CPU ownership again.
Work it through
Reusing the buffer immediately can let a late DMA write corrupt unrelated work.
Test the recovery protocol with a late completion and a new request using the same address.
A firmware-equivalent UVM sequence proves the modeled programming flow, not every behavior of a real compiler, cache or driver.
Compare shared headers and driver behavior, then verify abort, drain, late IRQ, stale status and restart on a suitable firmware platform.
Follow a descriptor from software publication through hardware readiness and acknowledgement, including a timeout recovery path.
| Signal / state | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| DESCRIPTOR | visible | owned | owned | released |
| DOORBELL | 0 | 1 | 0 | 0 |
| STATUS | idle | pending | ready | acked |
| OWNERSHIP | software | hardware | hardware | software |
Program descriptor data and establish the platform-specific visibility required before notifying hardware.
Check descriptor fields and the required ordering/visibility operation.
write_descriptor();
make_descriptor_visible_to_device();Example contract. T is the timeout required by the interface contract, not a numeric platform guarantee. Timeout wins at elapsed ≥ T, including a simultaneous readiness response. The fixture cancels the old request on timeout; a later response is retained as diagnostic evidence and cannot complete a new request. Checkpoints show selected state changes, not equally spaced simulation cycles.
SW writes Doorbell
-> HW starts the mailbox state machine
-> HW signals Ready
-> SW Acknowledges
-> transaction completes within the specified timeout
Interrupt coalescing:
interrupt when packet_count == N
OR when the coalescing timer expiresPages 62 through 65 contain no source code. This native contract preserves the source's required doorbell, Ready/Acknowledge, timeout, recovery, and coalescing relationships.
The verification sequence mirrors the firmware flow and checks programming order, hardware work, timeout behavior, interrupt status, acknowledgement, and recovery.
The verification environment reuses the software contract while replacing slow full-firmware execution with UVM and DPI-controlled transactions.
Write SystemVerilog sequences that follow the Software Programming Guide and mirror boot and interrupt flows.
Call the software team's C functions through DPI-C and adapt those operations into UVM agent transactions.
| Component | Responsibility | Required change |
|---|---|---|
| Firmware-equivalent sequence | Programming flow | Mirror the software boot, register, interrupt, mailbox, and recovery order. |
| DPI-C adapter | Driver reuse | Translate C driver calls, headers, and checksum operations into UVM transactions. |
| HW agent | Timing and fault injection | Randomize Ready, Acknowledge, interrupt, and slow-response behavior. |
| HSI scoreboard | End-to-end contract | Check doorbell state transitions, timeout recovery, and interrupt coalescing. |
SW writes Doorbell
-> HW starts the mailbox state machine
-> HW signals Ready
-> SW Acknowledges
-> transaction completes within the specified timeout
Interrupt coalescing:
interrupt when packet_count == N
OR when the coalescing timer expiresPages 62 through 65 contain no source code. This native contract preserves the source's required doorbell, Ready/Acknowledge, timeout, recovery, and coalescing relationships.
It is a register software writes to notify hardware that a task is ready. The write triggers a hardware state machine.
Inject slow responses from the hardware agent and require the software sequence to enter its recovery flow instead of hanging.
Verify that hardware interrupts software only after N packets arrive or the coalescing timer expires, reducing CPU context-switch overhead.