← All IP · the catalog
Serial, Networking & Storage

SPI Slave Controller

A synthesizable SPI slave (device) soft-IP — the counterpart to ip/spimaster.

Request this IP →Browse the catalog
ASIL-B
target
91.50%
SPFM
89.62%
LFM
PASS
FMEDA
384
gates
1.0.0
version
The deliverable

What you’re licensing

A synthesizable SPI slave (device) soft-IP — the counterpart to ip/spimaster. 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.

A synthesizable SPI slave (device) soft-IP — the counterpart to ip/spi_master. An external SPI master drives sclk/mosi/cs_n, asynchronous to the host clock; this IP synchronizes them, frames each transfer on chip-select, and shifts data in/out via APB4 TXDATA/RXDATA registers, supporting all four CPOL/CPHA modes.

Key Features

Standards & Compliance

Motorola/Freescale SPI protocol (4-wire, modes 0–3, CPOL/CPHA); ISO 26262 ASIL-B SEooC (SPFM 91.50%, LFM 89.62%, PMHF 6.15×10⁻¹⁰/h)

Functional Safety

ASIL-B (SEooC) · SPFM 91.50% · LFM 89.62% · PASS

ISO 26262:2018 · FMEDA available · Safety Manual included

Register Map

OffsetRegisterDescription
0x00CTRL[0]=EN [1]=CPOL [2]=CPHA
0x04STATUS[0]=RX_READY [1]=OVERRUN(W1C) [2]=CS_ACTIVE
0x08TXDATA0x0C RXDATA (read clears RX_READY) 0x10 IER [0]=RX_IE

Getting Started

// Minimal instantiation
spi_slave #(
  .ADDR_W(6)
) u_spi_slave (
  .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 in-vehicle networks, industrial gateways, and sensor/actuator links where a bus controller has to carry its own safety argument.

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 SPI Slave Controller?

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