Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 14463
  • 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

ASSURA LVS errors

Dennis Faber

Hello,

I hope you will undestand me. My English is not very well.

My Problem:

I have to check a layout with assura. It is an array and consists of tree components. I call them "basic cells". So I build tree types of columns of those cells and then I add them to an array. If I check the columns separetly. It works. Thereby the "basic cells" will be ckecked with ?flattenCellContents contition. If I try to verify the whole array. I get errors (device, nets) in one column and their subcell, "one of a basic cell". This column consist of two mirrored and overloop "basic cells of one type".

I think I get the error message because the cells overlap. I assume Assura put some devices on the top of hierarchy and then can not map schmetatic and layout. So my question is, are there any rules I can put to avoid this problem?

I have a solution that woks but I have to flatten one type of array. It take a lot of time to check the whole array.

If you have some ideas, post otherwise correct my language skills! :-)

 Best regards, Dennis

Parents

  • Hi Dennis

    Would you please post the specific error messages? It would be good if you can upload the cls file in the run directory. Perhaps you can try adding expandOnError cmd and see if it solves the problem. It can be found in avCompareRules of the lvs form. If you are running by batch mode, please add the following to the rsf file:

    avCompareRules(
       expandOnError( (unstableDevices t) (swap t) (reduce t) (pins t) (match t) (swapThres t) (instCount t) (skipMatchOnReduceError t) (ambiguousPinAssignment t) (parameter t) )
    ) ;avCompareRules


    Best regards
    Quek

Reply

  • Hi Dennis

    Would you please post the specific error messages? It would be good if you can upload the cls file in the run directory. Perhaps you can try adding expandOnError cmd and see if it solves the problem. It can be found in avCompareRules of the lvs form. If you are running by batch mode, please add the following to the rsf file:

    avCompareRules(
       expandOnError( (unstableDevices t) (swap t) (reduce t) (pins t) (match t) (swapThres t) (instCount t) (skipMatchOnReduceError t) (ambiguousPinAssignment t) (parameter t) )
    ) ;avCompareRules


    Best regards
    Quek

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.