SpaceWire

Independent SpaceWire link-partner BFM, clean-room from the public ECSS-E-ST-50-12C spec — bit-level Data-Strobe encode/decode, the character-level odd-parity chain, and the ErrorReset→Ready→Started→Connecting→Run link-init handshake, driven against the catalog’s own second, genuinely asynchronous spw_rxclk recovered-clock domain. A passive protocol checker instantiated on each direction of the point-to-point link independently re-derives DS legality and the parity chain purely from the wire, with zero hierarchical peeking into either side’s state. Interop-proven against the catalog’s spacewire link-layer IP: brings the link to Run, exchanges N-Chars with EOP framing in both directions (BFM→DUT confirmed via APB RXCHAR read-back; DUT→BFM decoded independently off the real TX pins), plus a directed illegal-DS-transition injection caught by the checker. Only the core spacewire link-layer IP is covered — spw_router, spacewire_rmap, and spacefibre are not exercised by this BFM and remain roadmap.

Key Features

• Independent DS bit-level encoder/decoder (NULL, FCT, EOP, EEP, ESC, N-Char, Time-code) with the spec’s chained odd-parity check — not derived from the target RTL
• Full ErrorReset→Run link-init handshake exercised, including the genuine second spw_rxclk clock domain (not a clk-tied shortcut)
• Bidirectional N-Char exchange with EOP framing, cross-checked over the real APB bus and the real DS pins
• Passive per-direction protocol checker (DS-transition legality, parity-chain self-consistency, link-init ordering) proven against a directed injected fault; RMAP, SpaceFibre, and the multi-port router are roadmap, not covered

Standards & Compliance

ECSS-E-ST-50-12C rev 1 (core link layer only)

Pairs With

Built to lean against these catalog IPs during integration:

• spacewire
• spw_router
• spacewire_rmap
• spacefibre