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
- DeWarp IP
- 6-bit, 12 GSPS Flash ADC - GlobalFoundries 22nm
- LunaNet AFS LDPC Encoder and Decoder IP Core
- ReRAM NVM in DB HiTek 130nm BCD
- UFS 5.0 Host Controller IP
Related Articles
- Interstellar: Fully Partitioned and Efficient Security Monitoring Hardware Near a Processor Core for Protecting Systems against Attacks on Privileged Software
- How to Elevate RRAM and MRAM Design Experience to the Next Level
- NoCs and the transition to multi-die systems using chiplets
- The Hitchhiker's Guide to Programming and Optimizing CXL-Based Heterogeneous Systems
Latest Articles
- VolTune: A Fine-Grained Runtime Voltage Control Architecture for FPGA Systems
- A Lightweight High-Throughput Collective-Capable NoC for Large-Scale ML Accelerators
- Quantifying Uncertainty in FMEDA Safety Metrics: An Error Propagation Approach for Enhanced ASIC Verification
- SoK: From Silicon to Netlist and Beyond Two Decades of Hardware Reverse Engineering Research
- An FPGA-Based SoC Architecture with a RISC-V Controller for Energy-Efficient Temporal-Coding Spiking Neural Networks