• 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. Black Box Mismatches

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 61
  • Views 16099
  • 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

Black Box Mismatches

archive
archive over 17 years ago

Hello Everyone,
      I have problem with the black box matching.
      I am trying to run a LEC on top level(RTL to gates) by assuming the core blocks are black boxes. Other than these black boxes top level have the JTAG, PINMUXING, PAD, clkrst and some clock blocks. I am seeing black box non equivalences. I tried to diagonise one of the black box which has a feedback to its input from its own output, i found that the outputs ports from which the feedback has to come is different in both the RTL and Revised when checked in the schematics, but i checked the connections in both RTL and Revised netlist and i have found that they are connected properly coming from same port.
            I have found that all other black boxes are unequal because one of its input are connected to the other black box outputs, and all these ports are mismatched between RTL and revised in schematics, but in RTL and netlist theyare correctly connected, so LEC is assuming the different port? why?

Example:   to explain the scenerio
  testblock1 and testblock2 are blackboxes

  testblock1 :                                                         testblock2:
      blockout[4:0]  (5bit output bus)                          blockinput[1:0]

     blockout[3:2] are connected to blockinput[1:0] in both revised and RTL. testblock1 is non equivalent black box and if we diagonise testblock2. The input port blockinput[0] is connected to the blockout[2] in RTL and blockout[4] in Revised. Can i know y this is happening in LEC? If the black boxes are non equivalent then y it is assuming these. What are the basic checking does LEC do to see whether black boxes are equal.

         
Please also find the basic do file used.
system mkdir -p lec
set analyze option -auto
set log file lec/lec.log -replace
date
set UNDefined Cell black_box -both
$read_LIBRARY
$readRTL
$readNETLIST
add pin constraints 1 vddmem -both
  add pin constraints 1 vddp -both
  add pin constraints 0 vss -both
  add pin constraints 0 vsso -both
  add pin constraints 0 vsspll -both
  add pin constraints 0 jtag_trst_l -both
set flatten model -seq_constant -seq_constant_x_to 0
//set flatten model -seq_merge
set flatten model -nodff_to_dlat_zero
set flatten model -nodff_to_dlat_feedback
set flatten model -latch_transparent
set undriven signal 0 -both
report black box
set mapping method -name only -nosensitive
set system mode lec
set mapping method -name first
map key points
add compared points -all
compare
exit -force


Thanku,
Sai.





 

 
   
     


Originally posted in cdnusers.org by saikiran_454
  • Cancel
Parents
  • archive
    archive over 17 years ago

    By default lec will assume that the bus is defined in ascending order, but it looks like you are defining the bus in descending order. Try adding the -noascend switch to the set_undefined_cell command.


    Originally posted in cdnusers.org by broesicke
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    By default lec will assume that the bus is defined in ascending order, but it looks like you are defining the bus in descending order. Try adding the -noascend switch to the set_undefined_cell command.


    Originally posted in cdnusers.org by broesicke
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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