Kuiper image does not extend to the capacity of SD Card dac_fmc_ebz on a10soc - failing with timing violation failure.

Util_adcfifo (Update interfaces for the asymetric memory) Spi_engine (Add pulse_width and pulse_period registers) *Quartus Standard 18.1 is used only for Cyclone5 projects (c5soc and de10nano), arria10soc+cn0506_rgmii and arria10soc+fmcomms2Īxi_spi_engine, jesd204 (Multiple fixes and improvements)Īxi_ad6676, axi_ad9963, axi_adc_decimate, axi_adc_trigger, axi_generic_adc, (Fixes and improvements)Īxi_ad7616 (Update ad_edge_detect port names)Īxi_ad9739a (Add tristate option for ad_serdes_out)Īxi_dac_interpolate (Export signals indicating the rate)

Suporting ad908x on multiple carriers and add examples built with different JESD configurations: *Quartus Standard 20.1 is used only for Cyclone5 projects (c5soc and de10nano) Also, for Arria10 SOC sysid value is not returned from dmesg log ( dmesg | grep sysis) This is expected since HDL projects are not recompiled if there are no changes that affects them. SysID value returned by dmesg during booting may be older that the last commit from this branch. The solution is to delete the wrong created file if there exists (/usr/share/X11//nf is created by enable_dummy_display.sh and /etc/X11/nf is created by fix_x11.sh). Running the one for zynq on a zynqmp device or vice versa will broke video output. There are two scripts that can be run in Kuiper terminal: enable_dummy_display.sh - which is used to create a display for zynq based boards and fix_x11.sh - which is used to create display for zynqmp based boards. On Arria10 SOC with cn0506_mii, IPs are not assigned on both ports even if dhcp is enabled. Projects removed from 20212_r2 release please use them from previous release or master:Ģ021_R2 will be the last release for next projects: Also, for Arria10 SOC sysid value is expected to not be returned. This is expected since HDL projectsĪre not recompiled if there are no changes that affects them. (/usr/share/X11//nf is created by enable_dummy_display.sh and /etc/X11/nf is created by fix_x11.sh). The solution is to delete the wrong created file if there exists Zynqmp device or vice versa will broke video output. There are two scripts that can be run in Kuiper terminal: enable_dummy_display.sh - which is used to create aĭisplay for zynq based boards and fix_x11.sh - which is used to create display for zynqmp based boards. To get it, is enough to run 'adi_update_boot.sh' from inside a 2022_r2 Kuiper. The problem is already fixed and is part of latest boot files. If there is rgmii, zynqmp platform or ports are not both connected, the setup will boot fine. The workaround is to boot it with GRHD files provided by Xilinx (doesn't matter if it's petalinux or yocto), and after is booting to type nextĭate -s '$(wget -qSO -max-redirect=0 2>&1 | grep Date: | cut -d' ' -f5-8)Z' hwclock -systohc poweroffĪfterwards, it should boot also with Kuiper official image.Ĭn0506 mii/rmii hang during booting, on zynq platforms, if both ethernet ports are connected to the network. Versal based carriers (vck190) won't boot with 2022_r2 Kuiper image Projects removed (you can find pre-built files in previous releases or main):Īd9434_fmc on zc706 (the project still remained in main)Ĭn0501 on coraz7s (the project still remained in main)ĭac_fmc_ebz on a10soc (the project still remained in main)Īdrv9361z7035 and adrv9364z7020 on ccpackrf 3. New / removed projects in 2022_r2 Release: *Quartus Standard 21.1 is used only for Cyclone5 projects (C5SOC Kit and DE10 nano) 2. Supported tools version for this release are:

Xilinx vivado 2017.4 download