tnt
03/09/2024, 12:40 PMcaravel_openframe_project
project, you have some config in openlane/openframe_project_wrapper/fixed_dont_change/fixed_wrapper_cfgs.tcl
that explicitely says "DONT CHANGE" ... and then in openlane/openframe_project_wrapper/config.json
those values are overwritten ... so which one are the right one ?!?Tim Edwards
03/09/2024, 2:59 PMcaravel_openframe_project
has a setup that I attempted to do early on. I think some of those were just copied from caravel_user_project
and adapted. The caravel_user_project
has strict requirements on the PDN ring because it has to match up between the user project and the caravel chip. That wouldn't apply to the openframe. Also I don't think the die area and core area matter that much as long as the area overlaps the pins on the frame, so the difference of a few microns is probably not relevant. Just make sure that you're picking up the repository fork from https://github.com/efabless/openframe_project_wrapper which is the one that went through timing signoff.tnt
03/09/2024, 3:07 PMtnt
03/09/2024, 3:10 PMconfig.json
get very large rings but they also get "outside" of the official DIE_AREA
so I'm not entirely sure that's valid.tnt
03/09/2024, 3:11 PMTim Edwards
03/09/2024, 3:12 PMTim Edwards
03/09/2024, 3:16 PMcaravel_openframe
put in the gds/
directory of the caravel/
project.---Top level cells in the gds/
directory aren't used and are just taking up repository space. The final integration step uses mag/caravel_openframe.mag
. You can view that in magic, and if you prefer klayout, then just read it into magic long enough to write out a GDS file.tnt
03/09/2024, 3:28 PMCORE_AREA
was only affecting the generation of the standard cell grid, but that's also what will end up being used for the origin of the rings.