System, Safety & Compute

Processor Trace Encoder

RISC-V branch-trace encoder (N-Trace style) with APB4 slave interface and ASIL B safety monitor.

Request this IP →Browse the catalog

ASIL-B

target

100.00%

SPFM

90.00%

LFM

PASS

FMEDA

2.4K

gates

1.0.0

version

The deliverable

What you’re licensing

RISC-V branch-trace encoder (N-Trace style) with APB4 slave interface and ASIL B safety monitor. 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.

Trace Enc — Introduction

    ## What it is

    RISC-V branch-trace encoder (N-Trace style) with APB4 slave interface and ASIL B safety monitor.

Key Features

Execution-trace compression / packetisation
Config-register parity (err_code 1) + safety_monitor
err_clear / err_valid / err_code[3:0] safety ports
APB4 control

Standards & Compliance

ISO 26262 (SEooC)

Functional Safety

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

ISO 26262:2018 · FMEDA available · Safety Manual included

Register Map

Offset	Register	Description
`0x00`	CTRL	[0]=EN [1]=SYNC_REQ (self-clearing) [2]=FIFO_RST (self-clearing)
`0x04`	STATUS	[0]=FIFO_EMPTY [1]=FIFO_FULL [2]=OVERFLOW (sticky, W1C via ISR)
`0x08`	PACKET	(RO) pop one 32-bit packet word (0 when empty)
`0x0C`	COUNT	(RO) number of words currently in the FIFO
`0x10`	IER	[0]=NOTEMPTY_IE [1]=OVF_IE

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

Getting Started

// Minimal instantiation
trace_enc #(
  .ADDR_W(6)
) u_trace_enc (
  .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 the safety backbone of an ASIL SoC — error detection, redundancy, and the fault-reaction path that takes the system to a safe state.

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 Processor Trace Encoder?

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