Configuration
Kuiper-gen’s build process is controlled by settings defined in the config
file located in the root of the repository. This file contains bash variables
that determine what features to include and how to build the image.
How to Configure
To modify the configuration:
Edit the
config
file in your preferred text editorSet option values to
y
to enable features orn
to disable themModify other values as needed for your build
Save the file and run the build script
After the build completes, you can find a copy of the used configuration in
the root directory (/
) of the built image.
You can also set the number of processors or cores you want to use for
building by adding NUM_JOBS=[number]
to the config file. By default,
this uses all available cores ($(nproc)
).
System Configuration
These options control the fundamental aspects of your Kuiper image:
Option |
Default |
Description |
---|---|---|
|
|
Target architecture: |
|
|
Debian version to use (e.g., |
Build Process Options
These options control how the Docker build process behaves:
Option |
Default |
Description |
---|---|---|
|
|
Keep the Docker container after building ( |
|
|
Name of the Docker container. Useful for building multiple images in parallel |
|
|
Download source files for all packages in the image ( |
Desktop Environment
Option |
Default |
Description |
---|---|---|
|
|
Install XFCE desktop environment and X11VNC server ( |
ADI Libraries and Tools
These options control which ADI libraries and tools are included in the image:
Option |
Default |
Description |
---|---|---|
|
|
Install Libiio library ( |
|
(see config file) |
CMake build arguments for Libiio |
|
|
Git branch to use for Libiio |
|
|
Install Pyadi library ( |
|
|
Git branch to use for Pyadi |
|
|
Install Libm2k library ( |
|
(see config file) |
CMake build arguments for Libm2k |
|
|
Git branch to use for Libm2k |
|
|
Install Libad9166 library ( |
|
(see config file) |
CMake build arguments for Libad9166 |
|
|
Git branch to use for Libad9166 |
|
|
Install Libad9361 library ( |
|
(see config file) |
CMake build arguments for Libad9361 |
|
|
Git branch to use for Libad9361 |
|
|
Install GRM2K ( |
|
(see config file) |
CMake build arguments for GRM2K |
|
|
Git branch to use for GRM2K |
|
|
Install ADI Linux scripts ( |
|
|
Git branch to use for Linux scripts |
ADI Applications
These options control which ADI applications are included in the image:
Option |
Default |
Description |
---|---|---|
|
|
Install IIO Oscilloscope ( |
|
(see config file) |
CMake build arguments for IIO Oscilloscope |
|
|
Git branch to use for IIO Oscilloscope |
|
|
Install IIO FM Radio ( |
|
|
Git branch to use for IIO FM Radio |
|
|
Install FRU tools ( |
|
|
Git branch to use for FRU tools |
|
|
Install JESD Eye Scan GTK ( |
|
(see config file) |
CMake build arguments for JESD Eye Scan GTK |
|
|
Git branch to use for JESD Eye Scan GTK |
|
|
Install Colorimeter ( |
|
|
Git branch to use for Colorimeter |
|
|
Install Scopy ( |
Non-ADI Applications
These options control which non-ADI applications are included in the image:
Option |
Default |
Description |
---|---|---|
|
|
Install GNU Radio ( |
Boot Files Configuration
These options control which boot files are included in your image:
Option |
Default |
Description |
---|---|---|
|
|
Include Raspberry Pi boot files ( |
|
|
Install Zynq architecture boot files ( |
|
|
Install ZynqMP architecture boot files ( |
|
|
Install Versal architecture boot files ( |
|
|
Install Arria10 architecture boot files ( |
|
|
Install Cyclone5 architecture boot files ( |
Architecture to Hardware Mapping:
Architecture |
Hardware Platform Examples |
---|---|
|
ZedBoard, ZC702, ZC706, Cora Z7s, ADRV9361-Z7035, ADRV9364-Z7020 |
|
ZCU102, ADRV9009-ZU11EG, Jupiter SDR |
|
VCK190, VPK180 |
|
Arria10 SoC Development Kit |
|
Cyclone 5 SoC Kit, DE10-Nano, Arradio board |
Hardware Targeting Configuration
These options configure your image for specific hardware during the build process:
Option |
Default |
Description |
---|---|---|
|
(empty) |
Configure which ADI evaluation board project the image will run. When set, the image will be pre-configured for this specific project. |
|
(empty) |
Configure which carrier board the image will boot on. Used together
with |
Note: Setting ADI_EVAL_BOARD
and CARRIER
is optional. You can leave
these empty and configure your hardware later using the runtime
configure-setup.sh
script. See Hardware Configuration for details.
Platform-Specific Packages
These options add platform-specific software packages beyond the basic boot files:
Option |
Default |
Description |
---|---|---|
|
|
Install Raspberry Pi specific packages ( |
Customization
Option |
Default |
Description |
---|---|---|
|
(empty) |
Path to a custom script inside the adi-kuiper-gen directory to run during build for additional customization |