on-demand webinar

RDC Overview and Questa RDC Methodology

Addressing your Reset Domain Crossing (RDC) challenges

Estimated Watching Time: 71 minutes

Share

RDC Overview & Questa RDC Methodology

Modern SoCs comprises of many design blocks with different functionalities and need different reset controls (global/local) for each blocks. Thus these blocks have multiple asynchronous resets. Asynchronous resets help these blocks/systems to clear faults and recover to a good state. Having local control to resets initialize only faulty logic and other logic remains functional. Interaction between multiple asynchronous resets may cause chip failure due to RDC issues introducing meta-stability in the design.

Catch true RDC issues

This web seminar will give you an overview of Reset Domain Crossing problem and methods to address it. Will also talk about Questa-RDC solution, how it catches true RDC issues and what is our proposed methodology of RDC flow to filter noise and have better QoR. It will cover the abstract flow support, we have for RDC analysis, which is quite useful for big Subsystems and SoC designs in today’s era.

What You Will Learn:

  • Basics of Reset Domain Crossing issues
  • How to catch them and fix early in the design cycle by either using existing reset architecture or by adding appropriate isolation/synchronizer
  • Learn Questa RDC solution and methodology to catch and address these issues

Meet the speaker

Siemens EDA

Atul Sharma

Product Engineer

Atul Sharma is a Product Engineer of the Questa Static products in Design Verification Technology Division for Siemens EDA and primarily responsible for CDC, RDC, SignOff CDC and Lint products. He holds a Bachelor of Engineer degree in Electronics and Communication Engineering from Engineering College Ajmer, Rajasthan. Started his career with Design and Verification Engineer and later moved to EDA domain. With 13 years of total experience, he has spent over a decade in customer facing role to solve Static Verification issues (CDC, Lint, Power Estimation/Reduction & Power Verification) and to create customer methodologies, use models for multiple EDA products.

Related resources