Skip to content

Commit ee2e5d0

Browse files
committed
Embed screenshots in README
1 parent 33ae24a commit ee2e5d0

1 file changed

Lines changed: 17 additions & 4 deletions

File tree

README.md

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -75,10 +75,23 @@ dashboard surfaces the offending checks under "Failing checks".
7575

7676
## Screenshots
7777

78-
docs/img/clean_run_dashboard.png ← the PASS dashboard
79-
docs/img/bug_run_dashboard.png ← the FAIL dashboard with addr-7 fails
80-
docs/img/waveform_reset.png ← waveform showing clean reset
81-
docs/img/waveform_addr7_bug.png ← waveform highlighting the corrupted write
78+
### Clean Regression Dashboard
79+
80+
![Clean run dashboard](docs/img/clean_run_dashboard.png)
81+
82+
### Bug Regression Dashboard
83+
84+
![Bug run dashboard](docs/img/bug_run_dashboard.png)
85+
86+
### Clean Reset Waveform
87+
88+
![Clean reset waveform](docs/img/waveform_reset.png)
89+
90+
### Intentional Address-7 Bug Waveform
91+
92+
![Address 7 bug waveform](docs/img/waveform_addr7_bug.png)
93+
94+
In the bug waveform, the DUT stores the corrupted value at address 7 while the testbench shadow memory keeps the expected value, so the self-checking testbench increments `fail_count`.
8295

8396
## What this project demonstrates
8497

0 commit comments

Comments
 (0)