Rotten to the Core — Part 2: Soft and Vanilla or Hard and Cryptic?
byDr. Barry Henderson
Introduction
In Part 1 of my article about IP core development, I explored the basic ideas and processes involved in selecting an IP core vendor. We looked into how to reduce risk, how to write the Lore (the requirements specification) that spells out all the major technical details required to design the core, and how to pick a reliable developer. Part 2 now takes a look under the hood, by which I mean that now we want to explore how a core is developed. This includes aspects of responsibility, the various types of core deliverables, verification environments, and steps to take to verify what you get, and how to stay on track once a project is under way.
Read more....Related Semiconductor IP
Related Articles
- Interstellar: Fully Partitioned and Efficient Security Monitoring Hardware Near a Processor Core for Protecting Systems against Attacks on Privileged Software
- The Hitchhiker's Guide to Programming and Optimizing CXL-Based Heterogeneous Systems
- How to design secure SoCs, Part V: Data Protection and Encryption
- The Growing Imperative Of Hardware Security Assurance In IP And SoC Design
Latest Articles
- LLM Agent-Based Design of RISC-V CPUs with FPGA-in-the-Loop Evaluation
- Automated Multi-Line Bug Repair Using Model Checker Aided LLMs: A Case Study on RISC-V Processors
- Cryogenic Recharacterization of a Commercial 22 nm FD-SOI Foundry Standard-Cell Library
- A 105 MS/s 4.18 nJ/inference 0.765 mm² Mixed-Signal Streaming ML Engine for Wireless Baseband in 12LP+ FinFET
- Agentic AI for Heterogeneous System Design Across Chip, Scale-Up, and Scale-Out Domains