• 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. lec blackbox nonequivalent problem

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 63
  • Views 15444
  • 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

lec blackbox nonequivalent problem

Arcade9999
Arcade9999 over 15 years ago

Dear All,

Currently I use the hierarchical compare for rtl to synthesized netlist LEC.
The sub-modules are all equivalent and are set to blackbox after comparison.
However, there are blackbox nonequivalent occur when comparing the top module.

For example: 

In rtl:

module top(inA, ....);
input [31:0] inA;
...
wire  [31:0] inB;
assign inB = inA;

sub1 usub1(.in1(inB), ...);
...
endmodule

In netlist:

module top(inA, ....);
input [31:0] inA;
...
sub1 usub1(.in1(inA), ...);
...
endmodule

 

The sub-module sub1 is compared firstly and set to blackbox.
But sub1 will be reported as nonequivalent BBOX after comparing top module top.

I found the problem is due to the connection wire name of blackbox are changed after synthesis optimization.

So is there any command that can solve this kind of blackbox nonequivalent problem??

Thanks a lot!!

  • Cancel
  • croy
    croy over 15 years ago

     Hi

     

    This should pass. It doesn't matter that the net names changed as long as the driver is the same. What does the diagnosis manager report? Is anything reported by 'report message -map -verbose'? Are you running Conformal L (ASIC) or XL (Ultra)?

    You may want to file a Service Request with support so they can do a Spacecruiser session with you.

     Also, allow me to do a quick plug for our online on-demand training about the Conformal diagnosis features at trainingondemand.cadence.com.

     

    Chrystian

    • Cancel
    • Vote Up 0 Vote Down
    • 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