OpenROAD complete backend with nangate45 #608
Conversation
vlsi/Makefile
Outdated
| HAMMER_EXEC ?= ./example-vlsi | ||
| INPUT_CONFS ?= $(if $(filter $(tech_name),nangate45),\ | ||
| example-nangate45.yml,\ | ||
| example.yml) |
There was a problem hiding this comment.
Perhaps we should name eaxmple.yml example-asap7.yml?
| @@ -0,0 +1,144 @@ | |||
| # Technology Setup | |||
| # Technology used is nanagate45 | |||
| vlsi.core.technology: nangate45 | |||
There was a problem hiding this comment.
We might want to separate out the yaml into generic settings and tech specific settings, so we would have an:
example.yml
example-asap7.yml
example-nangate45.yml
And it optionally includes the right pair based on tech_name
vlsi/example-vlsi-nangate45
Outdated
| return True | ||
|
|
||
| class ExampleDriver(CLIDriver): | ||
| def get_extra_par_hooks(self) -> List[HammerToolHookAction]: |
There was a problem hiding this comment.
I think we just have a generic exampleDriver that inspects os.env(tech_name) and includes the get hooks programmatically.
The magic of hammer 🎉
|
I know this is still a draft, but I would appreciate seeing docs associated with this. |
ssteffl
changed the title
| ifneq ($(CUSTOM_VLOG), ) | ||
| OBJ_DIR ?= $(VLSI_OBJ_DIR)/custom-$(VLSI_TOP) | ||
| ifneq ($(CUSTOM_VLOG),) | ||
| OBJ_DIR ?= $(VLSI_OBJ_DIR)/custom-$(VLSI_TOP) |
There was a problem hiding this comment.
Do these spaces line something up? It seems like they unalign these ?= operators.
| @@ -7,21 +11,24 @@ from hammer_vlsi import CLIDriver, HammerToolHookAction | |||
| from typing import Dict, Callable, Optional, List | |||
|
|
|||
| def example_place_tap_cells(x: hammer_vlsi.HammerTool) -> bool: | |||
| x.append(''' | |||
| if x.get_setting("vlsi.core.technology") == "asap7": | |||
There was a problem hiding this comment.
There is a nicer way to do this now but this is ok for the time being.
overview
results