Questions about sampling vsync signals in different clock domains during Video Synchronization

Source: Internet
Author: User

Today, we have debugged the 4 K (3840x1920) vsync signal (clock at 297 MHz) in the 170 MHz clock domain, and found that the output signal jitter is particularly severe. It was later discovered that this was caused by different clock domains. Signals in the fast clock domain may not be collected when entering the slow clock domain. So I change the high level of a clock to the high level of three clocks, so that the slow clock domain can certainly be collected.

Always @ (posedge CLK or negedge reset_n) begin if (~ Reset_n) Begin rdaddr_req <= 1 'b0; // frame_counters <= 13 'b0; end else if (nvsync_dly1 &&(~ Nvsync) Begin rdaddr_req <= 1 'b1; end else if (nvsync_dly3 &&(~ Nvsync_dly2) rdaddr_req <= 1 'b0; // end

Therefore, be careful when handling cross-Clock Domain numbers !!!

Questions about sampling vsync signals in different clock domains during Video Synchronization

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.