Available now — real, tested verification collateral, not a roadmap placeholder.
Verification IP is not safety-rated. These are testbench components — no ASIL target, no FMEDA, no IP-XACT, no safety-mechanism interface. They exist to help you verify a design, not to carry a safety argument. The safety soft-IP catalog is over here.
An independent APB4 config master, written clean-room from the register map documented in the catalog’s own led_pwm RTL header comment — not derived from the RTL’s implementation — so it functions as a true second source. Ships with a passive duty/period checker that measures each pwm_out channel’s real high-time and period via edge detection and cross-checks them against the duty/period the TB itself configured, self-re-arming for the free-running waveform, and a self-checking interop TB proving two simultaneously-active channels at different duty ratios, a DUTY=0 boundary case, and a wrong-expectation injection against the catalog’s led_pwm. Covers the 4-channel (R/G/B/W) shared-period/prescaler LED-PWM contract today — mc_pwm (the motor-control PWM variant with complementary outputs and dead-time insertion) is a documented roadmap item, not yet built.
WR/RD task API against the documented CTRL/PRESC/PERIOD/DUTY_x register mapled_pwm: two channels concurrently at different duty ratios (37.5%/75%), a DUTY=0 boundary case, and a wrong-expected-duty injection — all passmc_pwm‘s complementary/dead-time pairs are roadmap, not yet builtGeneric PWM controller verification (no fixed external spec)
Built to lean against these catalog IPs during integration:
Deliverables, the file manifest, and licensing terms are shared under a mutual NDA.
Verification IP is testbench collateral and is deliberately not safety-rated: no ASIL target, no FMEDA, and no IP-XACT descriptor. It carries no functional-safety claim.
circuit-design.space · +1-971-357-1400 · sales@circuit-design.space