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
- Power-OK Monitor
- RISC-V-Based, Open Source AI Accelerator for the Edge
- Securyzr™ neo Core Platform
- 112G Multi-SerDes
- SHA3 Cryptographic Hash Cores
Related White Papers
- Efficient analysis of CDC violations in a million gate SoC, part 2
- Analysis of RDC Paths for a million gate SoC
- Internal JTAG - A cutting-edge solution for embedded instrument testing in SoC: Part 1
- 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
Latest White Papers
- 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
- AI in VLSI Physical Design: Opportunities and Challenges
- cMPI: Using CXL Memory Sharing for MPI One-Sided and Two-Sided Inter-Node Communications