URL
https://opencores.org/ocsvn/bluespec-h264/bluespec-h264/trunk
Go to most recent revision |
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
32 |
jamey.hick |
#=========================================================================
|
2 |
|
|
# Constraints file
|
3 |
|
|
#-------------------------------------------------------------------------
|
4 |
|
|
# $Id: par.sdc,v 1.1 2008-06-26 17:58:43 jamey.hicks Exp $
|
5 |
|
|
#
|
6 |
|
|
# This file contains various constraints for your chip including the
|
7 |
|
|
# target clock period, the capacitive load of output pins, and any
|
8 |
|
|
# input/output delay constraints.
|
9 |
|
|
#
|
10 |
|
|
|
11 |
|
|
# This constraint sets the target clock period for the chip in
|
12 |
|
|
# nanoseconds. Note that the first parameter is the name of the clock
|
13 |
|
|
# signal in your verlog design. If you called it something different than
|
14 |
|
|
# clk you will need to change this. You should set this constraint
|
15 |
|
|
# carefully. If the period is unrealistically small then the tools will
|
16 |
|
|
# spend forever trying to meet timing and ultimately fail. If the period
|
17 |
|
|
# is too large the tools will have no trouble but you will get a very
|
18 |
|
|
# conservative implementation.
|
19 |
|
|
|
20 |
|
|
create_clock CLK -name ideal_clock1 -period 8.0
|
21 |
|
|
|
22 |
|
|
# This constrainst sets the load capacitance in picofarads of the
|
23 |
|
|
# output pins of your design. 4fF is reasonable if your design is
|
24 |
|
|
# driving another block of on-chip logic.
|
25 |
|
|
|
26 |
|
|
set_load -pin_load 0.004 [all_outputs]
|
27 |
|
|
|
28 |
|
|
# Encounter doesn't seem to have its own way to specify dont_touch
|
29 |
|
|
# so we must do it in the SDC file
|
30 |
|
|
|
31 |
|
|
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.