timing constraints... again

Hi Christian, I did change the reesolution to a ps, but the timing constraints is in ns, anyway. Still, it doesn't work :( Marija

Hi Marija,

maybe you didn't change your simulation resolution to ps? (it is the -t option, or can also be found in a pull down menu in the ModelSim GUI)

Christian

Another possibility is that your constraints are not actually constraining the signals you think they are. For PERIOD constraints make sure that you place the constraint after the DCM (pin period constraints don't always propagate through DCM or DLL). A good thing to check is the place and route report, which has a clock report and a constraint report at the end. Make sure your PERIOD constraints cover all listed clocks. Look at the constraint report for "N/A" entries which may indicate constraints that cover no paths.

there are two possibility one u may not have apply reset for long enough time ,which will not initialise internal logic properly(this will be case if u r using asyncronous reset) nother possibility is if ur toplevel entity has bidirectional port then dont forget to use pullup/pulldown resistor model in test bench let me know is this help u or not

hi Marija there are two possibility one u may not have apply reset for long enough time ,which will not initialise internal logic properly(this will be case if u r using asyncronous reset) nother possibility is if ur toplevel entity has bidirectional port then dont forget to use pullup/pulldown resistor model in test bench let me know is this help u or not

Kindly post in plain text in future.

-- Jonathan Bromley, Consultant

DOULOS - Developing Design Know-how VHDL, Verilog, SystemC, Perl, Tcl/Tk, Verification, Project Services

Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, BH24 1AW, UK Tel: +44 (0)1425 471223 mail: snipped-for-privacy@doulos.com Fax: +44 (0)1425 471573 Web:

The contents of this message may contain personal views which are not the views of Doulos Ltd., unless specifically stated.