Libero - Add flexible TCL script hooks #268
Conversation
|
Ping @olofk ... News on this? |
carlosedp
force-pushed
the
tclhooks
branch
2 times, most recently
from
5b68802
to
d640d88
Compare
|
I'll probably have to rebase this once #274 is merged. |
I think that it will be quite painless, I have tried combining them and got no merge conflicts. |
carlosedp
force-pushed
the
tclhooks
branch
2 times, most recently
from
8f8bc13
to
aa98950
Compare
This allow adding TCL scripts on pre-synthesize, pre-pnr and
pre-bistream generation for the Libero backend.
In the .core file, this would be defined like:
```yaml
polarfireeval:
files:
- rtl/corescore_polarfire_eval_clock_gen.v: { file_type: verilogSource }
- rtl/corescore_polarfire.v: { file_type: verilogSource }
- data/polarfire_eval.pdc: { file_type: PDC }
- data/script_pre_synth.tcl: { file_type: tclSourcePresynth }
- data/script_pre_pnr.tcl: { file_type: tclSourcePrepnr }
- data/script_pre_bitstream.tcl: { file_type: tclSourcePrebistream }
```
Signed-off-by: Carlos de Paula <me@carlosedp.com>
|
Ping @olofk ... :) |
|
I'm not super excited about introducing these new file types but I understand the need to distinguish between these. My first question would be how Libero itself handles this. Is there some built-ink hook API we can use? More long-term I see a need in other flows as well for specifying which tool in a toolchain that should consume particular files. To solve the general problem I think we need to introduced custom attributes to files in core description files. In this case it could look something like But if this PR solves an immediate need I could be convinced to merge it with the expectation that these file types might be deprecated in a not too distant future |
This allow adding TCL scripts on pre-synthesize, pre-pnr and
pre-bistream generation for the Libero backend.
In the .core file, this would be defined like:
Multiple files of each kind could be used.
Signed-off-by: Carlos de Paula me@carlosedp.com