blob: b686c93b2e347b741ea5824831ce79cfa8b3c9ac (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
+++
title = "Timing constraints"
author = "Yann Herklotz"
tags = []
categories = []
backlinks = ["1c2a2a"]
forwardlinks = ["3c3", "1c2a2c"]
zettelid = "1c2a2b"
+++
Relative timing constraints
: These are relative timing constraints for IO interaction, which is
probably not that needed for Vericert ([\#3c3]). For example, these
can be used to have a specific amount of cycles in between
operations.
Latency constraint
: This is used to specify the maximum latency for a subgraph in the
CDFG. Not sure when this would be useful in practice.
Cycle time constraint
: This is to limit the maximum combinational delay within a clock
cycle. This will basically implement operation chaining as long as
the operations take less time than the maximum combinational delay.
[\#3c3]: /zettel/3c3
|
