[dv] Connect SPI agents to the chip-level UVM testbench (spi_device + spi_host)
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 38
- Forks
- 21
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 14
Description
The chip TB currently ties off the spi_device pins and uses an internal loopback for spi_host, so chip_spi_device_smoke and chip_spi_host_smoke do not exercise agent-driven SPI transactions (only CSR + SW-forced IRQ / internal loopback). Connect a spi_agent to the spi_device pins (agent as SPI host) and a spi_agent to the spi_host pins (agent as device), as done in OpenTitan Earlgrey chip DV, and rewrite the two smokes to drive a real transaction so they meet the chip-level smoke definition. Blocks V1 sign-off of the SPI smokes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the chip-level chip_spi_device_smoke and chip_spi_host_smoke tests and the current spi_device and spi_host pin connections. Compare the setup with OpenTitan Earlgrey chip DV, then identify how each spi_agent should act in the chip testbench. Done means both smokes drive real agent-based SPI transactions rather than only CSR, software-forced IRQ, or internal-loopback behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100