Building a design with FuseSoC¶
The FuseSoC build system pieces together a hardware design from individual cores.
Building a design in FuseSoC means calling a tool flow to produce some output, and execute it. Depending on the target and the tool flow chosen, the build process can do and produce very different things: it could produce a runnable simulation, an FPGA bitstream, or run a static analysis tool to check for common programming errors.
To build a hardware design with FuseSoC two steps are required:
Write one or multiple FuseSoC core description file(s). Read on in this section for information on how to do that.
fusesoc run. FuseSoC is a command-line tool and accessible through the
fusesoccommand. See Running FuseSoC for information on how to use the
Typically, FuseSoC support can be added to an existing design without changes to the directory structure or the source files. The following sections explain how to do it.
The first three sections are recommended reading for all users of FuseSoC. The first section Writing core files is an introduction into core description files and how to write them. The second and third section, Passing options to tools and Dependencies: link cores together for re-use look at how to customize what the (EDA) tools are doing, and how cores can be combined to form a larger system.
The subsequent sections are advanced topics, which are only relevant in some projects.
A full reference documentation on the CAPI2 core file format can be found in the section CAPI2 Reference.
- Writing core files
- Passing options to tools
- Dependencies: link cores together for re-use
- Flags: constraints in dependencies
- Generators: produce and specialize cores on demand
- Hooks: intercept the build process
- VPI Support