Visit this page to download the release files:
gemma4-on-FPGA is a release bundle for running Gemma-based inference on a Xilinx Kria KV260 board.
It is built for users who want a fixed set of files that work together. The bundle includes:
- FPGA bitstream files
- split binary parts
- tokenizer files
- hash files
- receipt files
- Verilog and SystemVerilog source files
- release and provenance documents
This package is meant for an edge device setup where the FPGA does the compute work and the ARM side handles control and setup.
Before you start, make sure you have:
- a Windows PC
- an internet connection
- enough free storage for the download
- a USB drive or SD card if your release package uses one
- a supported FPGA target such as the KV260 kit
If you are only downloading the release bundle on Windows, you do not need to build anything.
Follow these steps in order:
- Open the GitHub Releases page.
- Find the latest release at the top of the page.
- Download the release asset for your target board.
- Save the file to a folder you can find again, such as
DownloadsorDesktop. - If the release comes as a compressed file, right-click it and choose Extract All.
- Open the extracted folder.
- Read the included release file or checklist before you copy anything to the board.
- Copy the bundle files to the storage media or board location described in the release notes.
- Connect the KV260 to power, display, and network if the release expects them.
- Start the board using the steps in the release package.
If your download includes a Windows tool, run that file after extraction and follow the prompts on screen.
The release bundle is organized for stable deployment and checks.
You may see folders and files like these:
for_other_fpgas/.bitfile for FPGA logic- split
.binparts - contract file
- tokenizer
- hash files
- anchoring receipts
rtl/- hardware source files
- formal files
- constraints
RELEASE_CHECKLIST.mdMODEL_PROVENANCE.mdLICENSENOTICE
The names help keep the hardware, model data, and checks in one place.
The KV260 is a good fit for this project because it combines:
- an ARM control processor
- FPGA programmable logic
- Linux support
- camera input support in the kit ecosystem
That makes it useful for edge systems where data comes in from a camera and goes into inference on the same device.
Check these items first:
- the download finished without errors
- the folder contains the release assets
- the files match the names in the release notes
- the board you use matches the target in the bundle
- you have followed the release checklist
If the release includes hash files, use them to confirm the files match the published values.
A common setup flow looks like this:
- Download the release from GitHub.
- Extract the files on your Windows PC.
- Review
RELEASE_CHECKLIST.md. - Review
MODEL_PROVENANCE.md. - Copy the required files to the target storage.
- Boot the KV260.
- Load the FPGA bundle.
- Start inference from the provided launch steps.
If the release uses a helper script, run only the script included in the bundle.
The bundle includes integrity files for a reason.
Use them to confirm:
- the FPGA bitstream is the right one
- the model files match the release
- the split binary parts belong together
- no file was changed during transfer
If a file name does not match the checklist, stop and compare it with the release page.
Use this file as your step list for setup and transfer.
Use this file to review the model source, file chain, and release record.
Use these files to review the use terms and required notices.
This project targets FPGA-based edge inference.
That means:
- the control side runs on the ARM CPU
- the parallel compute side runs in programmable logic
- the deployment uses fixed files, not a live cloud service
- the system can run at the edge, close to the data source
The KV260 kit is useful when you want a camera-to-inference path.
A common edge setup is:
- camera input
- board capture
- FPGA inference
- output on the local device
This fits systems that need local processing and low delay.
The rtl/ folder has the hardware source files.
Use it if you want to:
- review the logic design
- study the constraints
- check the formal files
- understand how the FPGA side is built
You do not need to open these files to use the release bundle as an end user.
You can keep the files in a simple layout like this:
Downloads\gemma4-on-FPGA\Downloads\gemma4-on-FPGA\release\Downloads\gemma4-on-FPGA\docs\
This helps you keep the release files, documents, and copied target files separate.
Visit the release page to download the bundle
After you download the release, check:
- file size
- folder names
- release version
- any setup text in the package
- any README or checklist file in the archive
If the bundle contains more than one part, keep all parts in the same folder.
This repository is tagged for work in:
- edge AI
- FPGA
- Gemma
- quantization
- Xilinx
- KV260
- NPU
- Mamba
- base-l2
- HDC
- kan
These topics help describe the release scope and target system
For a non-technical user, the shortest path is:
- Open the release page.
- Download the latest bundle.
- Extract the files.
- Read the checklist.
- Copy the files to the target device.
- Start the board using the release steps.