More IP

ASIL-B Counting Bloom Filter

bloomfilter is a synthesizable, ASIL-B counting Bloom filter soft-IP: a compact,

Request this IP →Browse the catalog

ASIL-B

target

90.90%

SPFM

90.00%

LFM

PASS

FMEDA

24.6K

gates

0.1.0

version

The deliverable

What you’re licensing

bloomfilter is a synthesizable, ASIL-B counting Bloom filter soft-IP: a compact, 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.

bloom_filter is a synthesizable, ASIL-B counting Bloom filter soft-IP: a compact, self-checking accelerator for approximate set membership with deletion support.

Key Features

Insert / query / delete (counting)
M saturating counters, k hashes
Bounded false-positive, zero false-negative
Deletable (vs classic Bloom)
Config parity + FSM lockstep (ASIL-B)

Standards & Compliance

Generic (counting Bloom filter); ISO 26262 ASIL-B SEooC overlay

Functional Safety

ASIL-B (SEooC) · SPFM 90.90% · LFM 90.00% · PASS

ISO 26262:2018 · FMEDA available · Safety Manual included

Register Map

Offset	Register	Description
`0x00`	CTRL	RW [0]=CLEAR (self-clearing; sweeps the whole table to empty)
`0x04`	STATUS	RO [0]=BUSY, [1]=OP_DONE(sticky), [2]=ERR_VALID, [6:3]=ERR_CODE
`0x08`	OCCUPANCY	RO running net insert count since reset/clear (fill estimate, saturating)
`0x0C`	SEED0	RW [31:0] multiply-shift constant A1 for base hash h1 (odd recommended)
`0x10`	SEED1	RW [31:0] multiply-shift constant A2 for base hash h2 (forced odd internally)

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

Getting Started

// Minimal instantiation
bloom_filter #(
  .ADDR_W(6)
) u_bloom_filter (
  .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 specialized datapath and acceleration needs across the portfolio.

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 ASIL-B Counting Bloom Filter?

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