I am getting these errors when doing tapeout job o...
# caravel
h
I am getting these errors when doing tapeout job on my design. Any idea how to solve this?
m
@User I believe these are warnings generated from reading GDS, is that correct? Are they causing fatal errors? @User these can be ignored correct -
boundary was redefined
and
NODE elements not supported
?
h
Seems like so... These warnings are generated in fill_initial.log, not sure if these can be ignored or not. But I don't think this would cause fatal errors, the tapeout job can proceed and finish. I went through all the logs and these errors are the only errors I got from the tapeout job. If they can be ignored, then I am genuinely confused about what change I should make to my layout. The log only gave me a fail message without telling me where was the problem.
Copy code
10/25/21 09:52:32 PDT] SUBMITTED






[10/25/21 10:19:35 PDT] STARTED






[10/25/21 10:19:41 PDT] PROJECT GIT INFO
Repository: <https://github.com/jhz701/class_d_audio_amplifier.git> | Branch: main | Commit: ceca0b29f456a86cebe0430712994cab4473a1b3






[10/25/21 10:19:41 PDT] EXTRACTING GDS
Extracting GDS Files






[10/25/21 10:19:44 PDT] PROJECT GDS INFO
user_analog_project_wrapper: d6da70a242b11d25194d62345a4cb471e801bf9d






[10/25/21 10:19:44 PDT] START
Tapeout Started






[10/25/21 10:19:45 PDT] STEP UPDATE
Generating Final Layout: Step 1 of 5






[10/25/21 10:23:13 PDT] STEP UPDATE
Generating Final Layout: Step 2 of 5






[10/25/21 10:34:50 PDT] STEP UPDATE
Generating Final Layout: Step 3 of 5






[10/25/21 10:50:54 PDT] STEP UPDATE
Generating Final Layout: Step 4 of 5






[10/25/21 10:58:37 PDT] STEP UPDATE
Generating Final Layout: Step 5 of 5






[10/25/21 11:00:27 PDT] STEP UPDATE
Converting Final Layout from GDS to OAS






[10/25/21 11:00:56 PDT] STEP UPDATE
Executing Check 1 of 2: Klayout Metal Minimum Clear Area Density






[10/25/21 11:04:54 PDT] STEP UPDATE
Executing Check 2 of 2: Klayout Field Oxide Mask Density






[10/25/21 11:05:10 PDT] FINISH
Executing Finished, the full logs can be found in u5424_hj2548/design/class-d_audio_amplifier/jobs/tapeout-job/60fbc78a-460c-4abf-8878-1a4b882c7d38/logs






[10/25/21 11:05:10 PDT] FAILED
STDOUT: {{Project Git Info}} Repository: <https://github.com/jhz701/class_d_audio_amplifier.git> | Branch: main | Commit: ceca0b29f456a86cebe0430712994cab4473a1b3
STDOUT: {{Extracting GDS}} Extracting GDS Files
STDOUT: {{Project GDS Info}} user_analog_project_wrapper: d6da70a242b11d25194d62345a4cb471e801bf9d
STDOUT: {{START}} Tapeout Started
STDOUT: {{Step Update}} Generating Final Layout: Step 1 of 5
STDOUT: {{Step Update}} Generating Final Layout: Step 2 of 5
STDOUT: {{Step Update}} Generating Final Layout: Step 3 of 5
STDOUT: {{Step Update}} Generating Final Layout: Step 4 of 5
STDOUT: {{Step Update}} Generating Final Layout: Step 5 of 5
STDOUT: {{Step Update}} Converting Final Layout from GDS to OAS
STDOUT: {{Step Update}} Executing Check 1 of 2: Klayout Metal Minimum Clear Area Density
STDERR: [ WARN ] MET Density Check Result: GDS has 0 DRC violations.
STDOUT: {{Step Update}} Executing Check 2 of 2: Klayout Field Oxide Mask Density
STDERR: [ WARN ] FOM Density Check Result: GDS has 0 DRC violations.
STDOUT: {{FINISH}} Executing Finished, the full logs can be found in u5424_hj2548/design/class-d_audio_amplifier/jobs/tapeout-job/60fbc78a-460c-4abf-8878-1a4b882c7d38/logs
o
Hello Hongzhe, I believe you failed
tapeout
for a reason unrelated to your design, please re-submit another
tapeout
and let me know if you still get a
failed
status.
t
For the record, yes, the NODE and boundary messages are informational and do not represent an error. The boundary issue is that there are multiple mask layers that define the cell boundary, and I may be missing a check in magic to see if they represent the same boundary and to not complain about it if so. The NODE issue is that magic doesn't recognize this GDS record, and I have never seen it sufficiently documented to know how to handle it. It does not represent anything related to a mask layer, so ultimately it is not a problem.