Warning: OPMODE Input Warning : The OPMODE xx with CARRYINSEL 000 to DSP48E1 instance is invalid

csim、综合均与通过。在cosim是遇到大量以下warning：
Warning: OPMODE Input Warning : The OPMODE 011XX11 with CARRYINSEL 000 to DSP48E1 instance is invalid.
导致仿真很慢，无法完成。
以下是收集到的解决方案：

1

I have passed both C simulation and C synthesis successfully for my code. However, during the co-simulation, it isn’t finished with the following two types of warnings.

Warning: OPMODE Input Warning : The OPMODE 0110X0X with CARRYINSEL 000 to DSP48E1 instance is invalid.

Through waveform observation, the input is always zero and the output is always a fixed constant
You can change the “cosim_design” in script.tcl to “cosim_design -disable_depchk” to skip this check.
Yes, these can be safely ignored.

尝试这种方法
手动修改script.tcl，执行cosim时，会被删掉我们添加的 -disable_depchk。通过GUI添加的方式没有找到。

2

https://forums.xilinx.com/t5/High-Level-Synthesis-HLS/Warning-OPMODE-Input-Warning-The-OPMODE-0110X0X-with-CARRYINSEL/m-p/939048

You can change the “cosim_design” in script.tcl to “cosim_design -disable_depchk” to skip this check.

Origin of this message is uninitialized value of input (control) signal of DSP component. Such warnings can be ignored at simulation time = 0 ns or few clock cycles later. If this message appear through and through then it’s error which must be fixed

3

• OPMODE Input Warning “The OPMODE 0110X0X with CARRYINSEL 000 to DSP48E1 instance is invalid.” is related to a bug in Vivado HLS, as Xilinx confirmed by email (the OPMODE input to the DSP48 slice contains unknown inputs “X”, which are functionally irrelevant, but cause this warning to be displayed). The problem is that this warning slows down co-simulation so much that it’s completely unusable (simulation takes days without finishing).
  I suggest you go on with compilation, bitstream generation, and test the implementation on the target.

建议使用其他方式验证