Avionics, Space & Mil-Std Networking

ARINC 825 (CANaerospace) Profile Layer

arinc825 is an ARINC 825 (CANaerospace) avionics communication-profile layer for classic CAN 2.0B and CAN-FD networks,

Request this IP →Browse the catalog

ASIL-B

target

91.10%

SPFM

87.83%

LFM

PASS

FMEDA

3.2K

gates

1.0.0

version

The deliverable

What you’re licensing

arinc825 is an ARINC 825 (CANaerospace) avionics communication-profile layer for classic CAN 2.0B and CAN-FD networks, 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 (crypto: bit-exact) testbench and a one-command build, so you can reproduce every claim on day one.

What it is

arinc825 is an ARINC 825 (CANaerospace) avionics communication-profile layer for classic CAN 2.0B and CAN-FD networks, delivered as synthesizable SystemVerilog soft-IP with an APB4-lite control interface and built-in ISO 26262 (ASIL-B) safety instrumentation.

Key Features

29-bit extended-ID decode/encode into ARINC 825 fields — 4-bit PRIO, 11-bit Message-Code/LCC, 6-bit Function-Code-Identifier (bit 5 = server/client NOD/NSD flag), 7-bit source, and a redundancy-channel-id bit — symmetric on TX via a TX_FIELD write-triggered encode
CANaerospace data-field decode (data-type, service-code, message-code from the first 4 payload bytes) with node-id and Message-Code filtering (CFG.NODE_ID / MC_FILT) and an optional node-service-only mode (CTRL.SRV_ONLY)
A/B redundancy management: per-channel freshness down-counters (RED_CFG.FRESH_TO) flag a stale/lost redundant bus as a redundancy-loss timeout (err_code 4, STATUS.CHA_STALE/CHB_STALE), and a redundant duplicate on the other channel is de-duplicated (STATUS.DEDUP_DROP) rather than delivered twice
ID-structure and data-type/service-code plausibility checking rejects a malformed or implausible frame before it is committed to the readback registers (protocol err_code 3)
Even-parity guard over the CTRL/CFG/RED_CFG config-register set (err_code 1) plus a KEEP_ATTR complementary-DMR shadow of the redundancy-management/decode FSM (err_code 9), both aggregated with the safety_monitor self-check (err_code F)
fi_* DFT fault-inject inputs (always present, default 0) prove every mechanism in simulation/DFT: fi_cfg_par, fi_id_struct, fi_plaus, fi_fresh_to, fi_fsm_dmr
MAC-agnostic frame interface — attaches to any classic-CAN or CAN-FD controller’s framed RX/TX ports (the same convention as ip/can_dma), leaving bit-level bus-fault confinement and the external transceiver entirely outside this IP’s boundary

Standards & Compliance

ARINC 825 (CANaerospace avionics CAN profile); ISO 11898-1 CAN 2.0B / CAN-FD datalink (external MAC); ISO 11898-2/3 transceiver (external, board-level); DO-254/ED-80-aligned hardware design-assurance evidence; ISO 26262 ASIL-B SEooC (SPFM 91.10%, LFM 87.83%, PMHF 5.36×10⁻⁹/h)

Functional Safety

ASIL-B (SEooC) · SPFM 91.10% · LFM 87.83% · PASS

ISO 26262-5 FMEDA method (transferable evidence for the RTCA DO-254 assurance case) · FMEDA available · Safety Manual included

Register Map

Offset	Register	Description
`0x00`	CTRL	RW [0]=EN [1]=FILT_EN [2]=RED_EN(redundancy mgmt) [3]=SRV_ONLY(accept node-service only)
`0x04`	CFG	RW [6:0]=NODE_ID [17:7]=MC_FILT (accept this MC when FILT_EN) [18]=MC_FILT_EN
`0x08`	RED_CFG	RW [15:0]=FRESH_TO (per-source freshness/redundancy timeout, clocks; 0=off)
`0x0C`	STATUS	RO [0]=RX_VLD [1]=CHA_STALE [2]=CHB_STALE [3]=DEDUP_DROP [4]=ERR_VALID [8:5]=ERR_CODE
`0x10`	RX_ID	RO [28:0] last-decoded 29-bit extended ID

…4 more registers — see datasheet for the full table.

Getting Started

// Minimal instantiation
arinc825 #(
  .ADDR_W(6)
) u_arinc825 (
  .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 ARINC 825 (CANaerospace) Profile Layer?

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 · sales@circuit-design.space