Basics of multi-cycle & false paths
Nitin Singh, Neha Agarwal,Arjun Pal Chowdhury (Freescale Semiconductor)
 EDN (August 07, 2014)
One of the significant challenges to RTL designers is to identify complete timing exceptions upfront. This becomes an iterative process in complicated designs where additional timing exceptions are identified based upon critical path or failing path analysis from timing reports. This approach leaves a significant number of timing paths which may not be real, but these never get identified, since they may not come up in the critical path report. However, synthesis and timing tools will continue to expend resources optimizing these paths when it is not needed. At the same time, it can also impact area and power consumption of the device.
The intent of this document is to provide examples of false and multi cycle path exceptions that are easily missed by even experienced designers, and are identified through iterations on timing reports.
To read the full article, click here
Related Semiconductor IP
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
 - ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
 - MIPI SoundWire I3S Peripheral IP
 - ML-DSA Digital Signature Engine
 - P1619 / 802.1ae (MACSec) GCM/XTS/CBC-AES Core
 
Related White Papers
- Basics of SRAM PUF and how to deploy it for IoT security
 - Real-Time ESD Monitoring and Control in Semiconductor Manufacturing Environments With Silicon Chip of ESD Event Detection
 - DisplayPort 2025: Navigating the Next Wave of Display Innovation
 - Data Movement Is the Energy Bottleneck of Today’s SoCs
 
Latest White Papers
- FeNN-DMA: A RISC-V SoC for SNN acceleration
 - Multimodal Chip Physical Design Engineer Assistant
 - Attack on a PUF-based Secure Binary Neural Network
 - BBOPlace-Bench: Benchmarking Black-Box Optimization for Chip Placement
 - FD-SOI: A Cyber-Resilient Substrate Against Laser Fault Injection—The Future Platform for Secure Automotive Electronics