|
3 | 3 | This chapter presents the available models and tools which are used for I3C verification.
|
4 | 4 | The core is verified with [the Cocotb/Verilator + unit tests](https://github.com/chipsalliance/i3c-core/tree/main/verification/cocotb/block) and [the UVM test suite](https://github.com/chipsalliance/i3c-core/tree/main/verification/uvm_i3c).
|
5 | 5 |
|
6 |
| -## Verification plan |
| 6 | +There are also non-public tests which utilize Avery I3C VIP framework. The tests include: `private_read`, `private_write` and `recovery` and verify operation of target mode private reads and writes and the secure firmware recovery flow respectively. |
7 | 7 |
|
8 |
| -The verification plans can be found [here](https://github.com/chipsalliance/i3c-core/tree/main/verification/uvm_i3c). |
| 8 | +## Testplans |
| 9 | + |
| 10 | +This section contains testplans for the verification. |
| 11 | + |
| 12 | +Definitions: |
| 13 | +* `testplan` - an organized collection of testpoints |
| 14 | +* `testpoint` - an actionable item, which can be turned into a test: |
| 15 | + * `name` - typically related to the tested feature |
| 16 | + * `desc` - detailed description; should contain description of the feature, configuration mode, stimuli, expected behavior. |
| 17 | + * `stage` - can be used to assign testpoints to milestones. |
| 18 | + * `tests` - names of implemented tests, which cover the testpoint. Relation test-testpoint can be many to many. |
| 19 | + * `tags` - additional tags that can be used to group testpoints |
| 20 | + |
| 21 | +### Testplans for individual blocks |
| 22 | + |
| 23 | +```{include} ../../verification/testplan/generated/bus_monitor.md |
| 24 | +``` |
| 25 | +```{include} ../../verification/testplan/generated/bus_rx_flow.md |
| 26 | +``` |
| 27 | +```{include} ../../verification/testplan/generated/bus_timers.md |
| 28 | +``` |
| 29 | +```{include} ../../verification/testplan/generated/bus_tx_flow.md |
| 30 | +``` |
| 31 | +```{include} ../../verification/testplan/generated/bus_tx.md |
| 32 | +``` |
| 33 | +```{include} ../../verification/testplan/generated/ccc.md |
| 34 | +``` |
| 35 | +```{include} ../../verification/testplan/generated/csr_sw_access.md |
| 36 | +``` |
| 37 | +```{include} ../../verification/testplan/generated/descriptor_rx.md |
| 38 | +``` |
| 39 | +```{include} ../../verification/testplan/generated/descriptor_tx.md |
| 40 | +``` |
| 41 | +```{include} ../../verification/testplan/generated/drivers.md |
| 42 | +``` |
| 43 | +```{include} ../../verification/testplan/generated/edge_detector.md |
| 44 | +``` |
| 45 | +```{include} ../../verification/testplan/generated/flow_standby_i3c.md |
| 46 | +``` |
| 47 | +```{include} ../../verification/testplan/generated/hci_queues.md |
| 48 | +``` |
| 49 | +```{include} ../../verification/testplan/generated/tti_queues.md |
| 50 | +``` |
| 51 | +```{include} ../../verification/testplan/generated/i3c_bus_monitor.md |
| 52 | +``` |
| 53 | +```{include} ../../verification/testplan/generated/pec.md |
| 54 | +``` |
| 55 | +```{include} ../../verification/testplan/generated/width_converter_8toN.md |
| 56 | +``` |
| 57 | +```{include} ../../verification/testplan/generated/width_converter_Nto8.md |
| 58 | +``` |
| 59 | + |
| 60 | +### Testplans for the core |
| 61 | + |
| 62 | +```{include} ../../verification/testplan/generated/target_ccc.md |
| 63 | +``` |
| 64 | +```{include} ../../verification/testplan/generated/target_hdr.md |
| 65 | +``` |
| 66 | +```{include} ../../verification/testplan/generated/target_interrupts.md |
| 67 | +``` |
| 68 | +```{include} ../../verification/testplan/generated/target.md |
| 69 | +``` |
| 70 | +```{include} ../../verification/testplan/generated/target_recovery.md |
| 71 | +``` |
| 72 | +```{include} ../../verification/testplan/generated/target_reset.md |
0 commit comments