← All Verification IP
PCIe / CXL

CXL.mem (transaction layer)

An independent clean-room CXL.mem VIP, and this one is DUT INTEROP rather than a BFM self-check: ip/cxl_mem_dev is a real Type-3 memory expander in this catalog…

Request this VIP →Browse all VIP
shippingGroup PCIe / CXLStandard Compute Express Link (CXL) — CXL.mem transaction layer, incl. CXL 3.0 back-invalidate

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 deliverable

What you get

Bus-functional model
An independent driver for the protocol, written clean-room from the public specification — not derived from our own RTL, so it is a genuine second source.
Passive protocol checker
A monitor that watches the bus and asserts the spec’s rules continuously, so a violation fails the run where it happens rather than downstream.
Self-checking interop testbench
A one-command testbench that drives the model against real RTL and hard-checks the result — reproduce every claim on day one.

An independent clean-room CXL.mem VIP, and this one is DUT INTEROP rather than a BFM self-check: ip/cxl_mem_dev is a real Type-3 memory expander in this catalog, so the host root drives the actual RTL and an independently written memory model sits behind its downstream line port (“cxl/, make cxl_oss, 30/30 checks). Covers all four CXL.mem channels (M2S Req / M2S RwD / S2M DRS / S2M NDR), credited S2M flow control, HDM address decode, end-to-end SECDED through the real device (single-bit corrected and counted, double-bit poisoned), downstream bus errors, and the CXL 3.0 back-invalidate pair. Six rules, each pinned by a per-rule mask to its own injected fault. SCOPE: the transaction layer down to the flit boundary. CXL.io and the PCIe link and PHY beneath it are vip-pcie’s and are out of the device’s own scope too; .cache is not modelled, and neither is the multi-device switching that vip-cxl-switch would cover. It found a real defect in the device on its first run: a BISnpInv answered BIRspS — “I kept a shared copy”, which does not satisfy an invalidate — was accepted as completion, and a bias-flip back-invalidate would take Device Bias on it. And its sharpest test is a NEGATIVE one: a DRS flit carries data AND a poison bit, and honouring poison is entirely internal to the receiver. Two hosts fed the identical flit disagree about whether a line the device could not correct becomes live data; every rule passes and the checker is silent.

Key Features

Standards & Compliance

Compute Express Link (CXL) — CXL.mem transaction layer, incl. CXL 3.0 back-invalidate

Pairs With

Built to lean against these catalog IPs during integration:

Interested in the CXL.mem (transaction layer) VIP?

Deliverables, the file manifest, and licensing terms are shared under a mutual NDA.

Talk to us →See related VIP

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 · anovickis@circuit-design.space