- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
in my design project, I have 2 clock in input: 'ref_clk_i' and 'clock_i'. I set up these clocks with tickle commands create_clock -period 10 [get_ports ref_clk_i] create_clock -period 1 [get_ports clk_i] and after that I clicked 'Update the timing netlist', but this is the warning message I received: warning: the following clock transfers have no clock uncertainty assignment warning: from ref_clk_i (rise) to ref_clk_i (rise) (setup and hold)warning: from clk_i (rise) to ref_clk_i (rise) (setup and hold)
warning: from clk_i (fall) to ref_clk_i (rise) (setup and hold) Where am I going wrong? Thanks to all.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
--- Quote Start --- Hi all, in my design project, I have 2 clock in input: 'ref_clk_i' and 'clock_i'. I set up these clocks with tickle commands create_clock -period 10 [get_ports ref_clk_i] create_clock -period 1 [get_ports clk_i] and after that I clicked 'Update the timing netlist', but this is the warning message I received: warning: the following clock transfers have no clock uncertainty assignment warning: from ref_clk_i (rise) to ref_clk_i (rise) (setup and hold)
warning: from clk_i (rise) to ref_clk_i (rise) (setup and hold)
warning: from clk_i (fall) to ref_clk_i (rise) (setup and hold) Where am I going wrong? Thanks to all. --- Quote End --- Hi, nothing goes wrong. You can use the uncertainty assignment to define the "jitter" of your clock, means that your clock is not absolute stable. The assignment is taken into account for timing analysis. If your clock is stable you don't need to set this assignment. Kind regards GPK
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page