Copyright 1986-2022 Xilinx, Inc. All Rights Reserved. Copyright 2022-2025 Advanced Micro Devices, Inc. All Rights Reserved. --------------------------------------------------------------------------------------------------------------------------------------------- | Tool Version : Vivado v.2025.2 (lin64) Build 6299465 Fri Nov 14 12:34:56 MST 2025 | Date : Sat Nov 21 08:13:39 2026 | Host : System-Product-Name running 64-bit Ubuntu 20.04.6 LTS | Command : report_drc -file top_cve2_ep09_drc_routed.rpt -pb top_cve2_ep09_drc_routed.pb -rpx top_cve2_ep09_drc_routed.rpx | Design : top_cve2_ep09 | Device : xc7a35tfgg484-2 | Speed File : -2 | Design State : Fully Routed --------------------------------------------------------------------------------------------------------------------------------------------- Report DRC Table of Contents ----------------- 1. REPORT SUMMARY 2. REPORT DETAILS 1. REPORT SUMMARY ----------------- Netlist: netlist Floorplan: design_1 Design limits: Ruledeck: default Max checks: Checks found: 76 +-----------+----------+-----------------------------+--------+ | Rule | Severity | Description | Checks | +-----------+----------+-----------------------------+--------+ | CHECK-3 | Warning | Report rule limit reached | 1 | | DPIP-1 | Warning | Input pipelining | 33 | | DPOP-1 | Warning | PREG Output pipelining | 11 | | DPOP-2 | Warning | MREG Output pipelining | 1 | | DPREG-4 | Warning | DSP48E1_PregDynOpmodeZmuxP: | 10 | | REQP-1839 | Warning | RAMB36 async control check | 20 | +-----------+----------+-----------------------------+--------+ 2. REPORT DETAILS ----------------- CHECK-3#1 Warning Report rule limit reached REQP-1839 rule limit reached: 20 violations have been found. Related violations: DPIP-1#1 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#2 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#3 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#4 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#5 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#6 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#7 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#8 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#9 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#10 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#11 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#12 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#13 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#14 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#15 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#16 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#17 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#18 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#19 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#20 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#21 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#22 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#23 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#24 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#25 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#26 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#27 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#28 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#29 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#30 Warning Input pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd input u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#31 Warning Input pipelining DSP u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed input u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed/A[29:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#32 Warning Input pipelining DSP u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed input u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed/B[17:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPIP-1#33 Warning Input pipelining DSP u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed input u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed/C[47:0] is not pipelined. Pipelining DSP48 input will improve performance. Related violations: DPOP-1#1 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#2 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#3 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#4 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#5 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#6 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#7 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#8 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#9 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#10 Warning PREG Output pipelining DSP u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd output u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-1#11 Warning PREG Output pipelining DSP u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed output u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed/P[47:0] is not pipelined (PREG=0). Pipelining the DSP48 output will improve performance and often saves power so it is suggested whenever possible to fully pipeline this function. If this DSP48 function was inferred, it is suggested to describe an additional register stage after this function. If the DSP48 was instantiated in the design, it is suggested to set the PREG attribute to 1. Related violations: DPOP-2#1 Warning MREG Output pipelining DSP u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed multiplier stage u_core/u_cve2_core/ex_block_i/gen_multdiv_fast.multdiv_i/mac_res_signed/P[47:0] is not pipelined (MREG=0). Pipelining the multiplier function will improve performance and will save significant power so it is suggested whenever possible to fully pipeline this function. If this multiplier was inferred, it is suggested to describe an additional register stage after this function. If there is no registered adder/accumulator following the multiply function, two pipeline stages are suggested to allow both the MREG and PREG registers to be used. If the DSP48 was instantiated in the design, it is suggested to set both the MREG and PREG attributes to 1 when performing multiply functions. Related violations: DPREG-4#1 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[0].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#2 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[1].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#3 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[2].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#4 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[3].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#5 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[4].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#6 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[5].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#7 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[6].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#8 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[7].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#9 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[8].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: DPREG-4#10 Warning DSP48E1_PregDynOpmodeZmuxP: The DSP48E1 cell u_core/u_cve2_core/cs_registers_i/gen_cntrs[9].gen_imp.mcounters_variable_i/counter_upd with the given dynamic OPMODE[6:0] connections may lead to an unregistered asynchronous feedback path without the PREG attribute enabled. Please refer to the user guide and if one of the internal P feedback opmodes is possible for this design the PREG attribute must be set to 1, currently set to 0 Related violations: REQP-1839#1 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[17].rf_reg_q_reg[17][4]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#2 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[17].rf_reg_q_reg[17][5]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#3 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[17].rf_reg_q_reg[17][6]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#4 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[17].rf_reg_q_reg[17][7]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#5 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[17].rf_reg_q_reg[17][8]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#6 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[17].rf_reg_q_reg[17][9]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#7 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][0]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#8 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][10]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#9 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][11]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#10 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][12]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#11 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][13]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#12 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][14]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#13 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][15]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#14 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][16]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#15 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][17]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#16 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][18]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#17 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][1]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#18 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][2]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#19 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][3]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: REQP-1839#20 Warning RAMB36 async control check The RAMB36E1 u_ram/mem_reg_0_0 has an input control pin u_ram/mem_reg_0_0/ADDRARDADDR[14] (net: u_ram/alu_adder_result_ex_o[13]) which is driven by a register (u_core/u_cve2_core/register_file_i/g_rf_flops[18].rf_reg_q_reg[18][4]) that has an active asychronous set or reset. This may cause corruption of the memory contents and/or read values when the set/reset is asserted and is not analyzed by the default static timing analysis. It is suggested to eliminate the use of a set/reset to registers driving this RAMB pin or else use a synchronous reset in which the assertion of the reset is timed by default. Related violations: