← All Verification IP
Automotive Networking

FlexRay

An independent, clean-room FlexRay static-segment node — written from the public ISO 17458 frame/CRC semantics…

Request this VIP →Browse all VIP
shippingGroup Automotive NetworkingStandard ISO 17458 (FlexRay Communications System)

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 FlexRay static-segment node — written from the public ISO 17458 frame/CRC semantics, not from the catalog’s own flexray FSM — that configures a real multi-slot TDMA schedule over APB, decodes the DUT’s own transmissions off the wire with an independently recomputed header-CRC-11 and frame-CRC-24, and injects frames into the DUT’s receive path over a genuinely separate RX wire. Covers the static segment only (FlexRay’s core deterministic scheduling mechanism); the dynamic (minislotting), symbol-window, and NIT segments are counted-but-unstructured place-holders in this RTL and are out of scope. Single active channel per interop scenario against an 8-byte tractable payload subset (matching the DUT’s PAYLOAD_MAX default), with a directed characterization proving the DUT’s two channels mirror identical TX content and are not independently operable. This second-source effort also surfaced a real RTL finding, fixed 2026-07-09: the DUT’s protocol-fault path checked only header-CRC on receive, not frame-CRC — a frame with a good header but corrupted frame CRC was silently buffered without ever raising a safety fault (correctly flagged in the RX metadata, but not escalated). Fixed by recomputing the frame-CRC-ok expression fresh in the fault check rather than reading the register the DUT updates the same cycle; the VIP’s own interop TB now proves the fault correctly fires (err_code 3).

Key Features

Standards & Compliance

ISO 17458 (FlexRay Communications System)

Pairs With

Built to lean against these catalog IPs during integration:

Interested in the FlexRay 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 · sales@circuit-design.space