zcy
/
pluto_hdl_adi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
pluto_hdl_adi/library/xilinx/common/up_clock_mon_constr.xdc

8 lines
693 B
Plaintext
Raw Normal View History

ad_axi_ip_constr: Split up this constraint file into separate files For experimentation, to solve a constraint scoping issue, split up the ad_axi_ip_constraint file into separate constraints file, in function of there parent module.
2017-03-29 15:31:40 +00:00
up_clock_mon: Remove extra hold register Currently the clock monitor features a hold register in the monitored clock domain. This old register is used to store a instantaneous copy of the counter register. The value in the old register is then transferred to the monitoring domain. Since the counter is continuously counting it is not possible to directly transfer it since that might result in inconsistent data. Instead stop the counter and hold the registers stable for a duration that is long enough for the monitoring domain to correctly capture the value. Once the value has been transferred the counter is reset and restarted for the next iteration. This allows to eliminate the hold register, which slightly reduces utilization. The externally visible behaviour is identical before and after the patch. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2017-05-16 13:52:59 +00:00
set_property ASYNC_REG true [get_cells -hier -filter {name =~ *up_count_running_m*}]
set_property ASYNC_REG true [get_cells -hier -filter {name =~ *d_count_run_m*}]
ad_axi_ip_constr: Split up this constraint file into separate files For experimentation, to solve a constraint scoping issue, split up the ad_axi_ip_constraint file into separate constraints file, in function of there parent module.
2017-03-29 15:31:40 +00:00
up_clock_mon: Remove extra hold register Currently the clock monitor features a hold register in the monitored clock domain. This old register is used to store a instantaneous copy of the counter register. The value in the old register is then transferred to the monitoring domain. Since the counter is continuously counting it is not possible to directly transfer it since that might result in inconsistent data. Instead stop the counter and hold the registers stable for a duration that is long enough for the monitoring domain to correctly capture the value. Once the value has been transferred the counter is reset and restarted for the next iteration. This allows to eliminate the hold register, which slightly reduces utilization. The externally visible behaviour is identical before and after the patch. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2017-05-16 13:52:59 +00:00
set_false_path -from [get_cells -hier -filter {name =~ *d_count_run_m3_reg && IS_SEQUENTIAL}] -to [get_cells -hier -filter {name =~ *up_count_running_m1_reg && IS_SEQUENTIAL}]
set_false_path -from [get_cells -hier -filter {name =~ *up_count_run_reg && IS_SEQUENTIAL}] -to [get_cells -hier -filter {name =~ *d_count_run_m1_reg && IS_SEQUENTIAL}]
set_false_path -from [get_cells -hier -filter {name =~ *d_count* && IS_SEQUENTIAL}] -to [get_cells -hier -filter {name =~ *up_d_count* && IS_SEQUENTIAL}]