Add Flow API and nextpnr support for Cologne Chip GateMate FPGAs #489
Conversation
olofk
left a comment
olofk
left a comment
There was a problem hiding this comment.
Thanks for this! A few things that need to be fixed and I would appreciate some simple tests also. Looks great otherwise.
|
|
||
| _flow = { | ||
| "yosys": {"fdto": {"arch": "gatemate", "output_format": "json", | ||
| "yosys_synth_options": ["-luttree", "-nomx8"], |
There was a problem hiding this comment.
Are these options strictly needed? We try to avoid hardcoding any options unless necessary since that makes it harder for users to change to another value.
| }}, | ||
| "nextpnr": {"deps": ["yosys"], | ||
| "fdto": {"arch": "gatemate", | ||
| "nextpnr_options": ["--router router2"], |
There was a problem hiding this comment.
Is this option strictly needed? We try to avoid hardcoding any options unless necessary since that makes it harder for users to change to another value.
| "-lib", | ||
| "ccag", | ||
| " ".join(self.tool_options.get("p_r_options", "")), | ||
| "$(NEXTPNR)", |
There was a problem hiding this comment.
I think it's better to just have nextpnr-himbaechel here directly. This allows us to run a containerized version of nextpnr through the EDALIZE_LAUNCHER mechanism like we can do with the other nextpnr versions already.
| commands.add(command, [cfg_target], [synth_out]) | ||
|
|
||
| commands.set_default_target(targets) | ||
| commands.add_var("GMPACK := $(shell which gmpack)") |
There was a problem hiding this comment.
Use gmpack directly. We can use an EDALIZE_LAUNCHER to override the name if we want instead.
2 participants
Cologne Chip GateMate FPGA support is updated from the proprietary p_r tool to nextpnr and migrated from the old Tool API to the Flow API