Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 4900
  • 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

Hierarchical editor for AMS sims

paulinho

I have a gate level netlist, with which I want to do a co simulation in Virtuoso. I also only have the functional views of the individual std cells (which are present inside the gate level netlist). How do I configure the Hierarchical Editor (View list & Stop list) for this ? 

When I give 'spectre' in the stop list, the std cells are not binded in the HED

When I give 'functional' or both 'functional' and 'spectre' in the stop list, the simulator log shows:
Instance '**' of cellview '***:functional' was set to be stop view in Cadence Hierarchy Editor(HED) but this instance has hierarchy beneath it. Review and update its settings in HED appropriately.

  • You would normally just put functional in the view list - putting it in the stop list would indeed stop it expanding hierarchy beneath the functional views (if there is any - and the fact that it is complaining suggests that it is wrong).

    I don't see why it would not "bind" the cells if there is a functional view - I'd probably have to see what is actually happening to understand the problem - can you give a screenshot of the problem when you omit "functional" from the stop list (how it shows in the hierarchy editor, and what views exist for the problematic cell in the library manager).

    One thought - if there is a functional view with hierarchy within it, then you almost certainly will need to specify the library list to include the library containing the lower level hierarchy. Put another way, if the functional view is Verilog code with an instantiation, that only binds the cell; to find the cell you normally have to ensure that the library list includes all the libraries where it needs to look for such modules (cells) referenced from within Verilog descriptions.

    Andrew

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.