The Designer's Guide Community Forum

The Designer's Guide Community Forum
https://designers-guide.org/forum/YaBB.pl
Simulators >> AMS Simulators >> Hierarchy Editor cannot recognize cells
https://designers-guide.org/forum/YaBB.pl?num=1161620802

Message started by Pavel on Oct 23^rd, 2006, 9:26am

Title: Hierarchy Editor cannot recognize cells
Post by Pavel on Oct 23^rd, 2006, 9:26am

Hello

In my design I use only veriloga and verilogams views.
After making config view from TOP LEVEL cell, I see only TOP LEVEL cell in Cell Binding table of Hierarchy Editor.
All other cells are not recognized. Why??

For View List I use:
verilogams veriloga behavioral functional schematic symbol

For Stop List: symbol

In Library List I put the name of library where all the cells are situated.

Thank you in advance.

Pavel.

Title: Re: Hierarchy Editor cannot recognize cells
Post by Pavel on Oct 25^th, 2006, 3:57am

The issue (that I found) from this situation is to create SYMBOL view for each cell in hierarchy.
Including veriloga or verilogams in Stop List doesn't help as they can contain hierarchy.

Is this solution only issue?

Regards.

Title: Re: Hierarchy Editor cannot recognize cells
Post by bernd on Oct 25^th, 2006, 5:03am

How have you instantiated your blocks in the hierarchy
if you haven't got a symbol view for them?

Cadence DFII asks you whenever you finish first editing
of your VerilogA file and you have saved & quit the file
if a symbol view for the cell should be created, as long
as you edit inside DFII.

Did I miss something, I thing I didn'd understand the problem
clearly.

The HED gets the information for the hierarchy of the cellviews
pc.db (parent child database) file, at least in CDBA database versions
of DFII.

Bernd

Title: Re: Hierarchy Editor cannot recognize cells
Post by Pavel on Oct 25^th, 2006, 5:16am

Thank you for answer, Berndt

I thought that I can work without symbols while I don't use Schematic Editor.
After creating the veriloga/verilogams views, the Library Manager really proposed me to create symbol, but I refused,
thinking that for my purposes it isn't necessary.

So, I was wrong?

Pavel.

Title: Re: Hierarchy Editor cannot recognize cells
Post by bernd on Oct 25^th, 2006, 5:47am

Quote:

So, I was wrong?

Not necessarily, but if you work in DFII and
with HDE and not on a command line level, I would say yes.

Bernd

Title: Re: Hierarchy Editor cannot recognize cells
Post by Pavel on Oct 25^th, 2006, 5:57am

Ok, thanks

Title: Re: Hierarchy Editor cannot recognize cells
Post by jbdavid on Nov 2^nd, 2006, 12:31am

The issue in the cadence system, is that without the symbol view, when you check and save a structural view, (verilog netlist) it builds a database with pointers to the views used, but if those cells don't have a symbol view, the link database is not made correctly.
thus having the symbol makes it work..
Jonathan

Title: Re: Hierarchy Editor cannot recognize cells
Post by zhong on Dec 10^th, 2006, 3:44pm

HED does NOT need symbol for the view binding.
If you have full text view . there is no schematic view or symbol view at all . You can compile the text like verilog , veriloga , verilogams to DFII lib for example
ncvlog -use5x top.vams -work mylib

To be able to see HED bind to the sub text cell under the top level module . you need to add mylib in HED lib list .

Again . NO symbol needed in Cadence HED .

Title: Re: Hierarchy Editor cannot recognize cells
Post by Pavel on Dec 18^th, 2006, 2:50am

Hello Zhong

Thank you for respnse. I don't use command line, but GUI, so for me having SYMBOL view is mandatory.
We can postulate what we want, but the best juge is experience, isn't it?
With SYMBOL view for each module the hierarchy tree is created, without SYMBOL view - NOT.

Regards.

Pavel.

Title: Re: Hierarchy Editor cannot recognize cells
Post by zhong on Dec 19^th, 2006, 7:48pm

Pavel,
Even you use the GUI flow. The symbol is not a mandatory for TEXT view. HED hier tree does not requires for symbol . The hier tree is based on the pc.db file under module view not symbol .

However you can use symbol view to build up the schematic or go with verilogIn to create a schematic.

Basically Symbol is a MUST for schematic build up but this is NOT a must requirement in HED because HED can handle text view call text without schematic in between.

Here is the examples
top level top cell module view
middle leve - middle cell l verilogams view
lower level -- cell A schematic
leaf level -- cell x, y ,z

You dont need any symbol for top/middel and cell A . Of course you need the symbol to represent the sub block x/y/z to build schematic of cell A.

top level schematic -- top cell
middle level -- middle cell verilogams
leaf cell - cell B verilogams

You need to have middle cell symbol because this is a must for built-up of top cell schematic , But you dont neecd to the cell B symbol , text view instantiate text view does not requires symbol for the hier build-up

I am doing this in my daily work and it works perfectly. As I said, what you need to do is to add the text view lib in the HED lib list.

Of course , if you choose to always use symobl, that's fine . But it' does not necessary means it's a must .

Hope this helps ...

Zhong