Skip to content

Commit ab4c1ea

Browse files
committed
mock-array-big: Tore Ramsland's input
Signed-off-by: Øyvind Harboe <[email protected]>
1 parent c748a53 commit ab4c1ea

File tree

1 file changed

+25
-1
lines changed

1 file changed

+25
-1
lines changed

flow/designs/asap7/mock-array-big/README.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,29 @@ make
3737
Element/constraint.sdc
3838
----------------------
3939

40+
A relatively simple constraint.sdc is adequate for the Element as
41+
timing is exported when the Element macro is made and checked at the
42+
mock-array-big level.
43+
44+
Note that a failure on timing at the Element level is
45+
not a problem, as long as timing is met at the mock-array-big level.
46+
47+
The purpose of the constraint.sdc file at the Element level is to
48+
be able to iterate on the Element during development and work on,
49+
for instance, maximum operating frequency changes in the Verilog,
50+
but also to give the tools some guidance on how to optimize the
51+
macro.
52+
53+
Optimizing Element/constraint.sdc
54+
---------------------------------
55+
56+
Before considering the various strategies to articulate an Element/constraint.sdc
57+
file below, note that no tests have been run to verify that these
58+
different constraint.sdc changes below have any effects on the quality
59+
of results at the mock-array-big level. If there are no substantial
60+
differences in quality of results and timing is met, then the differences
61+
between the strategies below are inconsequential.
62+
4063
A single macro is made for all the elements in the array, though strictly
4164
speaking each macro is unique in that the timing constraints of each element
4265
in the array is different.
@@ -52,7 +75,8 @@ Taking a step back, it is also worth considering what level of detail is
5275
appropriate for the Element's constraint.sdc file.
5376

5477
In the beginning of a project, during exploration, the .sdc file does not
55-
need to be particularly detailed. In fact, details can be counterproductive, as they tend to be inaccurate and cause the tools to spend time solving potential non-issues.
78+
need to be particularly detailed. In fact, details can be counterproductive,
79+
as they tend to be inaccurate and cause the tools to spend time solving potential non-issues.
5680

5781
Consider minimum input delay, which relates to hold times. If the main concern
5882
of architectural exploration is to ensure that the design can operate on a

0 commit comments

Comments
 (0)