AccelFury
Verification status and evidence
Lifecycle, source access and technical checks answer different questions. Review each result with its configuration and evidence.
Checks are separate
There is no universal maturity ladder across these checks.
| Kind | What it establishes within scope |
|---|---|
| simulation | Specified testbench behavior; no timing closure or physical measurement. |
| synthesis | RTL synthesis for the specified tools and settings; no bitstream implied. |
| implementation | Target build or timing results as explicitly recorded; no functional board test implied. |
| programming | Configuration loaded into a device; no functional input/output measurement implied. |
| hardware_functional | Measured behavior of the stated board and configuration. |
| formal | Enumerated properties under explicit assumptions. |
| application_acceptance | The agreed application-level acceptance criteria for a specific integration. |
How to read results
A positive scoped badge needs passed + reviewed + evidence references, with a checked date and configuration.
- Reported: a source describes a result; this site has not independently reviewed the primary report.
- Unknown: evidence is insufficient to determine the result. Missing evidence is not failure or proof a test was never run.
- Not run: an explicit record says the check was not performed. Not applicable requires a reason.
- Private evidence is not publicly reproducible. Availability on request requires a confirmed delivery process.
Historical af-pdm-rx record
The website source at dad5cf5bde00f4921bd64d079fa9ce672655ed48, dated 2026-05-01, reports 13 Icarus test targets plus selected Tang Primer 20K Dock builds and JTAG programming.
The exact component commit, configurations and primary logs have not been independently reviewed. The record does not establish measured PDM clock, GPIO loopback, microphone capture or long-run hardware behavior. Wrapper-only entries for other boards do not establish qualification.