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
- RVA23, Multi-cluster, Hypervisor and Android
- 64 bit RISC-V Multicore Processor with 2048-bit VLEN and AMM
- NPU IP Core for Mobile
- RISC-V AI Acceleration Platform - Scalable, standards-aligned soft chiplet IP
- H.264 Decoder
Related White Papers
- Paving the way for the next generation of audio codec for True Wireless Stereo (TWS) applications - PART 5 : Cutting time to market in a safe and timely manner
- Stop-For-Top IP model to replace One-Stop-Shop by 2025... and support the creation of successful Chiplet business
- Semiconductors and software lead the way to sustainability
- Interstellar: Fully Partitioned and Efficient Security Monitoring Hardware Near a Processor Core for Protecting Systems against Attacks on Privileged Software
Latest White Papers
- QiMeng: Fully Automated Hardware and Software Design for Processor Chip
- RISC-V source class riscv_asm_program_gen, the brain behind assembly instruction generator
- Concealable physical unclonable functions using vertical NAND flash memory
- Ramping Up Open-Source RISC-V Cores: Assessing the Energy Efficiency of Superscalar, Out-of-Order Execution
- Transition Fixes in 3nm Multi-Voltage SoC Design