gating DCM output clock until LOCKED?

longb · ‎06-09-2009

I want to gate the deskewed DCM clock output until the DCM is locked. What is the recommended way of doing this?

Looking at Figure 2-13 on page 78 of the Virtex-5 user guide, I am guessing that I can connect a BUFGCE to the CLK0 output of the DCM, with the DCM LOCKED output controlling the CE input of the BUFGCE. (The BUFGCE would be replacing the BUFGMUX in the figure, and I would keep a BUFG in the DCM feedback loop.)

Is this correct? I tried instanting this structure in a Verilog design, but Synplify Pro didn't seem to infer the derived clock after the BUFGCE correctly...

Thanks.

dcm_bufgce

Message Edited by longb on 06-09-2009 05:21 PM

bobster_the_lobster · ‎07-15-2008

As a general rule you wouldn’t do that, there are exceptions to the rule, but not many.

Instead use an enable on you synchronous design and then use the locked signal to switch it on.

I’ve also used the locked signal to set a counter, then counted X pulses to set an enable, this gives you a variable start point..

Bobster

jprovidenza · ‎08-30-2007

Bobster -

Good advice. I've used the LOCKED signal to generate a reset signal instead of an enable.

Gating the clock is asking for problems.

John Providenza

longb · ‎06-09-2009

Thanks for the suggestions, but I can't use a synchronous clock enable because I am prototyping a soft core (ASIC code) whose code I can't easily change. I also can't keep reset asserted until the DCM locks, because in this application the input clock to the DCM can be stopped for a long period of time and started up again without a reset. (I also need a circuit that resets the DCM whenever the input clock is stopped and restarted.)

The BUFGCE is supposed to guarantee that that the output clock is glitchless, so why is this method not recommended?