• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. Potential multiply-driven net (corrected typesetting)

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 61
  • Views 13438
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Potential multiply-driven net (corrected typesetting)

archive
archive over 17 years ago

I have the following interfaces for two submodules module comparator7(a, b, clk, ce, reset, qa_gt_b); input clk; // The two are only sub modules in the design and there are instanciated and connected in an upper layer module as follows module eq_node_deq_5(clk, reset, decoding_enable, p_ch, load_prob_enable, prob_id, node_id, load_shift_enable,in0, in1, in2, in3, in4, address0_0, address0_1, address0_2, address0_3, address0_4, address0_5, address1_0, address1_1, address1_2, address1_3, address1_4, address1_5, address2_0, address2_1, address2_2, address2_3, address2_4, address2_5, address3_0, address3_1, address3_2, address3_3, address3_4, address3_5, address4_0, address4_1, address4_2, address4_3, address4_4, address4_5, out0, out1, out2, out3, out4, out_ch ); //==> goes to UD counter input clk; // goes to chk node output out1; // ==> goes to chk node output out2; // ==> goes to chk node output out3; // ==> goes to chk node output out4; // ==> goes to chk node output out_ch; wire em0_sig_in; wire em1_sig_in; wire em2_sig_in; wire em3_sig_in; wire em4_sig_in; wire em0_sig_out; wire em1_sig_out; wire em2_sig_out; wire em3_sig_out; wire em4_sig_out; wire update0; wire update1; wire update2; wire update3; wire update4; wire j0; wire j1; wire j2; wire j3; wire j4; wire k0; wire k1; wire k2; wire k3; wire k4; wire in_ch; wire j_ch; wire k_ch; wire out0; wire out1; wire out2; wire out3; wire out4; wire out_ch; wire cmp_en; reg sig_ch; assign cmp_en = (prob_id == node_id & load_prob_enable)? 1'b1 : 1'b0 ; //TODO: validate the first two address lines connection with SAEED comparator7 comparator(.a(p_ch), .b({address4_0, address3_5, address3_4, address3_3, address3_2, address3_1, address3_0}), .clk(clk), .ce(cmp_en), .reset(reset), .qa_gt_b(in_ch)); em em0(.clk(clk), .reset(reset), .in_bit(em0_sig_in), .update(update0), .address({address0_5, address0_4, address0_3, address0_2, address0_1, address0_0}), .out_bit(em0_sig_out)); // some other glue logic endmodule When synthesizing the design with BuildGates, I get the following warning message. I cannot understand why I get this warning since all the address*_* signals are driven only by input of the top layer. In all other submodules these signals are all input signals and not output. The same holds for the clk and the reset signal --> WARNING: Potential multiply-driven net 'address4_5' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'address3_5' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'address3_4' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'address3_3' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'address3_2' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'address3_1' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'address3_0' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'reset' found in module 'eq_node_deq_5' . --> WARNING: Potential multiply-driven net 'clk' found in module 'eq_node_deq_5' .


Originally posted in cdnusers.org by gkamendje
  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information