Open amm-efabless opened 1 month ago
Some IPs might require a lot of stuff intended for config.json that will make them integrate properly. An example is ROUTING_OBSTRUCTIONS (which should instead be GRT_OBS for OpenLane 1) which might not otherwise be obvious to the user: https://github.com/efabless/caravel_user_sram/blob/781c046d6c4e91d6fa1c28fa0aa25fee0a3754ad/openlane/SRAM_1024x32/config.json#L60-L66
config.json
ROUTING_OBSTRUCTIONS
GRT_OBS
For OL1 & OL2, can these be managed another way, instead of via explicit config.json entries? e.g. Keepouts in GDS or LEF, or some sort of dynamic config?
Some IPs might require a lot of stuff intended for
config.jsonthat will make them integrate properly. An example isROUTING_OBSTRUCTIONS(which should instead beGRT_OBSfor OpenLane 1) which might not otherwise be obvious to the user: https://github.com/efabless/caravel_user_sram/blob/781c046d6c4e91d6fa1c28fa0aa25fee0a3754ad/openlane/SRAM_1024x32/config.json#L60-L66For OL1 & OL2, can these be managed another way, instead of via explicit
config.jsonentries? e.g. Keepouts in GDS or LEF, or some sort of dynamic config?