Wiki

This version (16 Jan 2024 10:38) was approved by Stefan-Robert Raus.The Previously approved version (20 Dec 2023 12:11) is available.Diff

Releases

The HDL is released as git branches. The release branches are created first and then detailed tested before being made official. That is, the existence of a branch does not mean it is a fully tested release. Also, the release branch is tested ONLY on certain versions of the tools and may NOT work with other versions of the tools. The projects that are tested and supported in a release branch are listed here along with the ADI library cores that are used. The branch may contain other projects that are in development, one must assume these are NOT tested and therefore NOT supported by this release.

All HDL pre-built files are provided to download together with linux device trees and kernel images, as a boot partition archive (just replace '2022_r2' in above link with other release name to get specific boot files, ex. 2021_r2). All boot files are also part of released Kuiper images.

Check GitHub Release Notes for each release to see the main changes and links to related documentation.

On the other side, the 'main' HDL branch is used for development and regression testing is ran less often on it. This implies that it may not be always stable. Latest pre-build boot files from main are available here.

Porting a release branch to another Tool version

It is possible to port a release branch to another tool version, though not recommended. The ADI libraries should work across different versions of the tools, but the projects may not. The issues are most likely with the Intel and Xilinx cores. If you must still do this, note the following:

First, disable the version check of the scripts.

The ADI build scripts are making sure that the releases are being run on the validated tool version. It will promptly notify the user if he or she trying to use an unsupported version of tools. You need to disable this check by setting the environment variable ADI_IGNORE_VERSION_CHECK.

Second, make Intel and Xilinx IP cores version changes.

The Intel projects should automatically be changed by Quartus. The Xilinx projects are a bit tricky. The GUI automatically updates the cores, but the TCL flow does NOT. So it may be easier to create the project file with the supported version first, then opening it with the new version. After which, update the TCL scripts accordingly.

The versions are specified in the following format.

add_instance sys_cpu altera_nios2_gen2 16.0 
set sys_mb [create_bd_cell -type ip -vlnv xilinx.com:ip:microblaze:9.5 sys_mb] 

You should now be able to build the design and test things out. In most cases, it should work without much effort. If it doesn't do an incremental update and debug accordingly.

Release Branches

Releases Intel Xilinx Release Notes List of Supported Projects and IP cores
main Quartus Pro 23.2 Vivado 2023.1
hdl_2022_r2 Quartus Pro 22.4 Vivado 2022.2 Release Notes 2022_r2
hdl_2021_r2 Quartus Pro 21.4 Vivado 2021.2 Release Notes 2021_r2
hdl_2021_r1 Quartus Pro 21.2 Vivado 2021.1 Release Notes 2021_r1
hdl_2019_r2 Quartus Pro 19.3 Vivado 2019.1 Release Notes 2019_r2
hdl_2019_r1 Quartus 18.1 Vivado 2018.3 Release Notes 2019_r1
hdl_2018_r2 Quartus 18.0 Vivado 2018.2 Release Notes 2018_r2
hdl_2018_r1 Quartus 17.1.1 Vivado 2017.4.1 Release Notes 2018_r1
hdl_2017_r1 Quartus 16.1 Vivado 2016.4 Release Notes 2017_r1
hdl_2016_r2 Quartus 16.0 Vivado 2016.2 Release Notes 2016_r2
hdl_2016_r1 Quartus 15.1 Vivado 2015.4.2 Release Notes 2016_r1
hdl_2015_r2 Quartus 15.0.2 Vivado 2015.2 Release Notes 2015_r2
hdl_2015_r1 Quartus 14.1 Vivado 2014.4.1 Release Notes 2015_r1
hdl_2014_r2 Quartus 14.0 Vivado 2014.2 Release Notes 2014_r2
hdl_2014_r1 Quartus 14.0 Vivado 2013.4 Release Notes 2014_r1

Navigation - HDL User Guide

resources/fpga/docs/releases.txt · Last modified: 16 Jan 2024 10:38 by Stefan-Robert Raus