Efficient analysis of CDC violations in a million gate SoC, part 1
Sanymi Gupta , Aniruddha Gupta & Ankush Sethi (Freescale)
EDN (January 17, 2014)
Configuration of SoC specific logic
There is SoC specific logic (in addition to IPs) which is configured initially through software before the IPs are interacting with each other. A typical case could be as shown below (in Fig. 4). Here, we have a provision to use hardware trigger from timer module to ADC. Clocks of both the module are synchronous. However, if we don’t want to use hardware trigger and want to go only for software trigger for ADC we need to constrain the input of ADC based on configuration of mux select through general purpose register. Suppose the general purpose register is working at clk3 which is asynchronous to clk2 of ADC. The CDC tool will show a violating path from clk3 to clk2 but we can waive this path as we will program initially the select of the mux and then later we will use the ADC. So, this becomes a static signal when it is used.
To read the full article, click here
Related Semiconductor IP
- NPU IP
- JPEG XL Encoder
- I2C Master/Slave Controller Core
- NVMe Validation Test Suite
- Hybrid Memory Cube Verification IP
Related Articles
- Efficient analysis of CDC violations in a million gate SoC, part 2
- Analysis of RDC Paths for a million gate SoC
- U-Sonic: An Open-Source 8-Channel Ultrasound Transmit IP in a 130 nm RISC-V SoC
- Hardware/software design requirements analysis: Part 1 - Laying the ground work
Latest Articles
- Terracotta: Enabling the Adoption of New DRAM Techniques via a Flexible DRAM Interface and Memory Controller
- A Framework for Accelerating Transformer Inference on RISC-V for Edge AI
- An Interleaved Parallel Dependent Quantization Hardware Architecture for H.266/VVC
- A Formal Security Analysis of CAN XL
- A Secure dToF LiDAR SoC with Dual-Domain Fingerprinting and Event-Driven AFE Circuit Achieving Sensor-Level Attack Resilience