Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| asic:timing:constraints [2026/06/14 13:25] – [Timing forks] rajit | asic:timing:constraints [2026/06/14 13:27] (current) – rajit |
|---|
| |
| Depending on the asynchronous circuit family used, the correct operation of a design may require certain timing constraints to be satisfied. ACT provides a mechanism to specify these timing constraints, and Cyclone can check if the constraints are in fact satisfied using delay information from the timing ''.lib'' file and extracted parasitic capacitance/resistance values from an industry standard ''.spef'' file. | Depending on the asynchronous circuit family used, the correct operation of a design may require certain timing constraints to be satisfied. ACT provides a mechanism to specify these timing constraints, and Cyclone can check if the constraints are in fact satisfied using delay information from the timing ''.lib'' file and extracted parasitic capacitance/resistance values from an industry standard ''.spef'' file. |
| |
| ===== Timing forks ===== | |
| |
| |
| Constraints are specified using timing forks. Timing forks can be used to specify a wide range of timing constraints; in particular, they can be used to specify relative timing constraints commonly used in asynchronous circuits. They are general enough to be able to specify setup and hold time constraints in clocked circuits as well. Details on how timing forks are specified can be found in the description of the ''spec'' [[language:langs:spec#timing_constraints|body]]. | Constraints are specified using timing forks. Timing forks can be used to specify a wide range of timing constraints; in particular, they can be used to specify relative timing constraints commonly used in asynchronous circuits. They are general enough to be able to specify setup and hold time constraints in clocked circuits as well. Details on how timing forks are specified can be found in the description of the ''spec'' [[language:langs:spec#timing_constraints|body]]. |
| </code> | </code> |
| Here, the paths considered from ''a+'' to ''b-'' must have exactly one tick on them, while the paths from ''a+'' to ''c+'' have no ticks on them. (The asterisk can appear on ''b'', ''c'', or both.) | Here, the paths considered from ''a+'' to ''b-'' must have exactly one tick on them, while the paths from ''a+'' to ''c+'' have no ticks on them. (The asterisk can appear on ''b'', ''c'', or both.) |
| |
| ==== Ticked edges ==== | |
| |
| ==== Isochronic forks ==== | |
| |
| |
| |