#-----------------------------------------------------------------------------
# When constraining asynchronous clock domain paths, it is sometimes desired
# to limit the maximum delay between the two clock domains. Because the clock
# domains are asynchronous, the timing relationship between the two clock
# signals is not known, and should not be included in delay calculations. for
# these paths, the FROM-TO DATAPATHONLY constraint can be used.
#
# An example design situation is shown below:
#
#                             -----                      -----
#                             |REG|===Asynch Data Path===|REG|
#                             |   |                      |   |
#                             --^--                      --^--
#  O---WriteClk-----------------|                          |
#                                                          |
#  O---ReadClk----------------------------------------------
#
#-----------------------------------------------------------------------------

# Defining the Asynchronous Domain Path Timing Groups
# NET <clock_net> TNM_NET = "<clock_net_timegroup>";
NET "WriteClk" TNM_NET = "WriteClkGrp";
NET "ReadClk" TNM_NET = "ReadClkGrp";

# TIMESPEC <TS_name> = FROM <group1> TO <group2> <time> <units> DATAPATHONLY;
TIMESPEC TS_AsynchPath = FROM WriteClkGrp TO ReadClkGrp 10 ns DATAPATHONLY;