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 per-port descriptor BFM, written clean-room from tsn_switch‘s own documented ingress/egress descriptor interface and CSR register map — not from its internal forwarding FSM — drives SEND_INGRESS/drains RECV_EGRESS on the real catalog tsn_switch. A passive checker builds its own MAC-learning/destination-lookup model purely from observed ingress traffic and cross-checks every real egress port firing and its echoed descriptor fields against it. Covers source learning, unicast forwarding with split-horizon, and flood-on-miss/broadcast-DA — the generic L2 forwarding contract this descriptor-level abstraction exposes. This is a header/descriptor-level model (parsed {da,sa,vlan,prio,len} fields, not raw byte-stream Ethernet framing); the MAC/PHY datapath is the separate catalog gmac IP per tsn_switch‘s own integration-guide pointer.
SEND_INGRESS/RECV_EGRESS task API drives/observes the real per-port ingress/egress descriptor ports directly — no shared code with the DUTIEEE 802.1 TSN task-group standards, 802.1AS (gPTP), 802.1AE (MACsec)
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