Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 14874
  • 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

Hierachical comparisson issues in LEC

Verplec

Hello,

      I sucessfully completed a 

   write hier_compare

   run hier_compare

 verification approach , however in the run log i see 2 primary warnings:

  // Warning: Module 'XXXXXXX' exists in Revised only. Skip it for hierarchical comparison

// Warning: Golden or Revised have modules with number of instances less than 50. Skip it for hierarchical comparison
//    (G) xxxxxxx
//    (R) xxxxxxx

I am wondering if any one be kind enough to help me , ridding of these warnings or a work around to inform LEC not to skip anything.

Thank you in advance.

Roy

Parents
  • Hello Roy, 1) Is the renaming rule cause of the problem ? a) If the renaming rule was a success , you would not seen the warning of a missing module on revised or golden. b) if the renaming rule failed then there is a possibility of you seeing the message.Have you tried the "test renaming rule" to check if it worked? 2) to show if the modules are really merged ? That is the core functionality and the warning message is the proof.One way of checking may be using gate manager or schematic to prove this. 3) black boxing ? there is a concept of dynamic hierarchical comparision where the non-eq module are un black boxed and included in the comaprision of the parent module.You may want to get the script reviewed by the expert support available by filing a ticket through sourcelink.cadence.com. Hope this helps. -- Vishnu
Reply
  • Hello Roy, 1) Is the renaming rule cause of the problem ? a) If the renaming rule was a success , you would not seen the warning of a missing module on revised or golden. b) if the renaming rule failed then there is a possibility of you seeing the message.Have you tried the "test renaming rule" to check if it worked? 2) to show if the modules are really merged ? That is the core functionality and the warning message is the proof.One way of checking may be using gate manager or schematic to prove this. 3) black boxing ? there is a concept of dynamic hierarchical comparision where the non-eq module are un black boxed and included in the comaprision of the parent module.You may want to get the script reviewed by the expert support available by filing a ticket through sourcelink.cadence.com. Hope this helps. -- Vishnu
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.