Skip to content

2022_R2 Patch2

Compare
Choose a tag to compare
@SRaus SRaus released this 02 Jul 15:12
  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