This version is outdated by a newer approved version.
This version (10 Jan 2022 15:47) was approved by Stefan-Robert Raus.
This version (10 Jan 2022 15:47) was approved by Stefan-Robert Raus.This is an old revision of the document!
Table of Contents
HDL and Linux projects are build whenever there are new commits in HDL or Linux repositories. Output boot files are structured in folders as they would be on SD card, and archived.
Boot partition files
- MD5 checksum can be verified here
- It is recommended to use master boot files only if you really need them (for example features that are not part of any release yet) since the files may not be always in a good state. Check Latest release for most recent tested boot files.
- Inside downloaded archive is a ReadMe.txt file describing what files you need to copy on boot partition root depending on your hardware setup, and VERSION.txt file containing build dates and git commits.
Microblaze images
- It is recommended to use master microblaze images only if you really need them (for example features that are not part of any release yet) since the files may not be always in a good state. Check Latest microblaze released images for most recent and tested images.
- Inside every archive there is system_top.bit, simpleImage.<project name>.strip and a script to program it.
Nios2 images
- It is recommended to use master nios2 images only if you really need them (for example features that are not part of any release yet) since the files may not be always in a good state. Check Latest nios2 released images for most recent and tested images.
- Inside every archive, there is zimage, <project name>.sof and a script to program it.
NO-OS files
- Inside every archive there are different configurations <project name>.elf.
resources/tools-software/linux-software/adi-kuiper_images/master.1641826041.txt.gz · Last modified: 10 Jan 2022 15:47 by Stefan-Robert Raus