Reusing IP across SoCs
How one block serves several chips: configuration, versioning, derivative designs, what to verify again, and the common pitfalls.
Configuration
Most reusable blocks are configurable, so each SoC takes the variant it needs. Every option multiplies what must be verified.
- Keep the list of supported configurations short and named, rather than allowing any combination
- Record which configuration each SoC uses alongside the version
- Generate configuration-dependent files, such as register descriptions and constraints, from one source
- Treat a configuration no other SoC has used as new work, with its own verification
- Functions
- Disciplines
2 more reuse topics for registered members.
Register or sign in to read on
The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.