MIL-STD-1553

An independent MIL-STD-1553B Bus Controller — Manchester II encode/decode, sync-pattern generation, and odd-parity word framing written clean-room from the public MIL-STD-1553B word format, not from our own mil1553 RT’s internal FSM. Verified BC-to-RT (Receive Command with multi-word data capture, APB read-back confirmed) and RT-to-BC (Transmit Command with status + data response, independently Manchester-decoded and parity-checked off the wire) over bus A, plus a passive protocol checker that recomputes parity/sync legality on the RT’s own transmit pins and hard-catches an injected bad-parity fault. RT-to-RT relay is not exercised (no second RT instance in this harness) and dual-redundant bus arbitration is confirmed inert, not working — this v0.1 RTL locks its bus-select to bus A at reset and never re-evaluates it (documented in the IP’s own “Deferred features”), which was verified by showing a command sent only on bus B is correctly ignored.

Key Features

• Independent BC BFM: Manchester II bit-level encode/decode, SEND_COMMAND/SEND_DATA_WORD/RECV_STATUS_WORD/RECV_DATA_WORD task API, plus a SEND_COMMAND_BAD_PARITY injection primitive
• Passive protocol checker watching only the RT’s own bus_o/bus_tx_en pins: independently recomputed parity legality, sync-pattern legality, and a generous response-turnaround bound
• Self-checking interop TB: BC-to-RT receive (2 data words, APB read-back) and RT-to-BC transmit (status + data word, decoded off the wire) both verified over bus A, plus a directed bad-parity injection hard-checked at both the DUT (ignored + flagged) and checker (caught) levels
• Scope today: bus A only (bus B confirmed correctly inert per the RTL’s documented v0.1 limitation, not a working A/B failover); RT-to-RT relay and mode-code actions are roadmap, not yet built

Standards & Compliance

MIL-STD-1553B

Pairs With

Built to lean against these catalog IPs during integration:

• mil1553