Pragmatic Formal Verification Methodology for Clock Domain Crossing (CDC)

Aman Kumar, Muhammad Ul Haque Khan, Bijitendra Mittra
4/20/2024
cs.ARcs.AI

No confident code implementation found for this paper.

Abstract

Modern System-on-Chip (SoC) designs are becoming more and more complex due to the technology upscaling. SoC designs often operate on multiple asynchronous clock domains, further adding to the complexity of the overall design. To make the devices power efficient, designers take a Globally-Asynchronous Locally-Synchronous (GALS) approach that creates multiple asynchronous domains. These Clock Domain Crossings (CDC) are prone to metastability effects, and functional verification of such CDC is very important to ensure that no bug escapes. Conventional verification methods, such as register transfer level (RTL) simulations and static timing analysis, are not enough to address these CDC issues, which may lead to verification gaps. Additionally, identifying these CDC-related bugs is very time-consuming and is one of the most common reasons for costly silicon re-spins. This paper is focused on the development of a pragmatic formal verification methodology to minimize the CDC issues by exercising Metastability Injection (MSI) in different CDC paths.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{kumar2024pragmatic,
  title  = {Pragmatic Formal Verification Methodology for Clock Domain Crossing (CDC)},
  author = {Aman Kumar and Muhammad Ul Haque Khan and Bijitendra Mittra},
  year   = {2024},
  eprint = {2406.06533},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2406.06533v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2406.06533.svg)](https://codeofpaper.com/paper/2406.06533)

Discussion