HBAC analysis issue, while simulating a mixer from Cadence examples

The "master.tag" file is a file that lives within the cellView directory which tells Virtuoso which file is the "master" file for the cellView, and hence what type of view it is. So here's an example (from ahdlLib):

UNIX> pwd
/export/home/apps/IC616_isr/tools/dfII/samples/artist/ahdlLib/decimator/veriloga
UNIX> ls -lL
total 24
-rw-r--r-- 1 workmgr users    40 Nov  8  1996 master.tag
-rw-r--r-- 1 workmgr users 13128 Apr  9  2007 netlist.oa
-rw-r--r-- 1 workmgr users     0 Sep  8  1997 pc.db
-rwxr-xr-x 1 workmgr users  1453 Jul 31  2004 veriloga.va*
UNIX> cat master.tag
-- Master.tag File, Rev:1.0
veriloga.va

As  you can see in this cellView, there is a "netlist.oa" file - this contains some information about the veriloga view, such as the terminals and hierarchy (none in this case) of the design - which is used to help with hierarchy traversal.

Just realised that would have made more sense to show the balun_ideal cellView as an example, but the master.tag is identical (in my installation).

Adding a config view won't help if the master.tag is messed up. It shouldn't be required for spectre simulation anyway - all that allows you to do is have more fine-grained control over view-switching during netlisting. WIthout a config view, you can simply control the switch (or view) list and stop list. The view list gives  you the order of preference for picking a view when descending the hierarchy, and the stop list says that if the view you switched into was in the stop list, don't expand the hierarchy any further. With a config, you can tell it that specific cells or instances (or occurrences) can use a different view than the global search order, or you can have an inherited view order for that part of the hierarchy downwards and so on.

So the "config trick" is not a trick - and it's not really relevant here (I don't think). You need to look in the balun_ideal/veriloga directory and see if the master.tag is missing or messed up - if so, it may be something has got corrupted in your installation:

UNIX> pwd
/export/home/apps/IC616_isr/tools/dfII/samples/artist/rfLib/balun_ideal/veriloga
UNIX> ls -lL
total 32
-rw-r--r-- 1 workmgr users  2720 Apr 20  2009 data.dm
-rw-r--r-- 1 workmgr users    40 Apr 20  2009 master.tag
-rw-r--r-- 1 workmgr users 13080 Apr 20  2009 netlist.oa
-rwxr-xr-x 1 workmgr users   479 Apr 20  2009 verilog.vams*
-rwxr-xr-x 1 workmgr users   479 Apr 20  2009 veriloga.va*

Note that if you are using IC5141, the files may be slightly different (prop.xx and veriloga.cdb). Ah, I just took a look in my IC5141 installation and it seems that the balun_ideal veriloga view directory is empty.

So maybe that is your problem? I'm really not sure why it was missing - strangely I can't find any reports of it being missing (despite the fact that it was for some time).

Which version are you using?

Regards,

Andrew.

The "master.tag" file is a file that lives within the cellView directory which tells Virtuoso which file is the "master" file for the cellView, and hence what type of view it is. So here's an example (from ahdlLib):

UNIX> pwd
/export/home/apps/IC616_isr/tools/dfII/samples/artist/ahdlLib/decimator/veriloga
UNIX> ls -lL
total 24
-rw-r--r-- 1 workmgr users    40 Nov  8  1996 master.tag
-rw-r--r-- 1 workmgr users 13128 Apr  9  2007 netlist.oa
-rw-r--r-- 1 workmgr users     0 Sep  8  1997 pc.db
-rwxr-xr-x 1 workmgr users  1453 Jul 31  2004 veriloga.va*
UNIX> cat master.tag
-- Master.tag File, Rev:1.0
veriloga.va

As  you can see in this cellView, there is a "netlist.oa" file - this contains some information about the veriloga view, such as the terminals and hierarchy (none in this case) of the design - which is used to help with hierarchy traversal.

Just realised that would have made more sense to show the balun_ideal cellView as an example, but the master.tag is identical (in my installation).

Adding a config view won't help if the master.tag is messed up. It shouldn't be required for spectre simulation anyway - all that allows you to do is have more fine-grained control over view-switching during netlisting. WIthout a config view, you can simply control the switch (or view) list and stop list. The view list gives  you the order of preference for picking a view when descending the hierarchy, and the stop list says that if the view you switched into was in the stop list, don't expand the hierarchy any further. With a config, you can tell it that specific cells or instances (or occurrences) can use a different view than the global search order, or you can have an inherited view order for that part of the hierarchy downwards and so on.

So the "config trick" is not a trick - and it's not really relevant here (I don't think). You need to look in the balun_ideal/veriloga directory and see if the master.tag is missing or messed up - if so, it may be something has got corrupted in your installation:

UNIX> pwd
/export/home/apps/IC616_isr/tools/dfII/samples/artist/rfLib/balun_ideal/veriloga
UNIX> ls -lL
total 32
-rw-r--r-- 1 workmgr users  2720 Apr 20  2009 data.dm
-rw-r--r-- 1 workmgr users    40 Apr 20  2009 master.tag
-rw-r--r-- 1 workmgr users 13080 Apr 20  2009 netlist.oa
-rwxr-xr-x 1 workmgr users   479 Apr 20  2009 verilog.vams*
-rwxr-xr-x 1 workmgr users   479 Apr 20  2009 veriloga.va*

Note that if you are using IC5141, the files may be slightly different (prop.xx and veriloga.cdb). Ah, I just took a look in my IC5141 installation and it seems that the balun_ideal veriloga view directory is empty.

So maybe that is your problem? I'm really not sure why it was missing - strangely I can't find any reports of it being missing (despite the fact that it was for some time).

Which version are you using?

Regards,

Andrew.