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.
The deepest asset in this catalog’s VIP line: a clean-room CHI Home Node family spanning single-requester (credited TX-channel completion, DBIDResp/Comp/CompDBIDResp/CompData sequencing, injectable RespErr) up to full directory coherence — a per-line MESI directory Home Node driving snoops (SnpShared/SnpUnique) against a companion snoopable RN-F BFM that answers with downgrade/invalidate/dirty-forward. Proven directly against this catalog’s own kvce_chi_rnf (8/8 pass) and a 2-RN-F coherence scenario (16/16 pass, migration + downgrade + WriteBack).
chi_hn_bfm — single-requester Home Node: credits RN-F TX channels, models backing memory, INJECT_DERR/INJECT_NDERRchi_hn_dir_bfm — directory-coherent Home Node: per-line MESI state, issues SnpShared/SnpUnique, pulls dirty data forwardchi_rnf_bfm — snoopable RN-F: one cached line + MESI state, answers snoops with downgrade/invalidate/forwardARM AMBA 5 CHI (Issue E)
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