Find open IP and its integration resources
Filter these twenty open-core records to find repository evidence relevant to your integration task, then inspect the pinned source before selecting a core. The finder covers interface, licence, collateral type and language; it does not rank designs or certify that they will work in your SoC. An unverified field means this audit did not establish the answer, not that the repository lacks it.
Narrow the records to a concrete task
Choose an interface family when the surrounding interconnect is fixed. Add a language filter if it constrains the toolchain, and a collateral filter when you need an example testbench, driver or register description. Filters combine: a zero-result view means this small audited set has no row matching the selected labels, not that no suitable open IP exists.
The plain table remains available when scripts do not run. Outbound repository links open in a new tab. The finder has no upload field and does not save selections or send them to a service. Reset restores the full inventory.
Follow the evidence to the selected revision
Each row identifies a core and a pinned commit1. Follow its evidence to distinguish an interface description from a verified integration test, or a driver directory from software that has been run in your environment. Two cores can share a repository; the table does not treat that as independent project evidence.
The integration evidence page explains the recorded fields. Download the JSON or CSV, with the method, for an inspectable snapshot. Original compilation data is CC BY 4.0; each upstream project retains its own licence.
Not covered on this page
- Running, synthesizing or securing any listed core.
- Ranking maintainers or predicting integration effort.
- Resolving licence obligations for a particular use.
Sources
Code on this page is original and MIT licensed.
How we test: methodology. Found a mistake? Corrections.