Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 2265
  • 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

Hierarchy Editor - Setting schematic view recursively within a tree

cdonovan

 I'll try and explain my problem clearly first (sometimes there is an alternative solution).

 

I have a chip with distinct sections. Schematically they reside in different instances (eg I0 and I1).

I want to simulate everything within the section I0 using behavioural models and I1 with primitive models.

Within the view list I put my behavioural model before the schematic model name and that takes care of chosing the behavioural model.

For example my view list is: spectre schematic_behav cmos_sch schematic veriloga ahdl

 

Unfortunately this forces the I1 to also use behavioural models. While I *could* individually choose the models for the instance this is painful as there is a very large hierarchy into which I would have to decend and many individual instances (eg I1.level1.level2...   ...level20).

Is there an easy way that I can define that everything in the hierarchy I0... uses schematic_behav and everything in the hierarchy I1... uses schematic?

 

Thanks

  • You can do this by setting the "inherited view list". For example, on the tree view in the hierarchy editor, find I0 and then look along and see there is a column labelled "inherited view list" or something like that (I'm doing this from memory). If you set the order of views you want in this field, it will affect anything beneath I0.

    If that's not clear, I'll upload a picture (tomorrow).

    Regards,

    Andrew 

  •  Great! Thats exactly what I want Andrew.

    Thanks for that!

     

    Regards,

    Colm

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.