How-To Set LEF/DEF Input Warnings as Exception Severities for the Calibre FDI Utilities
How-To Set LEF/DEF Input Warnings as Exception Severities for the Calibre FDI Utilities
This video demonstrates how to use the FDI message codes as input exception severities when converting LEF/DEF design data to GDS or OASIS with the Calibre FDI2GDS or FDI2OASIS utilities.
Content
7.02 -> Hello and welcome to the IC Nanometer design
channel. Today, I'll demonstrate how to set
12.24 -> LEF/DEF input warnings as exception severities
when running the Calibre FDI utilities.
18.48 -> To start, I'll run fdi2oasis utility on
asimple LEF/DEF testcase which, I know,
23.88 -> has a few different warning types reported.
28.5 -> The summary at the bottom of the transcript lists
the FDI warning codes and the number of warnings
33.78 -> printed in the transcript, as well as the total
number of each type found during the conversion.
40.32 -> The default for each warning code is 20,
but that can be customized by setting the
44.52 -> FDI_DBDIFF_SUPPRESS_VALUES environment variable.
48.96 -> I'll add this to my script and set
FDI1119 to output just 1 message,
53.34 -> FDI1121 to 3, and FDI1173 to 300.
59.82 -> Now I'll rerun the script to see the difference.
65.82 -> Here, we can see that the printed
message counts match the settings
68.94 -> specified in the variable but the actual
number of warnings found has not changed.
74.58 -> Rather than specifying custom values for each
message key, we can set a global value. Here,
80.28 -> I'll just set it to 500 so we
can force all the messages.
89.34 -> This time, when I re-run, the
printed counts match the total.
93.9 -> Understanding the source of these warning codes
95.88 -> is critical to ensure the data you
generated is correct and complete.
99.48 -> In the log file, we can scan for the warning codes
and see the message description. Here, the FDI1119
106.38 -> message indicates an object in the DEF was on
a layer not defined in the LEF technology file.
112.86 -> I can manage FDI behavior for
individual message codes by
116.52 -> adding the -inputExceptionList
option to the FDI command line.
120.78 -> First, I'll set the three codes to 1
which should match the current behavior.
128.16 -> When I rerun, I don't see any
difference. This is what we expected.
133.92 -> However, if I set a value of 2 and
rerun I do expect to see a difference.
140.82 -> This time the job stopped almost
immediately and I can see the
144.3 -> error code FDI1119 for the issue causing it.
149.34 -> This one is just a fake error
I created in the DEF file. So
152.88 -> when I fix it, that message won't be
reported and the job will continue.
160.44 -> Let me set the other codes to 2
so they will also force an exit.
171.06 -> So that also worked. The inputExceptionList is
174.48 -> a good way to choose specific warning codes
you want to check for, but you can also use
178.68 -> an environment variable if you want any
LEF/DEF warning codes to force an exit.
185.1 -> In my script, I'll set
FDI_LEFDEF_WARNINGS_AS_ERRORS to 1 and rerun.
196.62 -> The environment variable also
forced FDI to exit as we expected.
200.22 -> I hope you found this useful, thanks for watching.
Source: https://www.youtube.com/watch?v=s9fI4uSl5-U