Stats

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

adexl and config file

gsciller

Hello everyone,

 When I am using a config file set to a schematic view, I can see the underlying cells and their respective views which I can change individually to lets say, calibre or spectre.  When I then switch the config top cell view to adexl, I can view the top level cell but not view or change hierarchical cell views. Is there a way to change then underlying cell views when using adexl and a config file. Any suggestions would be appreciated and would greatly improve my efficiency. Thanks.

 

  • I suspect you've misunderstood something here. Config views are intended as a way of describing the rules by which a design hierarchy is expanded, and are typically consumed by tools that need to expand the hierarchy (such as the netlisters used in ADE L/XL/GXL). So it's reasonable that ADE XL allows you to describe one or more tests where the design is specified as a config - and that will tell it how to expand the hierarchy (which views you want to simulate) for that test.

    It makes no sense for a config view to reference an ADE XL view. The ADE XL view is nothing to do with the design hierarchy - so I can't see why you'd ever want to do this. What would you expect to do with the resulting config? If you consumed that resulting config in (say) ADE XL, what would you expect it to do when it encountered an ADE XL view in the config? Especially as the ADE XL view could be describing multiple tests, each with different designs.

    So I think you're probably thinking about this back to front. You use the config to describe the hierarchy expansion, and then reference that config from the ADE XL view, not the other way around.

    Kind Regards,

    Andrew.

     

  • I see. Thank you for the quick response.

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.