Careful IP Integration Key to First-Pass Silicon
Vamshi Krishna, Sr. FAE & IP Solutions Manager, Open-Silicon
EETimes (4/25/2016 00:00 AM EDT)
Follow these four aspects of IP integration to allow first-pass ASIC silicon when using IP from multiple vendors.
Most ASIC companies today rely on third-party IP in building a custom ASIC/SoC. While ensuring convenience in terms of flexibility, schedule, and cost effectiveness, however, this approach can also present challenges. IP companies, although they adhere to common Industry standards, typically follow different IP development processes, apply different quality benchmarks, and provide different deliverables. The fact that each IP block is unique with respect to its function creates even more differentiation. All this variability makes it difficult to assemble an ASIC using IP from multiple sources and achieve first-pass silicon.
It is possible to achieve first-pass silicon, however, by following a careful integration process. Here are four aspects that ASIC design companies have to consider when using IP blocks from different vendors.
To read the full article, click here
Related Semiconductor IP
- Post-Quantum Digital Signature IP Core
- Compact Embedded RISC-V Processor
- Power-OK Monitor
- RISC-V-Based, Open Source AI Accelerator for the Edge
- Securyzr™ neo Core Platform
Related White Papers
- Mastering Key Technologies to Realize the Dream - M31 IP Integration Services
- The common silicon issues in analog IP integration
- Agile Analog's Approach to Analog IP Design and Quality --- Why "Silicon Proven" is NOT What You Think
- SoCs: Design tools -> Configurability is key to IP integration
Latest White Papers
- DRsam: Detection of Fault-Based Microarchitectural Side-Channel Attacks in RISC-V Using Statistical Preprocessing and Association Rule Mining
- ShuffleV: A Microarchitectural Defense Strategy against Electromagnetic Side-Channel Attacks in Microprocessors
- Practical Considerations of LDPC Decoder Design in Communications Systems
- A Direct Memory Access Controller (DMAC) for Irregular Data Transfers on RISC-V Linux Systems
- A logically correct SoC design isn’t an optimized design