A3.9.3 Forever After the Request

MediumDebug10 minKey: IEEE 1800-2017, checkedReview the topic

An unbounded always after each request: give each attempt's verdict, including those open at the end.

Hardware context: A link that must stay ok forever after each request. Read an unbounded, weak always at the end of a test.

From each request on, ok must hold at every edge, the request edge included.

The trace gives the sampled values at ten rising edges; the test ends after the tenth. Six attempts are asked. For each, choose its verdict and the edge where it is decided.

The Assertion and the Trace

Req |-> Always Okreq |-> always ok
req |-> always okAttempts start at edge 1 (t=5), edge 2 (t=15), edge 5 (t=45), edge 6 (t=55), edge 9 (t=85), edge 10 (t=95).edgetime152153254355456557658759851095clkreqokattemptsattempt @5?attempt @15?attempt @45?attempt @55?attempt @85?attempt @95?
Scroll horizontally ↔
Read the sampled values as text
  • req: edge 1 = 0, edge 2 = 1, edge 3 = 0, edge 4 = 0, edge 5 = 0, edge 6 = 1, edge 7 = 0, edge 8 = 0, edge 9 = 1, edge 10 = 0
  • ok: edge 1 = 1, edge 2 = 1, edge 3 = 1, edge 4 = 1, edge 5 = 0, edge 6 = 1, edge 7 = 1, edge 8 = 1, edge 9 = 1, edge 10 = 1

Standard behaviour: no free simulator runs this construct correctly. The key was derived by hand from IEEE 1800-2017 and checked independently.

Simulator note: Verilator 5.052 misses failures of an unbounded always (measured). The key is the standard behaviour, checked against an independent evaluator.

How to Answer

For each attempt, choose its verdict and the edge where that verdict is decided. A vacuous attempt is graded on its verdict only. A pending one is still running at the end of the run.

  • Answer every attempt: its verdict, and the edge where that verdict is decided.
  • Read the values the assertion samples at each edge (the dots), not the values after the edge.
  • Run grades the first attempt and says whether it is right. Submit grades every attempt and says only whether all are right.
Full specification
The assertion
a1: assert property (@(posedge clk) req |-> always ok);

The clock rises at 5, 15, 25, ... 95. The test ends at 100, after the tenth edge.

Hints

Hint 1

always ok starts at the edge of the attempt itself.

Hint 2

An unbounded always can fail, but it never finishes inside a test.

Hint 3

Is unbounded always weak or strong?

What is checked: The verdict and decision edge of six attempts, against the standard key derived in docs/sva-standard-traces/A3.md (sva-089-b).

More problems on this topic

Report a problem with this page

Your answers 6 attemptsSaved locally

req |-> always ok

AttemptVerdictDecided atResult
attempt @5starts at edge 1 (t=5)
attempt @15starts at edge 2 (t=15)
attempt @45starts at edge 5 (t=45)
attempt @55starts at edge 6 (t=55)
attempt @85starts at edge 9 (t=85)
attempt @95starts at edge 10 (t=95)

Edges and times match the trace figure. Your answers stay in this browser until you submit.

Not checked yet

Run checks the first attempt. Submit checks every attempt.

Key: IEEE 1800-2017, checked