Makefile Targets
The ruckus Makefile chain provides a small set of PHONY targets that
all per-target Makefiles inherit via
include $(TOP_DIR)/submodules/ruckus/system_vivado.mk.
Per-Target make Entry Points
From inside firmware/targets/<Board>/<Target>/:
Command |
Effect |
|---|---|
|
Default target. Runs synthesis + implementation + |
|
Same as |
|
Default — explicit name; alias for |
|
Versal-class targets only — produces a |
|
Open the existing Vivado project in interactive mode. Use after a
prior batch |
|
Launch Vivado simulator with the target’s testbench
( |
|
Delete |
|
Generate/regenerate Vivado IP from |
Per-Target Makefile Variables
Each target’s Makefile (e.g.
firmware/targets/XilinxVariumC1100/XilinxVariumC1100DmaLoopback/Makefile)
exports a small set of variables that drive the ruckus inclusion:
Variable |
Meaning |
|---|---|
|
Xilinx part number. Required. Per-board constant —
e.g. |
|
Parallel-synthesis worker count. Most targets use 8; some heavy targets set 1 to reduce peak memory. |
|
Path to |
|
Inherited from |
|
Inherited from |
Top-Level firmware/Makefile
firmware/Makefile runs builds in parallel across a curated set of
“production” targets — used by the release pipeline. For day-to-day
development, cd into the specific target directory and run make
there.
Image Generation Flags
The following environment variables control output artefact format
(defaults from ruckus/system_vivado.mk):
Variable |
Default |
Effect |
|---|---|---|
|
1 |
Copy |
|
0 |
Also produce |
|
0 |
Produce |
|
0 |
Produce |
|
1 |
Run promgen and copy |
|
0 |
Also produce |
Set any flag to 1 (or 0) in your environment before invoking
make to override:
GEN_MCS_IMAGE_GZIP=1 make