New DFII cdsLibDebug UNIX/Linux command

[John Gianni]

1. In the past, Customers approached me with a problem of debugging deeply
nested DFII cds.lib files containing an assortment of:
a) multiple-nested cds.lib files (only some of which might exist)
b) shell-environment variables (only some of which might exist)
c) multiple libraries of the same name (only some of which exist)
d) incorrectly assigned tmp libraries (overlay libraries), etc.

2. The good news is that Cadence has created a new executable:
cdsLibDebug
which works from the UNIX/Linux command line as:
csh% cdsLibDebug -cla
which should help you debug your cds.lib files for errors
(see PCR 356393).

3. I just tested it this Sunday on a recent version of DFII:
csh% cds_root cdsLibDebug
REPORTED: /net/chip/cds/ICOA5033
csh% cds_root vce
REPORTED: /net/chip/cds/ICOA5033
csh% vce -W
REPORTED: sub-version 5.02.33.111
csh% cds_root icfb
REPORTED: /net/chip/cds/ICOA5033
csh% icfb -W
REPORTED: sub-version 5.02.33.111

Let's try the new cdsLibDebug command on an arbitrary cds.lib file:
csh% setenv SOC /net/chip/SOC_TSMC13_OA
csh% cd $SOC/design/custom
csh% cdsLibDebug -cla
INSTANTLY REPORTED:

Parsing cdslib file ./cds.lib.
cds.lib files:
1: /net/chip/SOC_TSMC13_OA/design/custom/cds.lib

Libraries defined:

Defined in /net/chip/SOC_TSMC13_OA/design/custom/cds.lib:
Line# Filesys Path
----- ---- ----
5 basic /cds/ICOA5033/tools/dfII/etc/cdslib/basic
6 analogLib /cds/ICOA5033/tools/dfII/etc/cdslib/artist/analogLib
9 avTech /cds/AV305_502_sun4v/tools/assura/etc/avtech/avTech
13 tsmc13lv /SOC_TSMC13_OA/share/lib/pdk_tsmc13lv_1.0/tsmc13lv
16 tpz013lg2_6lm /SOC_TSMC13_OA/share/lib/tsmc13/tpz013lg2_6lm
19 tsmc13_6lm /SOC_TSMC13_OA/share/lib/tsmc13/oa/tsmc13_6lm
22 condor_ram /SOC_TSMC13_OA/design/cicdata/oa/condor_ram
24 condor_rom /SOC_TSMC13_OA/design/cicdata/oa/condor_rom
25 hummingbird /SOC_TSMC13_OA/design/cicdata/oa/hummingbird
26 falcon /SOC_TSMC13_OA/share/lib/oa/falcon
30 mockingbird /SOC_TSMC13_OA/design/cicdata/oa/mockingbird
33 condor /SOC_TSMC13_OA/design/cicdata/oa/condor
36 raptor /SOC_TSMC13_OA/design/cicdata/oa/raptor
39 custom_pad /SOC_TSMC13_OA/design/cicdata/oa/custom_pad
40 tooling /SOC_TSMC13_OA/design/cicdata/oa/tooling
43 robin /SOC_TSMC13_OA/design/cicdata/oa/robin
49 finch /SOC_TSMC13_OA/design/cicdata/oa/finch
55 bushtit /SOC_TSMC13_OA/design/cicdata/oa/bushtit
59 nutcracker /SOC_TSMC13_OA/design/cicdata/oa/nutcracker
60 ptarmigan /SOC_TSMC13_OA/design/cicdata/oa/ptarmigan
62 owl /SOC_TSMC13_OA/design/cicdata/oa/owl
65 wigeon /SOC_TSMC13_OA/design/cicdata/oa/wigeon
69 quail /SOC_TSMC13_OA/design/cicdata/oa/quail
72 turnstone /SOC_TSMC13_OA/design/cicdata/oa/turnstone
75 warbler /SOC_TSMC13_OA/design/cicdata/oa/warbler

Note: Had we had nested cds.lib files, these would have all been
traversed accordingly.

Note: Our cds.lib is extensively commented and is never overwritten
by any tool (see PCR 426161 to ensure comment preservation).

Note: This cdsLibDebug command would report any missing or corrupted or
libs not found due to incorrect shell-environment variables, etc.

Note: According to the PCR, the first release containing this new
cdsLibDebug utility is IC-5.0.33
--
ALL my USENET posts are personal opinion for the benefit of Cadence Customers.