Hi, with @User configuration we have achieved to pass the tapeout job. However, we have done some modifications to the macro to try to reduce the sllew violations and, even that we don't have DRC violations, we have failed the test. We don't know why as when checking the log files it appears empty. Do you know what is happening? @User

[11/14/21 08:09:08 PST] FAILED
STDOUT: {{Project Git Info}} Repository: <https://github.com/theatomb/Elpis-Light-MPW3.git> | Branch: HEAD | Commit: 509a6d573900b8c88f11cc9d684c7b5c1b488967
STDOUT: {{Extracting GDS}} Extracting GDS Files
STDOUT: {{Project GDS Info}} user_project_wrapper: 5d943fccf41b5c830d1d179f68a32129f355651c
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: Final GDS File caravel_0003c9f4.gds sha1sum: 63c692ccf0091718cc549b338768a025495adfa0
STDOUT: {{Step Update}} Converting Final Layout from GDS to OAS
STDOUT: Final OAS File caravel_0003c9f4.oas sha1sum: 7289da7fdc75290abe42f120700528e42ba2b089
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 u6276_aurorat/design/elpis-light-mpw3/jobs/tapeout/db87a841-c221-438a-8c6e-4ce0364a9e7b/logs

@User I see you got to a successful precheck, is your issue resolved ?

@User Yes! Thanks to @User docker image for the macros, and the official one for the wrapper. The issue from this screenshot I don't know where it comes from as there were no violations and anything reported... It was a try to improve the design but that configuration had something that did not like..

@User thanks for letting me know, the issue was related to your git repo configuration, I am not sure of the exact cause but it failed for that reason, regardless glad you fixed it, and good luck 🙏

@User The configuration that seems that did not like was: Having in the core macro

set ::env(SYNTH_MAX_TRAN) "3.1"

and this settings in the custom sram:

set ::env(DIE_AREA) "0 0 1200 1500"

,

set ::env(PL_TARGET_DENSITY) 0.46

,

set ::env(PL_RESIZER_MAX_SLEW_MARGIN) 75

,

set ::env(SYNTH_STRATEGY) "AREA 2"

. If you want to see the current settings better check the repo, so I don't make this message too huge😅

ok, I will pass it along, thanks @User