Group Actions
Engagement
  • Author Author: narrucmot
  • Date Created: Date Created
  • Views 2462 views
  • Likes 6 likes
  • Comments 8 comments
Related
Recommended

Announcing New PetaLinux 2019.2 BSP for Ultra96-V2

narrucmot

Hi Everyone,

 

Avnet has just released the PetaLinux 2019.2 BSP for the Ultra96-V2 board:

 

This BSP includes working WiFi and access point to ease configuration for connecting to the user's WLAN.  Instructions for this can be found in the Ultra96-V2 Getting Started Guide.

 

This BSP also includes the logic pieces in the programmable logic (PL) fabric to allow it to be used as the basis for a Xilinx Vitis platform to allow users to create custom accelerators or experiment with the provided examples.  There is currently a known issue that Vitis accelerators that require an interrupt may not work correctly, and an update to fix this is currently being developed.  Accelerators like the vector addition example, though, are known to work and can be used as a good way to get started using Vitis.

 

Instructions for how to install this BSP can be found in Xilinx UG1144.

 

Ready-to-boot Linux OS binaries are provided in the pre-built folder of the installed BSP and can be copied and extracted to a micro-SD card.  This Xilinx wiki page has good instructions for preparing a micro-SD card for use with the Ultra96-V2 board.   Once the micro-SD card has been partitioned and formatted copy the boot.bin and image.ub files to the FAT32 partition and extract the rootfs to the ext4 partition:

$ cp BOOT.BIN /path/to/mounted/SD_card_FAT32/.

$ cp image.ub  /path/to/mounted/SD_card_FAT32/.

$ sudo rm -rf /path/to/mounted/SD_card_ext4/* (Only if the partition is not empty.  THIS WILL DELETE ALL THE FILES IN THE EXT4 PARTITION!)

$ sudo tar xvf rootfs.tar.gz -C  /path/to/mounted/SD_card_ext4/.

 

Before ejecting the micro-SD card make sure the file buffers are emptied:

$ sync; sync

$ sudo eject /dev/<SD_card_device> (e.g. /dev/sdf1)

 

Stay tuned for further PetaLinux BSP and Vitis platform updates for the Ultra96-V2 and UltraZed SOMs.

 

Buy Commercial Ultra96-V2Buy Commercial Ultra96-V2

Buy Industrial Ultra96-V2Buy Industrial Ultra96-V2

Parents

  • Ultra96V2 Petalinux v2019.2 fails to build.  The failure happens when petalinux tries to download libelf1_0.176-1_arm64.deb.  Googling I found that the powers that be updated the debian to libelf1_0.176-1.1_arm64.deb.

     

    Alternatively, is there a way to disable the inclusion of arduino and openamp in the Ultra96V2 build?

     

    WARNING: arduino-toolchain-1.0-r0 do_fetch: Failed to fetch URL http://http.us.debian.org/debian/pool/main/e/elfutils/libelf1_0.176-1_arm64.deb;subdir=avrgcc;unpack=false;name=libelf1, attempting MIRRORS if available

    ERROR: arduino-toolchain-1.0-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export GIT_SSL_CAINFO="/opt/Petalinux192/components/yocto/source/aarch64/buildtools/sysroots/x86_64-petalinux-linux/etc/ssl/certs/ca-certificates.crt"; export PATH="/home/bgetz/ultra96v2_oob_2019_2/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/opt/Petalinux192/components/yocto/source/aarch64/layers/core/scripts:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-xilinx-linux:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/recipe-sysroot-native/usr/sbin:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/recipe-sysroot-native/usr/bin:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/recipe-sysroot-native/sbin:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/recipe-sysroot-native/bin:/opt/Petalinux192/tools/xsct/bin:/opt/Petalinux192/tools/xsct/gnu/microblaze/lin/bin:/opt/Petalinux192/tools/xsct/gnu/aarch32/lin/gcc-arm-none-eabi/bin:/opt/Petalinux192/tools/xsct/gnu/armr5/lin/gcc-arm-none-eabi/bin:/opt/Petalinux192/tools/xsct/gnu/aarch64/lin/aarch64-none/bin:/opt/Petalinux192/components/yocto/source/aarch64/layers/core/bitbake/bin:/home/bgetz/ultra96v2_oob_2019_2/build/tmp/hosttools"; export HOME="/home/bgetz"; /usr/bin/env wget -t 2 -T 30 --passive-ftp --no-check-certificate -P /home/bgetz/ultra96v2_oob_2019_2/build/downloads 'http://http.us.debian.org/debian/pool/main/e/elfutils/libelf1_0.176-1_arm64.deb' --progress=dot -v failed with exit code 8, output:

    --2020-04-22 12:59:05--  http://http.us.debian.org/debian/pool/main/e/elfutils/libelf1_0.176-1_arm64.deb

    Resolving http.us.debian.org... 64.50.233.100, 208.80.154.15, 64.50.236.52

    Connecting to http.us.debian.org|64.50.233.100|:80... connected.

    HTTP request sent, awaiting response... 404 Not Found

    2020-04-22 12:59:05 ERROR 404: Not Found.

     

     

     

     

    ERROR: arduino-toolchain-1.0-r0 do_fetch: Fetcher failure for URL: 'http://http.us.debian.org/debian/pool/main/e/elfutils/libelf1_0.176-1_arm64.deb;subdir=avrgcc;unpack=false;name=libelf1'. Unable to fetch URL from any source.

    ERROR: arduino-toolchain-1.0-r0 do_fetch: Function failed: base_do_fetch

    ERROR: Logfile of failure stored in: /home/bgetz/ultra96v2_oob_2019_2/build/tmp/work/aarch64-xilinx-linux/arduino-toolchain/1.0-r0/temp/log.do_fetch.6953

    ERROR: Task (/opt/Petalinux192/components/yocto/source/aarch64/layers/meta-petalinux/recipes-utils/arduino-toolchain/arduino-toolchain_1.0.bb:do_fetch) failed with exit code '1'

    NOTE: Tasks Summary: Attempted 8795 tasks of which 8481 didn't need to be rerun and 1 failed.

     

     

    Summary: 1 task failed:

      /opt/Petalinux192/components/yocto/source/aarch64/layers/meta-petalinux/recipes-utils/arduino-toolchain/arduino-toolchain_1.0.bb:do_fetch

    Summary: There was 1 WARNING message shown.

    Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

    ERROR: Failed to build project

  • in reply to bgetz

    Thanks to Whitney Knitter for solving that.  My problem now is that we are unable to modify the project shipped with the 2019.2 BSP.  There are two PWM IPs in the block diagram that are locked (because they are not in the ip repostiory) and therefore if you modify the design, you cannot generate the bd and get an updated xsa/bit file.  I cannot find the component.xml and source code for this Avnet custom IP in the extracted project from the BSP.  Does anyone know how this is supposed to work?  I did find on the Avnet hdl git repo something that looks close - but hasn't been udpated in over two years and the markdown comments only referent 2017.4 - rather old.

     

    https://github.com/Avnet/hdl/tree/master/IP/PWM_w_Int

     

    Where is the packaged ip repo for the 2019.2 version of the Ultra96v2 BSP?

Comment
  • in reply to bgetz

    Thanks to Whitney Knitter for solving that.  My problem now is that we are unable to modify the project shipped with the 2019.2 BSP.  There are two PWM IPs in the block diagram that are locked (because they are not in the ip repostiory) and therefore if you modify the design, you cannot generate the bd and get an updated xsa/bit file.  I cannot find the component.xml and source code for this Avnet custom IP in the extracted project from the BSP.  Does anyone know how this is supposed to work?  I did find on the Avnet hdl git repo something that looks close - but hasn't been udpated in over two years and the markdown comments only referent 2017.4 - rather old.

     

    https://github.com/Avnet/hdl/tree/master/IP/PWM_w_Int

     

    Where is the packaged ip repo for the 2019.2 version of the Ultra96v2 BSP?

Children