-
Notifications
You must be signed in to change notification settings - Fork 140
Project Structure
Juan Gonzalez-Gomez edited this page Apr 2, 2024
·
5 revisions
An Apio project consist of the following files:
- apio.ini. This is generated using apio init
-
Constraint file (
.pcf
or.lpf
). There should be exactly one constraint file per Apio project The first constraint file that is found will be used for mapping wires to the physical FPGA pins for apio build -
Verilog source files. All files ending in
.v
will be selected and included in the project automatically. If you don't want to include a Verilog file automatically, name it as.vh
(Verilog Header) to exclude it. If you are using multiple files or including headers above your top module, mark the top module like so:
(* top *)
module my_top_module(
output led_r,
input serial_rxd,
);
....
endmodule
- Optionally, a testbench file ending in
_tb.v
. This file will be excluded by apio build, but become the main module for apio sim.
Note
Have a look at the apio examples package
- Project structure
- Project configuration file (apio.ini)
- apio
- Project Commands:
- Setup commands:
- Utility Commands:
- Downloading the Blinky example
- The apio-examples package: Adding examples
-
Apio packages
- Tools-oss-cad-suite
- Apio examples
- Tools-drivers (Windows)
- Gtkwave (Windows)