Planned — scoped for this wave; deliverables not yet built. Ask if you need it sooner.
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.
eCPRI packet-based fronthaul: the common header (protocol revision, C bit, message type, payload size), the message types (IQ Data, Bit Sequence, Real-Time Control, Generic Data Transfer, Remote Memory Access, One-Way Delay Measurement, Remote Reset, Event Indication), PC_ID/SEQ_ID stream identification and concatenation of several eCPRI messages in one Ethernet frame. Split out of vip-cpri because they are not one product: classic CPRI is constant-bit-rate over a vendor SerDes and genuinely PHY-gated, while eCPRI rides ordinary Ethernet or UDP/IP and is pure packet protocol — exactly the layer this catalog builds well, and the same call that unparked NVMe and Interlaken. This repo already carries the Ethernet layer beneath it (gmac, eth_t1_mac, tsn_switch, eth_pfc).
eCPRI Specification (Ethernet-based Common Public Radio Interface)
Built to lean against these catalog IPs during integration:
This VIP is scoped but not yet built — tell us your timeline and we will reorder the wave.
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