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
- Chiplet Die-to-Die Interconnect IP Solution
- High speed MACsec Engine 100G/200G/400G/800G/1.6T
- Temperature/Voltage sensors
- AMBA Bus Host to eSPI Controller/Target
- AMBA Bus Host to eSPI Controller
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
- Embedded Security explained: Advanced Encryption Standard (AES)
- Cadence Demonstrates PCIe 8.0 PHY at PCI-SIG DevCon 2026
- Cadence Achieves Successful Silicon Validation of 1st IP Test Chips on Intel 18A
- From Classical CAN and CAN FD to CAN XL: Functional Safety and Security for Next-Generation In-Vehicle Communication
- Accelerating Embedded Memory Performance with 16-bit xSPI PSRAM IP