Re: Counter clocks on both edges sometimes, but not when different IO pin is used



In this case, the solution is not to clock anything with your muxed
'clocks' since there is nothing that actually needs to be clocked with
those signals. Instead you should mux those input 'clocks' to create
a logic signal that you then synchronize to your FPGA's clock

I would probably take it a step further and synchronise the two 'clocks' to
the FPGA clock at the IO then select which of the two synchronised inputs is
used as the enable for the counter.

Generalising....

Mr CRC, FPGAs and the tools are designed to guarantee that the output of
one register clocked with one clock will get to the input of any other
register clocked with the same clock (as long as the build meets timing).
This is the beauty of the devices, you don't need to worry about timing,
just functionality.

Once you start introducing asynchronous clock transfers guaranteeing what happens
between them is difficult to constrain, and for the tools to analyse. This is
what needs to be carefully handled in your design.

It is easiest to design, constrain, guarantee meeting timing and so get
guaranteed functional devices if you keep the number of clocks to a minimum.

Preferably 1 (though this is rarely possible).



Nial.


.



Relevant Pages

  • Re: ISE software bug???
    ... The design & report files attached below. ... TIMING REPORT ... Add Generic Clock Buffer: 8 ...
    (comp.arch.fpga)
  • Re: Spartan 3 clock to output tristate timing
    ... I'm a stickler for well defined I/O constraints so I see shoddy engineering on the part of the FPGA group, ... The Timing Analyzer within the Xilinx tool suite has a section at the end that summarizes data input setup and hold times as well as clock-to-out for all the various signals. ... I believe the clock and clock edge are included as well. ... As long as the design doesn't budge, ...
    (comp.arch.fpga)
  • Please HELP: timing problems on Virtex-4FX
    ... In my design, I need to use DDR2 and the APU ... complains that timing constraints are not met for the DDR2 clocks. ... DCMs to make the 266 MHz CPU clock. ...
    (comp.arch.fpga)
  • Re: regarding the post PnR timing simulation.....
    ... Regarding the timing violation. ... quality of the clock is essential, for instance jitter, duty cycle, phase ... This is all what I can guess without knowing your design. ...
    (comp.arch.fpga)
  • Spartan 3 clock to output tristate timing
    ... I've got a problem at work where the FPGA group is at war with the ... designed the board although there was not a lot of original design. ... proper bus timing analysis and I need the data on the FPGA. ... rather than the other clock being provided to the FPGA. ...
    (comp.arch.fpga)