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
- NoC Interconnect IP Generator
- Over-Voltage Lockout (OVLO) IP
- Verification IP for Universal Chiplet Interconnect Express (UCIe) up to 3.0
- UCIe-S (Gen2) Compatible PHY for Standard Package (x16) in TSMC N3P, North/South Orientation
- DSP-Based 112G SerDes
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
- Building the engine behind Arm’s silicon shift
- M31 High-Speed and Long-Channel MIPI C/D-PHY Solution on TSMC N3P/N3C
- Understanding security certification and how analog IP can help
- Embedded Security explained: Secure boot for embedded systems
- World's First Standards-Compliant 112G PHY IP for Linear Optics: A Turning Point for AI Interconnects