Avionics, Space & Mil-Std Networking

SpaceWire N-Port Routing Switch

ECSS-E-ST-50-12C §10 wormhole crossbar router for multi-node SpaceWire networks, ASIL-B.

Request this IP →Browse the catalog

ASIL-B

target

90.75%

SPFM

90.00%

LFM

PASS

FMEDA

10.2K

gates

0.1.0

version

Interfaces at a glance

Block diagram

The deliverable

What you’re licensing

ECSS-E-ST-50-12C §10 wormhole crossbar router for multi-node SpaceWire networks, ASIL-B. It is delivered as a licensable soft-IP block engineered as an ASIL-B Safety Element out of Context — not just RTL, but the complete functional-safety work package needed to carry it into an ISO 26262 program:

Synthesizable RTL

Portable, vendor-neutral SystemVerilog that drops onto your existing SoC fabric — no foundry or EDA-tool lock-in.

Per-IP FMEDA report

SPFM / LFM / PMHF computed against the ASIL target per ISO 26262-5 — the quantitative analysis your assessor asks for.

Safety manual

Assumptions of use, the safety mechanisms and their diagnostic coverage — written to drop straight into your safety case.

IP-XACT + integration docs

A machine-readable descriptor plus register and integration documentation for fast, low-risk bring-up.

Self-checking testbench

A self-checking testbench and a one-command build, so you can reproduce every claim on day one.

spw_router is a SpaceWire (ECSS-E-ST-50-12C §10) N-port routing switch, delivered as synthesizable SystemVerilog with an APB4 configuration slave and a rad-tolerant / ASIL-B safety overlay.

Key Features

N-port wormhole crossbar, NPORT = 2..32 (default 4); a granted worm holds its output until the packet’s EOP/EEP is forwarded, then releases it
ECSS path addressing (header 0..31): header names the output port directly, always header-deleted so a nested path route peels one hop at a time
ECSS logical addressing (header 32..255): 224-entry APB routing table, per-entry {DELETE, PORT_MASK}, even-parity protected against SEU (err_code 1)
Group-adaptive routing: a multi-bit PORT_MASK names a candidate output set; round-robin arbitration grants the worm to whichever member is free, so no input is starved
Per-port error containment: an out-of-range path port or unrouted logical address is swallowed locally (err_code 3) without corrupting or blocking any other port’s routing/arbitration
Complementary-DMR route-ownership shadow (err_code 9) plus the shared safety_monitor aggregator, formally proved mutual-exclusion / route-consistency / no-false-trip
Single clock domain (make cdc IP=spw\_router reports zero crossings) — the per-port DS recovered-clock crossing lives in each spacewire link instance, not the switch fabric

Standards & Compliance

ECSS-E-ST-50-12C §10 (SpaceWire); ECSS-Q-ST-60-02C device assurance + ECSS-Q-ST-60-13 radiation (TID/SEE); ISO 26262 ASIL-B SEooC (SPFM 90.75%, LFM 90.00%, PMHF 1.78×10⁻⁸/h)

Functional Safety

ASIL-B (SEooC) · SPFM 90.75% · LFM 90.00% · PASS

ISO 26262-5 FMEDA method (transferable evidence for the ECSS-Q-ST-60 / radiation case) · FMEDA available · Safety Manual included

Register Map

See datasheet for full register reference.

Getting Started

// Minimal instantiation
spw_router #(
 .ADDR_W(6)
) u_spw_router (
 .clk (clk),
 .rst_n (rst_n),
 // APB4
 .p_paddr (paddr),
 .p_psel (psel),
 .p_penable (penable),
 .p_pwrite (pwrite),
 .p_pwdata (pwdata),
 .p_prdata (prdata),
 .p_pready (pready),
 // Safety
 .err_clear (1'b0),
 .err_valid (err_valid),
 .err_code (err_code)
);

Configure via the CTRL register after reset to enable the IP and set operating parameters. Monitor err_valid / err_code for any safety faults reported by the built-in safety monitor.

Applications

Where it fits

Typically deployed in avionics, defense, and space systems built to the ARINC, MIL-STD, and CCSDS standards.

The case

Why license it, not build it

Skip 12–18 months

The FMEDA and the safety case are already generated. You integrate a finished safety element — you don’t stand up a safety-IP program to originate one.

One vendor, one safety story

Every block in the catalog shares the same safety architecture, fault-reaction model, and FMEDA methodology — so subsystems roll up cleanly.

Verified, not vapor

The RTL builds and passes today; the safety metrics come from analysis and fault injection against real RTL, not a datasheet promise.

Interested in SpaceWire N-Port Routing Switch?

Pricing, the per-IP FMEDA, safety manual, and RTL data room are shared under a mutual NDA.

Talk to us →See related IP

Figures are pre-silicon engineering-grade estimates for a Safety Element out of Context (SEooC); final ASIL sign-off is the integrator’s, supported under NDA. FMEDA and Safety Manual available under NDA.

circuit-design.space · +1-971-357-1400 · anovickis@circuit-design.space