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 GPIO pin driver, written clean-room against the pad-level contract — not derived from our own gpio RTL — so it functions as a true second source. Ships with a passive contract checker that verifies pull-up/pull-down pad contention and output-readback consistency (a symmetric delay line, not a same-cycle combinational compare), and a self-checking interop TB proving bit-loopback, the DSET/DCLR/DTGL atomic aliases, independent input, and both edge- and level-triggered interrupt modes against the catalog’s gpio. Covers per-pin input/output/interrupt behavior on a single-instance pad today — wake-from-low-power sequencing and multiplexed-pin sharing with the catalog’s SPI/I2C IP are a documented roadmap item, not yet built.
DRIVE/PULSE_BIT task API on the pad’s input sidegpio: bit-loopback proof, DSET/DCLR/DTGL aliases, independent input, edge- and level-mode IRQ — all passGeneric GPIO verification (no fixed external spec)
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