This is a template/example, not a standalone core.
P2M2-M3 templateManually reviewedgithub
AccelFury core-template
Шаблон production-style FPGA IP: manifest, registry, board/toolchain scaffolding, SPDX checks, separated licenses and release checklist.
Primary risk
How to read riskThe risk banner compresses license clarity and review state into a short verdict. Integration decisions still need tests, synthesis, and board evidence.Engineering review is still required before integrationHDL/docs/tests/examples still need manual review.
License needs reviewManually reviewed
Warnings
2Generated projects require separate review.
Purpose and boundaries
Шаблон production-style FPGA IP: manifest, registry, board/toolchain scaffolding, SPDX checks, separated licenses and release checklist.
Core kind and readiness
Readiness focusIf the status is not yet reproduced, close license, tests, and board-level evidence gaps first. The fields below are for quick scope checking.Core kind
generatorRust/SystemVerilog/TypeScript
Interfaces / buses / flow
unknownVerilator
Still missing before production
2- No reproducible tests or CI smoke are confirmed yet.
- There is no board-level evidence with real constraints/report data yet.
Scores
What scores meanEach scale is independent. High usefulness does not cancel a license blocker, and high confidence does not replace board evidence.Quality42
Usefulness36
Integration70
Verification18
Docs62
License48
Beginner42
Professional44
RAG78
Confidence20
Engineering signals
Signals legendSignals show whether useful engineering artefacts are visible. "Yes" does not imply completeness, and "No" often means missing evidence rather than impossible support.TestsTests: current metadata says No.
CICI: current metadata says No.
FormalFormal: current metadata says No.
DocsDocs: current metadata says Yes.
FuseSoCFuseSoC: current metadata says No.
Board demoBoard demo: current metadata says No.
Open flowOpen flow: current metadata says No.
CommercialCommercial: current metadata says Review.
License matrix
Why split by scopeHDL, docs, tests, and generated artifacts can carry different terms. Commercial use is split out so each card does not repeat the same prose.HDLCERN-OHL-S-2.0 + AGPL + CC-BY-SA
DocumentationCERN-OHL-S-2.0 + AGPL + CC-BY-SA
TestsUnknown
ExamplesUnknown
ArtifactsUnknown
Commercial useManual review required
Board compatibility
Compatibility is still unknownSynthesis/implementation evidence and reproducible board reports are still needed.
Evidence matrix
How to read evidenceEach group only shows confirmed links. The confidence floor is a lower trust bound, not an absolute verdict.Local verification
1- Try a synthesis smoke run with: Verilator.