Comments (2)
Appreciate you reaching out. I think this does need some planning and scoping. E.g., is the intention to create RTL from a bd file or are you looking at some kind of automatic packaging as well? It's been a while since I last used this flow myself so my memory of the details are a bit rusty, but I think some people are using FuseSoC/Edalize with their own bd files and adding some custom tcl to do the RTL generation on the fly. Let's iterate on this so that I understand the use case a bit better.
from edalize.
Our use-case doesn't involve BDs specifically, but rather automatically packaging our IPs so users can generate XCIs.
As a specific example: we have a device we communicate with over a high-speed serial link, and we have the top-level for this device and the IP to communicate with it. Both managed by FuseSoC. Workflow-wise:
- For the top-level, the workflow is good—FuseSoC can automatically produce the bitstream for us and flash it
- For the IP, to produce an archived packaged IP, we have to get FuseSoC to produce its scratch directory containing all the RTL, manually update the
component.xml
using the Vivado GUI, enable the option to produce an archive, then click the right buttons in the GUI to produce the archive
The IP itself consists of a number of our internal FuseSoC cores. Ideally this is the form we'd package them in, but there are two obstacles to this: (1) our users don't use FuseSoC, and (2) our internal cores are generically named, so we can't easily make sure there won't be a conflict between module names.
By default, FuseSoC has most of the information we copy over into the IP packager. Adding the rest as extra properties in the .core
file isn't a hassle. But what it doesn't nicely support at the moment is a flow that feeds this information into Vivado. I'll be honest at this point and say I haven't yet figured out the exact details, but I imagine most of it is driven through the (mildly undocumented) ipx::*
Tcl commands. Maybe there'll be some XML generation in there.
Once we have the archive, our users can put its contents in their IP repo and specialise our parameterised IP using create_ip
as they would for anything out of the Vivado IP catalogue.
So my rough thinking on how this breaks down is:
- Edalize:
- Expose places to put all the metadata (VLNV, compatibility, IP categories, etc.)
- Interpret tags on files to produce the correct directory structure for synth vs. sim filesets
- Drive Vivado to produce the
component.xml
that describes the package + the archived package
- FuseSoC:
- Do its usual thing of sourcing all the files/dependencies for the cores
- Support this packaging flow, with a mix of automatic (e.g. VLNV) and user-defined data (tags, etc.) passed in Edalize
- Poke Edalize in the right way to run its packaging flow
Is there anything I've left unclear there?
from edalize.
Related Issues (20)
- Xcelium: file list HOT 1
- Modelsim missing in tools
- Simulating Vivado IPs (xci, bd) HOT 4
- `make_libraries_directories` on Windows fails due to `mkdir -p` HOT 3
- GHDL Support for cocotb simulation flow HOT 2
- Vars do not survive Edaflow
- Add update_compile_order to vivado workflow HOT 1
- QSys Pro 23 files are not processed correctly by the filter HOT 4
- Jinja2 issue witth edarool loader HOT 4
- Vivado flow not re-run when Verilog parameter is changed HOT 3
- Yosys: `configure_main` should check for "file_type" in fileset, or provide a default
- Incorrect toplevel name used when loading EDIF netlist in Vivado
- How to read an EDIF netlist into Vivado that isn't the toplevel?
- Not possible to fully suppress stdout in edatool API?
- Passing Verilog string parameters with quotes
- edalize/flows/edaflow.py # Yeah, I know. It's just a temporary hack HOT 1
- Symbiflow tool doesn't pass Yosys parameters when using VPR as PnR HOT 1
- Error using f4pga flow for Xilinx
- Edatool.tool_options.get() returns string "None" rather than NoneType
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from edalize.