Available now — real, tested verification collateral, not a roadmap placeholder.
Verification IP is not safety-rated. These are testbench components — no ASIL target, no FMEDA, no IP-XACT, no safety-mechanism interface. They exist to help you verify a design, not to carry a safety argument. The safety soft-IP catalog is over here.
An independent SPI master, written clean-room from the de facto 4-wire SCK/MOSI/MISO/CS_n convention — not derived from our own spi_master/spi_slave RTL — so it functions as a true second source. Ships with a passive protocol checker enforcing SCK-idle-while-deselected, CS-only-changes-while-SCK-low, and byte-multiple transfer framing, and a self-checking interop TB proving MOSI, MISO, and simultaneous full-duplex transfers against the catalog’s spi_slave. Covers Mode 0 (CPOL=0/CPHA=0, the reset default of both spi_master and spi_slave) and single-slave chip-select only today — the remaining CPOL/CPHA modes and Dual/Quad-I/O QSPI framing are a documented roadmap item, not yet built.
XFER_BYTE task APIspi_slave: MOSI path, MISO path, and simultaneous full-duplex — all passDe facto flash-vendor conventions (Motorola/Macronix/Winbond/Micron/Samsung)
Built to lean against these catalog IPs during integration:
Deliverables, the file manifest, and licensing terms are shared under a mutual NDA.
Verification IP is testbench collateral and is deliberately not safety-rated: no ASIL target, no FMEDA, and no IP-XACT descriptor. It carries no functional-safety claim.
circuit-design.space · +1-971-357-1400 · sales@circuit-design.space