Develop the architecture-based test plan, justify a methodology at every layer, and build/harden a runnable Synopsys verification environment.
- Read the current assignment and artifact locations.
- Work on a branch and open a PR for
@abhinavnandwaniusing CONTRIBUTING.md. Main requires a code-owner approval; admins can bypass.
- Architecture-based test plan
- Per-layer methodology using Synopsys
- Runnable and hardened verification scaffold
| Location | Purpose |
|---|---|
| plans/ | Versioned test plan and requirements-to-tests/coverage mapping for issue #2. Use stable requirement/test IDs; identify assumptions and proposed completion criteria. |
| docs/methodology/ | Per-layer methodology matrix, environment diagram, alternatives and feasibility evidence for issue #3. Identify the Synopsys role at each layer. |
| models/ | Independent reference models and documented numerical/timing semantics. Cite provenance and explain how the model differs from the implementation it checks. |
| tb/unit/ | Unit pilot testbenches, stimulus, checking and coverage. The existing tb/pe_mac_smoke_tb.sv remains an Icarus example, not completion of the Synopsys requirement. |
| tb/integration/ | Integration/SoC pilot and its connection to RTL. Label every stub and the scope of behavior actually checked. |
| scripts/regression/ | Team-owned VCS compile/run, Verdi debug/coverage and deterministic regression entry points for issue #4. These are deliverables to implement, not working commands supplied by this folder. |
An independent Icarus MAC smoke test exists. Synopsys setup, unit/integration pilots and the test/methodology proposals remain open team deliverables; this refresh does not claim they have run.
Shared diagram · Software evidence
CHARTER.md and OBJECTIVES.md describe the longer-term purpose. Current issues and the starting guide specify the work assigned now. SETUP.md describes existing example commands and scope.
Verilator routing pilot: test scope.