Skip to content

Releases: analogdevicesinc/adi-kuiper-gen

2023_R2

21 Nov 13:24
a10c8bc
Compare
Choose a tag to compare

Changelog

1. Major updates:

  • Kuiper base image: "bulleye"
  • Kernel version: 6.1
  • Scopy: 'v1.4.1' tag
  • Libm2k: 'v0.8.0' tag
  • Pyadi-iio: 'v0.0.18' tag
  • GNU Radio '3.8.2' version

2. Known issues:

  1. Writing SD cards with Balena Etcher(Windows) or Disk Image Writer(Ubuntu) may give an error at the end.
    Even so, SD cards should be written properly, so you can ignore it.
    As alternatives you can use Win32 Disk Imager (version 1.0) from Windows or 'dd' command from linux systems.

  2. Video output might not work on Xilinx platforms
    Please check the list of monitors supported by Xilinx

  3. Jesd Eye Scan application doesn't work
    There is an error 'Failed to read JESD204 device…' when 'Start' button from application UI is pushed.
    Please use a previous Kuiper Linux release until we will publish a fix.

  4. Colorimeter Demo - CN0363 application doesn't work
    There is error “Device not found: [Errno 13] Permission denied…” show in Colorimeter Demo.
    Please use a previous Kuiper Linux release until we will publish a fix.

  5. No data in buffer for cn0540
    The issue is reproducible only when sampling frequency is set from a lower to a higher value.
    Please use a previous Kuiper Linux release until we will publish a fix.

  6. AD9081 with 122.88 MHz oscillator doesn't boot
    Evaluation Board AD9081 vcxo122p88 on ZCU102 doesn't boot due to a SPI issue.
    Please use a previous Kuiper Linux release until we will publish a fix.

  7. “Segmentation Fault” issue on all evaluation boards that use ad7768 device
    Evaluation boards ad7768, ad7768-4 and cn0579 give “Segmentation fault” error when running 'iio_info' or other libiio commands.
    A fix is already in PR 2632. Once the PR is merged, you can update boot files
    to latest (by running adi_update_boot.sh in Kuiper terminal) or wait for the fix to be part of next patch.

3. Reference links:

2022_R2 Patch2

02 Jul 15:12
Compare
Choose a tag to compare
  1. Changelog
    The single difference compared with 2022_R2 Patch 1 is that it uses pyadi-iio from latest main (commit 4352b32f9) instead of 'v0.0.16' tag. This contains adrv9002 API version 68.13.7.
    Only adi-kuiper-gen and linux repositories have release tag 2022_r2 Patch2, the rest of components, since have not been updated, remained with 2022_r2 Patch1 tag.

  2. Versions used (the same as for 2022_R2 and 2022_R2 Patch1 releases):
    Kuiper base image: "bullseye"
    Kernel: 5.15
    Scopy: v1.4.1
    Libm2k: v0.8.0
    Gnuradio 3.8.2

  3. Known issues (the same as for 2022_R2 and 2022_R2 Patch1 releases):
    a. Video output might not work.
    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. Running the one for zynq on a zynqmp device or
    vice versa will broke video output.
    The solution is to delete the wrong created file if there exists (/usr/share/X11/xorg.conf.d/xorg.conf is
    created by enable_dummy_display.sh and /etc/X11/xorg.conf is created by fix_x11.sh).

    b. Writing SD cards with Balena Etcher (version 1.7.9) from Windows10 or Ubuntu Disk Image Writer from Ubuntu may give an error at the end, when validating SD card.

    Even so, SD card should be written properly, As alternatives you can use Win32 Disk Imager or 'dd' command from linux systems.

    c. Versal based carriers (vck190) might not boot with 2022_r2 Patch1 image.

    The problem appears because some revisions of VCK190 or VPK may have the date/time set randomly or in 64bit format. To make them boot, it is enough to overwrite the date, following next steps:

    • when booting the board, hit any key to go intou-bootmenu
    • type mw F12A0000 6613DE3D (this value is hexa of the date from Unix Converter webpage)
    • continue booting

    Another workaround is to boot it with kuiper2.0 basic image 64bits (still in development phase), and after is booting to type next commands:
    date -s "$(wget -qSO --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z" & hwclock --systohc in terminal.
    After reboot, you should be able to boot also with Kuiper official image.

  4. Reference links:
    Wiki Documentation
    2022_R2 Patch2 SD Card image
    Support
    HDL repository
    HDL Testbenches repository
    HDL 2022_r2 Patch1 Release Notes
    Linux repository
    Linux 2022_R2 Patch2 Release Notes
    NO-OS repository

2022_R2 Patch1

10 Apr 09:19
Compare
Choose a tag to compare
  1. Changelog
    Different bugs fixes.

  2. Versions used:
    Kuiper base image: "bulleye"
    Kernel: 5.15
    Scopy: v1.4.1
    Libm2k: v0.8.0
    Pyadi-iio: v0.0.16
    Gnuradio 3.8.2

  3. Known issues:
    a. Video output may not work.
    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. Running the one for zynq on a zynqmp device or
    vice versa will broke video output.
    The solution is to delete the wrong created file if there exists (/usr/share/X11/xorg.conf.d/xorg.conf is
    created by enable_dummy_display.sh and /etc/X11/xorg.conf is created by fix_x11.sh).

    b. Writing SD cards with Balena Etcher (version 1.7.9) from Windows10 or Ubuntu Disk Image Writer from Ubuntu may give an error at the end, when validating SD card.

    Even so, SD card should be written properly, As alternatives you can use Win32 Disk Imager or 'dd' command from linux systems.

    c. Versal based carriers (vck190) might not boot with 2022_r2 Patch1 image.

    The problem appears because some revisions of VCK190 or VPK may have the date/time set randomly or in 64bit format. To make them boot, it is enough to overwrite the date, following next steps:

    • when booting the board, hit any key to go intou-bootmenu
    • type mw F12A0000 6613DE3D (this value is hexa of the date from Unix Converter webpage)
    • continue booting

    Another workaround is to boot it with GRHD files provided by Xilinx, and after is booting to type next commands:
    date -s "$(wget -qSO --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z" & hwclock --systohc in terminal.
    After reboot, you should be able to boot also with Kuiper official image.

  4. Reference links:
    Wiki Documentation
    2022_R2 Patch1 SD Card image
    Support
    HDL repository
    HDL Testbenches repository
    HDL 2022_r2 Patch1 Release Notes
    Linux repository
    Linux 2022_R2 Patch1 Release Notes
    NO-OS repository

2022_R2

21 Dec 13:20
Compare
Choose a tag to compare

Changelog

1. Major updates:

  • Kuiper base image: "bulleye"
  • Kernel: 5.15
  • Scopy: v1.4.1
  • Libm2k: v0.7.0
  • Pyadi-iio: v0.0.16
  • Gnuradio 3.8.2

2. Known issues:

  1. Video output may not work.
    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. Running the one for zynq on a zynqmp device or
    vice versa will broke video output.

    The solution is to delete the wrong created file if there exists (/usr/share/X11/xorg.conf.d/xorg.conf is
    created by enable_dummy_display.sh and /etc/X11/xorg.conf is created by fix_x11.sh).

  2. Writing SD cards with Balena Etcher (version 1.7.9) from Windows10 or Ubuntu Disk Image Writer from Ubuntu may give an error at the
    end, when validating SD card.

    Even so, SD card should be written properly, As alternatives you can use Win32 Disk Imager or 'dd' command from linux systems.

  3. Versal based carriers (vck190) won't boot with 2022_r2 Kuiper image.

    The workaround is to boot the hardware with GRHD files provided by Xilinx (doesn't matter if it's petalinux or yocto), and after is booting
    to type next commands:

  date -s "$(wget -qSO --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z"
  hwclock --systohc
  poweroff

Afterwards, it should boot also with Kuiper official image.

  1. cn0506 mii/rmii hang during booting, on zynq platforms, if both ethernet ports are connected to the network.
    If there is rgmii, zynqmp platform or ports are not both connected, the setup will boot fine.

    The problem is already fixed and is part of latest boot files. To get them, is enough to boot Kuiper 2022_r2 on any platform, connect it to
    the internet and run 'adi_update_boot.sh' from a terminal.

3. Reference links:

Wiki Documentation
SD Card image
Support
HDL repository
HDL Testbenches repository
HDL 2021_r2 Release Notes
Linux repository
Linux 2021_R2 Release Notes
NO-OS repository

2021_R2

19 Apr 12:14
Compare
Choose a tag to compare

Changelog

1. Major updates:

  • Kuiper base image: "bulleye" ( Debian Release shedule )
  • Kernel: 5.10
  • Scopy: v1.4.1
  • Libm2k: v0.7.0
  • Pyadi-iio: v0.0.13
  • Gnuradio 3.8.2 (installed, not built)

2. Known issues:

  1. Video output may not work.

    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. Running the one for zynq on a zynqmp device or vice versa will broke video output. The solution is to delete the wrong created file if there exists (/usr/share/X11/xorg.conf.d/xorg.conf is created by enable_dummy_display.sh and /etc/X11/xorg.conf is created by fix_x11.sh).

  2. Kuiper image does not extend to the capacity of SD Card

    Workaround: This happens when first use of a new created SD card is on a development board. If you see that the root fs partition is not extended to the SD card capacity minus 1 GB (fixed size of boot partition), just open a terminal and type:
    > raspi-config --expand-rootfs

  3. Keyboard layout may revert back to English(UK) - default one. This is expected behavior in Raspberry Pi OS ( you can find the whole discussion here).

  4. Writing SD cards with Balena Etcher (version 1.7.9) from Windows10 or Ubuntu Disk Image Writer from Ubuntu 20.04/ 22.04 may give an error at the end, on validating SD card.
    Even so, SD cards should be written properly, so you can ignore it. As alternatives you can use Win32 Disk Imager (version 1.0) from Windows or 'dd' command from linux systems.

3. Reference links:

Wiki Documentation
SD Card image
Support

HDL repository
HDL Testbenches repository
HDL 2021_r2 Release Notes
Linux repository
Linux 2021_R2 Release Notes
NO-OS repository

2021_R1

10 Aug 08:39
Compare
Choose a tag to compare

Changelog

1. Major updates:

  • Updated Kuiper from "buster" to "bulleye" ( Debian Release shedule )
  • Updated Scopy to v1.4.0
  • Updated Libm2k to v0.6.0
  • Switched from building gnuradio 3.8.0 to installing gnuradio 3.8.2 and fix iio.

2. Known issues:

  1. Video output may not work. 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. Running the one for zynq on a zynqmp device or vice versa will broke video output. The solution is to delete the wrong created file if there exists (/usr/share/X11/xorg.conf.d/xorg.conf is created by enable_dummy_display.sh and /etc/X11/xorg.conf is created by fix_x11.sh).

  2. Kuiper image does not extend to the capacity of SD Card

    Workaround: This happens when first use of a new created SD card is on a development board. If you see that the root fs partition is not extended to the SD card capacity minus 1 GB (fixed size of boot partition), just open a terminal and type:
    > raspi-config --expand-rootfs

  3. Arria10 SOC, Cyclone5 SOC and DE10 Nano boards will automatically start-up few seconds after “poweroff” commmand is given and the board shuts down.

    Workaround: you can disable watchdog from u-boot, with the risk that boot process to hang if there are issues.

  4. Development boards may have a big delay (about 1.5 minutes) when are powered off (“poweroff”, “reboot” of “shutdown” commands).
    Workaround: modify “DefaultTimeoutStopSec” in file “/etc/systemd/system.conf” from 90 sec to 10 sec (or any another smaller value), killing in this way all hanging processes after 10 seconds and begin “poweroff” procedure.

  5. ADI Diagnostic Report generate an empty report when is ran from System Tools Menu.
    Workaround: run “adi_diagnostic_report” command from terminal.

  6. Keyboard layout may revert back to English(UK) - default one. This is expected behavior in Raspberry Pi OS ( you can find the whole discussion here).

3. Reference links:

[Wiki Documentation]repository][https://wiki.analog.com/resources/tools-software/linux-software/adi-kuiper_images/release_notes]
SD Card image
Support

HDL repository
HDL Testbenches repository
HDL 2021_r1 Release Notes

Linux repository
Linux 2021_R1 Release Notes

NO-OS repository

2019_R2: stage6: aditof-sdk: Fix process using 100% of cpu core

20 Aug 07:31
Compare
Choose a tag to compare

1. Major updates:

i. First partition (boot partition) :

  • on boot partition should exist by default boot files for booting on RPI
  • folder structure for projects has been changed in next way:
    • projects that are using the same BOOT.BIN will have subfolders with all supported DTB files. Exceptions:
      • zcu102 with adrv9002 projects has two versions of BOOT.BIN (CMOS / LVDS interfaces) and there are two device trees file (zynqmp-zcu102-rev10-adrv9002 and zynqmp-zcu102-rev10-adrv9002-rx2tx2). All combinations between those should work.
      • adrv9009-zu11eg with fmcomms8 has one device tree for simple project and another two for multisom ('primary' and 'secondary')

ii. Second partition (rootfs partition)

iii. Third partition (altera partition) :

  • on altera partition should be written the preloader for booting on Cyclone5 SOC, de10nano or Arria10 SOC.

2. Reference links: