- SpaceWire CODEC
- testbench and stimuli to cover the exception conditions described in the standard
- WISHBONE wrapper (optional)
- Triple Modulo Redundant (optional)
- Error Detection and Correction for TX and RX FIFOs (optional)
- makefile for simulation and synthesis (vmake utility)
Tentative release of the following documentation:
- Architectural Requirement Specification (ARS)
- Architectural Verification Plan (AVP)
- Architectural Design Report (ADR)
- Architectural Verification Report (AVR)
In accordance with ECCS-Q-60-02.
Tailoring may be added at network level, but character, exchange and packet level will remain as is defined in the ECSS-E-ST-50-12C.
Tentative first draft for ARS is on December 2011 (hopefully!)
SpaceWire (SpW) grown organically from the needs of on-board processing applications. It's a network of spacecraft/aerocraft with Routers.
Instead of customization in builting system on a project-by-project basis resulting in long development at high cost and risk, SpaceWire focused on the definition of an network architecture for payload data systems. Processing units, mass-memory units and down-link telemetry systems developed for one mission can be readily used on another mission, reducing the cost of development, improving reliability.
(SpaceWire is currently being installed on several NASA and European Space Agency (ESA) spaceships to support onboard communications during space missions.
---27 January, 2003)
SpaceWire standard has taken into consideration two existing standards, IEEE 1355-1995 and ANSI/TIA/EIA-644.
For official publication, please visit
http://www.ecss.nl (registration required)
to download ECSS-E-ST-50-12C "SpaceWire - Links, nodes, routers and networks" by ECSS (31 July 2008)
For IEEE1355, you could visit
"IEEE 1355-1995 Heterogeneous InterConnect (Low cost, low latency, scalable serial interconnect for parallel system construction)."