Behavioral Modeling of Clock/Data Recovery
May 1, 2014
Clock/Data recovery (CDR) is a tricky logic to implement correctly. To verify the clock/data recovery logic implemented in designs, the corresponding verification infrastructure needs to be modeled correctly.
This presentation aims to present the various issues faced for modeling CDR behaviorally along with their solutions.
The presentation starts off by explaining the need for CDR in the context of serial interfaces. It then explains how CDR would be done in an ideal scenario. Real issues like Jitter and PPM/Drift are then introduced along with techniques for handling these effects. Finally, a flow chart explains how an accurate behavioral model can be constructed.
Related Semiconductor IP
- MIL-STD-1553 Controller IP
- UFS 5.x Device IP
- UCIe 3.x Controller IP
- Ethernet 800G PCS IP
- CHI to UCIe Bridge IP
Related Blogs
- UEC-LLR: The Future of Loss Recovery in Ethernet for AI and HPC
- TSMC Yields Recovery!
- In search of recovery
- TSMC UMC Lead Semiconductor Recovery - Record Year in 2010
Latest Blogs
- CDM Dependence on Device Capacitance
- What the Cyber Resilience Act means for the future of chip design
- When Your IP Vendor Has Operated 150,000 Base Stations: Introducing Viettel Semiconductor
- Relationship between architecture and validation in system design
- The Post-Quantum Cryptography Mandate: Building Cryptographically Agile Systems for the Quantum Era