A
Angela formerly of Intel
Guest
What do you do when you open a newly arrived hierarchical schematic in
IC5033 to find basic/iopin/symbol pins & other lib/cell/view instances
blinking?
a) The missing master form tells you only the top-level unbound
masters, not all the underlying unbound instances. Should it provide a
fix-it wizard?
b) The Edit->Properties form won't find unbound pins (only other types
of unbound instances); and even so, it's not hierarchical anyway.
c) The DFII Search & Replace mechanism is hierarchical, but it won't
find pins or instances that are unbound (so it won't replace
anything).
How do YOU handle this common situation?
- Do you write SKILL code to solve unbound hierarchical instances
(incl. pins)?
(Does that SKILL use leRemasterInstances or some other remastering
function?)
- Do you temporarily copy duplicate masters into the original library
& then run a DFII search & replace (& then remove your temporary
duplicate masters)?
- Do you complain to Cadence support (I already did ... they filed a
PCR asking for a missing-master fix-it wizard)?
I am curious blinking:
What do YOU do when you find missing pin & other instance masters?
Note: Pins are handled differently than other instances according to
Cadence so my question is related to BOTH the special pins and regular
instances.
Angela
P.S. In my case, the original masters were moved from one library to
another but I received legacy schematics which have instances bound to
the original library which no longer has these instances. I merely
need to move the instance calls to where the new pin & instance
library is, hierarchically. I prefer to do this in one step. Before I
make any further moves, I ask you how you do this.
IC5033 to find basic/iopin/symbol pins & other lib/cell/view instances
blinking?
a) The missing master form tells you only the top-level unbound
masters, not all the underlying unbound instances. Should it provide a
fix-it wizard?
b) The Edit->Properties form won't find unbound pins (only other types
of unbound instances); and even so, it's not hierarchical anyway.
c) The DFII Search & Replace mechanism is hierarchical, but it won't
find pins or instances that are unbound (so it won't replace
anything).
How do YOU handle this common situation?
- Do you write SKILL code to solve unbound hierarchical instances
(incl. pins)?
(Does that SKILL use leRemasterInstances or some other remastering
function?)
- Do you temporarily copy duplicate masters into the original library
& then run a DFII search & replace (& then remove your temporary
duplicate masters)?
- Do you complain to Cadence support (I already did ... they filed a
PCR asking for a missing-master fix-it wizard)?
I am curious blinking:
What do YOU do when you find missing pin & other instance masters?
Note: Pins are handled differently than other instances according to
Cadence so my question is related to BOTH the special pins and regular
instances.
Angela
P.S. In my case, the original masters were moved from one library to
another but I received legacy schematics which have instances bound to
the original library which no longer has these instances. I merely
need to move the instance calls to where the new pin & instance
library is, hierarchically. I prefer to do this in one step. Before I
make any further moves, I ask you how you do this.