can anyone get a successful result when building caravel_user_project with the mpw3 tools that includes an openram block?

I haven't had time to update to the mpw3 work flow, so I'm not going to be much of a help here for now

@User I have used OPENRAM in My Two of MPW-3 Projects https://efabless.com/projects/422 and https://efabless.com/projects/385 In the both project in the local pre-check run has 50 Magic DRC around SRAM .. Still I need to understand how to replace meglef for SRAM to avoid these magic DRC.

Probably something else? We get 3million drc

@User, I have run Magic DRC only with local pre-check. In the local pre-check run, as Tim Edwards informed the Magic DRC check are around the SRAM are bypassed. You can refer this logic in File: ./checks/drc_checks/magic/magic_gds_drc_check.py def magic_gds_drc_check(gds_ut_path, design_name, pdk_root, output_directory): parent_directory = Path(file).parent logs_directory = output_directory / 'logs' outputs_directory = output_directory / 'outputs' reports_directory = outputs_directory / 'reports' design_magic_drc_file_path = reports_directory / f"magic_drc_check.drc.report" installed_sram_modules_names = [] sram_maglef_files_generator = Path(pdk_root / "sky130A" / "libs.ref" / "sky130_sram_macros" / "maglef").glob('*.mag') for installed_sram in sram_maglef_files_generator: installed_sram_modules_names.append(installed_sram.stem) sram_modules_in_gds = [] for sram in installed_sram_modules_names: if check_if_binary_has(sram, gds_ut_path): sram_modules_in_gds.append(sram) # only the name of the module Precheck Git Repo Path: https://github.com/efabless/mpw_precheck.git

So do you disable magic DRC for building?

Yes, I disabled Magic DRC check during make user_project_wrapper Run using interactive.tcl I am using local pre-check to validate the Magic DRC. Still I see Magic DRC is broken in efabless site GUI pre-check.

@User Are you still at 50 DRC violations in precheck? Do you know anything about efabless work in the matter of precheck?