{'fraction_non_alphanumeric': 0.015174506828528073, 'fraction_numerical': 0.0, 'mean_word_length': 5.168224299065421, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Clock Domain Crossing Verification Challenges

Clock Domain crossing is one of the critical aspects of chip design. As the technology node shrink, more IPs can be squeezed into single chip, the chip architecture complexity also increases with more features included. Hence, clock domains crossing probability also increase as more clocks domains co-exists within single chip. The need of clock domain crossing verification also increases and no longer enough to be simple design review and verification. The intend of this paper is to provide an overview of clock domain crossing verification challenges and watchouts. Hopefully it will benefit the community.