Debunking myths about analog IP at 28 nm
Manuel Mota, Synopsys
12/3/2012 12:37 PM EST
The economics of system-on-chip development are objective and well understood. Industry-wide trends set the stage for integrating more functions into a SoC, which then drives the scaling down of process technology nodes. In the resulting product, all of the previous product’s functionality is implemented while more functional blocks are added to build increasingly complex functionality. This trend is not questioned - it is an axiom.
Register transfer logic (RTL) is agnostic to the process technology node, so porting digital functionality is not perceived as problematic. However, analog functionality is perceived as more challenging because of its closer dependency on the process characteristics. At each new node, the debate regarding whether or not to integrate analog IP into the SoC is rekindled until the economics validate the integration. Successful mixed-signal SoCs in all previous process technology nodes have demonstrated this cycle despite the persistence of three myths around the economics of analog block implementation in advanced process technologies.
These three myths deserve to be analyzed to better understand why they are erroneous.
To read the full article, click here
Related Semiconductor IP
- oFEC Encoder and Decoder
- NPU IP Core for Edge
- NPU IP Core for Mobile
- NPU IP Core for Data Center
- NPU IP Core for Automotive
Related White Papers
- Density Requirements at 28 nm
- Fully depleted silicon technology to underlie energy-efficient designs at 28 nm and beyond
- Analog IP to protect SoC from side-channel attacks
- Analog and Mixed-Signal Connectivity IP at 65nm and below
Latest White Papers
- Customizing a Large Language Model for VHDL Design of High-Performance Microprocessors
- CFET Beyond 3 nm: SRAM Reliability under Design-Time and Run-Time Variability
- Boosting RISC-V SoC performance for AI and ML applications
- e-GPU: An Open-Source and Configurable RISC-V Graphic Processing Unit for TinyAI Applications
- How to design secure SoCs, Part II: Key Management