CHI Interconnect & Coherency

AXI4-to-CHI Coherent RN-F Bridge

Catalog MC-3 · v0.1.0 · ASIL-B SEooC

Request this IP →Browse the catalog

ASIL-B

target

90.30%

SPFM

88.99%

LFM

PASS

FMEDA

5.0K

gates

0.1.0

version

The deliverable

What you’re licensing

Catalog MC-3 · v0.1.0 · ASIL-B SEooC 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.

Catalog #MC-3 · v0.1.0 · ASIL-B SEooC

The coherent tier of the AXI-to-CHI bridge family (pairs with the shipped tl_c_to_chi = TL-C → CHI): an AXI4 slave front-end that drives the CHI Request Node channels — request/data as axi_to_chi does, plus the snoop-response pair (RXSNP → TXRSP) that turns the bridge into a full RN-F.

Key Features

Coherent CHI RN-F requests: CTRL.COH selects ReadUnique/WriteUnique (coherent) over ReadNoSnp/WriteNoSnpFull (non-coherent) — the same FSM and datapath serve both personalities
Snoop-response channel (chi_rxsnp_/chi_txrsp_): accepts an RXSNP whenever COH=1, even while the bridge’s own request is outstanding, and answers unconditionally with SnpResp(I) (opcode 0x1) — a non-caching RN-F
One CHI request per AXI beat (DATA_W=256b default); a burst re-issues per beat, address advancing by DATA_W/8
CHI RespErr on a read/write completion sticky-latches and reports back as AXI SLVERR on B/R (err_code 3)
Per-transaction watchdog (TIMEOUT_CYCLES, default 1024) bounds a hung CHI response (err_code 4)
ASIL-B config/address even parity (err_code 1) and inline SECDED on the held read-data line, single-bit auto-correct/double-bit detect (err_code 2)
Two independent complementary-redundant FSM lockstep shadows — command sequencer and snoop responder — both aggregated to err_code 9; catalog FMEDA: SPFM 90.30%, LFM 88.99%, PMHF 9.76×10⁻⁹/h, PASS ASIL-B

Standards & Compliance

Arm AMBA 5 CHI (Request Node); AMBA AXI4 (slave, INCR bursts); ISO 26262 ASIL-B SEooC (SPFM 90.30%, LFM 88.99%, PMHF 9.76×10⁻⁹/h)

Functional Safety

ASIL-B (SEooC) · SPFM 90.30% · LFM 88.99% · PASS

ISO 26262:2018 · FMEDA available · Safety Manual included

Register Map

Offset	Register	Description
`0x00`	CTRL	RW [0]=EN (accept AXI transactions) [1]=COH (coherent mode: ReadUnique/WriteUnique)
`0x0C`	STATUS	RO [7:0]=FSM state [11:8]=err_code [12]=err_valid

Getting Started

// Minimal instantiation
axi_to_chi_coh #(
  .ADDR_W(6)
) u_axi_to_chi_coh (
  .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 multi-core compute clusters that need cache coherency with a defensible ordering proof.

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 AXI4-to-CHI Coherent RN-F Bridge?

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