UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor zhi_kaan_zhi
Visitor
12,224 Views

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

Jump to solution

Hello, I'm building a large project and I'm using Vivado HLS 2016.1 and my target device Zynq ZC706. When I'm trying to simulate my design with C/RTL Co-Simulation the console keeps showing the following warning:

 

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

Time: 6295685 ns Iteration: 11 Process: /apatb_dev_nonbonded_slow_energy_top/AESL_inst_dev_nonbonded_slow_energy/dev_nonbonded_slow_energy_faddfsub_32ns_32ns_32_4_full_dsp_U65/dev_nonbonded_slow_energy_ap_faddfsub_2_full_dsp_32_u/U0/i_synth/addsub_op/ADDSUB/speed_op/dsp/OP/dsp48e1_body/ALIGN_ADD/DSP2/DSP/prcs_opmode_drc File: C:\Xilinx\Vivado\2016.1\data/vhdl/src/unisims/primitive/DSP48E1.vhd

 

The C/RTL Co-simulation is very slow and I think that the output of this warning in console makes it even slower.

Can anyone help me understand this warning and how will I make it disappear?

 

I've attached a printscreen.

 

Thank you in advance.

 

P.S. I'm simulating my design about 20 hours and the console keeps spamming this warning.

 

printscreen.png

1 Solution

Accepted Solutions
Adventurer
Adventurer
7,048 Views

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

Jump to solution

Yes I think it shows up in both OS. But you can just ignore it. Nobody knows what it really is, but it works.

0 Kudos
31 Replies
Teacher muzaffer
Teacher
12,168 Views

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

Jump to solution
Assuming your C simulation passes, the only conclusion I can draw from your result is that there is something wrong with the code 2016.1 generates which is driving an unknown value into the dsp48 which is the source of your problem.
- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
0 Kudos
Visitor zhi_kaan_zhi
Visitor
12,146 Views

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

Jump to solution

Thank you for your reply. So there is nothing I can do, right?

0 Kudos
Teacher muzaffer
Teacher
12,137 Views

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

Jump to solution
I'd suggest trying your design with a different version of Vivado ie 2015.4 ?
- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
0 Kudos
Visitor zhi_kaan_zhi
Visitor
11,891 Views

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

Jump to solution

I've found a thread in a forum about this warning but I don't know how to fix it.

 

In the reply he suggests the following:

"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.
To remove this warning set initial value for reported signal."

 

Does anyone know how to set this initial value?

 

The thread is the following:

http://www.edaboard.com/thread179587.html

0 Kudos
Visitor xy0
Visitor
8,015 Views

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

Jump to solution

Same thing happens to me here, in Vivado HLS 2016.4.

 

Hope someone give some help or information. Thanks!!!!

0 Kudos
Adventurer
Adventurer
7,849 Views

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

Jump to solution

@zhi_kaan_zhi @xy0 I'm having the same problem here. Did you guys solve this?

 

Thanks!

0 Kudos
Observer delk
Observer
7,618 Views

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

Jump to solution

Exact same problem here on Vivado 2016.4 during co-simulation. Anyone managed to fix that?

 

0 Kudos
Moderator
Moderator
7,607 Views

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

Jump to solution

Hi @delk,

 

Are you using VHDL for cosimulation? If so can you please give it a try with Verilog?

Thanks,
Arpan
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
Observer delk
Observer
7,598 Views

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

Jump to solution
I am using Verilog for cosim, but I'll give it a go with VHDL and report back.
0 Kudos
Observer delk
Observer
6,300 Views

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

Jump to solution

Same warning with VHDL cosim with only difference the iteration is now 13 (was 11-12 in Verilog cosim).

 

Warning: OPMODE Input Warning : The OPMODE 0110X0X with CARRYINSEL  000 to DSP48E1 instance is invalid.
Time: 2280755 ns  Iteration: 13  Process: /apatb_triangulate2D_top/AESL_inst_triangulate2D/grp_insertSite_fu_72/grp_inTriangle_fu_364/grp_ccw_fu_69/grp_triArea_fu_56/triangulate2D_fsubkb_U2/triangulate2D_ap_fsub_2_full_dsp_32_u/U0/i_synth/addsub_op/ADDSUB/speed_op/dsp/OP/dsp48e1_body/ALIGN_ADD/DSP2/DSP/prcs_opmode_drc  File: /wrk/2016.4/nightly/2017_01_23_1756540/data/vhdl/src/unisims/primitive/DSP48E1.vhd

I am really stuck here! Any ideas?

0 Kudos
Visitor aayushntu
Visitor
5,765 Views

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

Jump to solution

Hi,

 

Is this post solved? I am facing this issue with Vivado 2016.4.

I read the suggestion some where that all the variables should be initialized. It allows the co-simulation to pass. However, when I export the IP to Vivado I get faulty results i.e. the IP core does not work as expected. I use chipscope to analyse the results. I suspect the problem is still due to this warning.

0 Kudos
Visitor gaucho253
Visitor
5,645 Views

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

Jump to solution

@aayushntu, I currently have the same warning in my 2016.2 design with the simulation remaining in iterations 11 and 12.  I learned that it is not a critical warning, and the co-simulation is still able to complete if you give it enough time.  

 

My design in particular has pointer inputs with large depth values.  It takes multiple days for co-simulation to complete, but I don't know yet if it is the design's fault or the warning's.  I have not exported the IP to Vivado yet.

0 Kudos
5,454 Views

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

Jump to solution

Hi All,

 

I am facing same issue and I ended up following this link. Those who had same issue and came up with solution, mention the way you fixed it. I used Verilog for co-simulation in Vivado2016.2 and the VHDL code of DSP481 in Vivado/2016.2/SDSoC is being called, from where this Warning is coming up.

 

Any suggestions are highly welcomed.

 

Thanks

Divya

0 Kudos
Visitor gaucho253
Visitor
5,438 Views

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

Jump to solution

divyapraneetha@gmail.com,

 

I receive this warning in 2016.2, but my simulation is still able to complete.  I have not performed a hardware test yet.

0 Kudos
5,435 Views

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

Jump to solution

Hi gaucho,

 

The co-simulation is being on run for 24 hours now. (After looking at your previous post I gave it a try to run longer). Still the same warning is coming up. Any fix you made when your encountered the problem..

 

Thanks

Divya

0 Kudos
Visitor gaucho253
Visitor
5,433 Views

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

Jump to solution

divyapraneetha@gmail.com

 

No, I did not make any change to my design regarding this warning because I don't know what causes it.  I also don't know if my long simulation time is related to this warning or not.  

 

In my top level interface, I have a few AXI master inputs and outputs with depth=5000 each (width of 24-32).  Are you also using deep AXI master ports?

0 Kudos
Visitor manujvk
Visitor
4,337 Views

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

Jump to solution

I'm facing the same problem and cosimulation has been running for more than 24 hrs. Is there any solution to it?

0 Kudos
Participant jehandad
Participant
4,240 Views

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

Jump to solution

Vivado HLS version 2017.2 and the error is still there! 

0 Kudos
Observer angu_sewa
Observer
3,837 Views

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

Jump to solution

Does this warning shows up while working with vivado HLS in Linux OS too??

0 Kudos
Adventurer
Adventurer
7,049 Views

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

Jump to solution

Yes I think it shows up in both OS. But you can just ignore it. Nobody knows what it really is, but it works.

0 Kudos
Explorer
Explorer
2,648 Views

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

Jump to solution

Same issue here with 2017.2 on Linux

 

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

0 Kudos
Visitor lannylian
Visitor
2,465 Views

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

Jump to solution

Same issue here with 2017.2 on Linux

0 Kudos
Visitor gsutter
Visitor
1,902 Views

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

Jump to solution

Same error in SDx 2017.2 in Linux. Cosimulating in VHDL and Verilog.

More strange the Latency reported is not the same...

Report: 2917; VHDL: 5399 and Verilo 5428.

The simple algorithm implemented uses Floating Point

0 Kudos
Visitor jeff.su
Visitor
1,568 Views

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

Jump to solution

Same issue here with Vivado HLS version 2017.2 on Windows

Warning: OPMODE Input Warning : The OPMODE 001XXXX with CARRYINSEL  000 to DSP48E1 instance is invalid.

 

If it's a non-vital warning, is there any method to eliminate the warning message to speed up the co-simulation process??

0 Kudos
Explorer
Explorer
360 Views

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

Jump to solution

Hello,

 

I'm using SDSoC 2017.2 and I'm trying to co-simulate a floating-point design using as board the zc706.

I get the OPMODE Input Warning and I have the feeling that the simulation does not progress.. it's been 22 hours up to now. The same fixed-point version design simulates at about 20 minutes.

 

Is there any hope, or the only way to check my design is to actually have a zc706 board?

 

Without proper software tools the hardware is unusable no matter how good and well designed it is.

 

 

Cheers,

Panos

Without proper software tools the hardware is unusable no matter how good and well designed it is.
0 Kudos
Explorer
Explorer
350 Views

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

Jump to solution


After 1469m52.274s c/rtl co-simulation failed!

I have to wait ONE DAY AND ONE HOUR for the cosim to complete.

Still, I have no idea what went wrong.. my fixed-point design works fine (same code) and csim says my design gives correct results.

So, any suggestions?

 

 

Cheers,

Panos

Without proper software tools the hardware is unusable no matter how good and well designed it is.
0 Kudos
Adventurer
Adventurer
297 Views

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

Jump to solution

I had the same problem.  This error showed up and RTL cosimulation was taking a very long time.

 

When configuring RTL cosimulation, select "Setup Only".  That worked for me.  This option makes RTL cosimulation just generate the files.

0 Kudos
Explorer
Explorer
271 Views

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

Jump to solution

@agailey

Hi, agailey,
 
Thanks for your reply in the question thread and I just encountered the same problem. However, I have a question for you.
 
For the "Setup Only" option you mentioned, what's the purpose while set it ? Does it still run the C/RTL co-sim but not shown the progress and logging on the console screen ? Or it doesn't run C/RTL co-sim ? 
 
p.s. I use Vivado HLS/Vivado 2017.2 
 
Many thanks in advance.

 

0 Kudos
Adventurer
Adventurer
259 Views

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

Jump to solution

@nansonThe "Setup Only" option does seem to allow co-sim to run. I have the test bench print the results to the screen at runtime, and I do see these results printed to the screen even when "Setup Only" is selected.

0 Kudos