iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The Ultra96-V2 has built-in Wi-Fi capability, and Avnet links to PetaLinux BSP resources for the board. But the available official documentation does not establish that a particular PetaLinux 2020.2 BSP archive includes working Wi-Fi configuration or a VNC server. Treat those as features to verify in the exact archive—not as guaranteed parts of the BSP.
This guide separates the documented PetaLinux 2020.2 setup from the additional checks required before relying on wireless networking or remote desktop.
What the Ultra96-V2 and PetaLinux 2020.2 documentation establish
Avnet identifies the Ultra96-V2 as a Zynq UltraScale+ MPSoC ZU3EG board. Its product page lists integrated Microchip Wi-Fi and Bluetooth, 2 GB LPDDR4, uSD configuration memory, USB connectivity, mini DisplayPort, and 12 V DC power. These specifications describe the board; they do not confirm which peripherals a particular Linux image enables. Avnet also marks the Ultra96 V1 and V2 as no longer in production. Avnet Ultra96-V2 product page
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →AMD’s PetaLinux Tools Documentation Reference Guide UG1144, 2020.2 English, released November 24, 2020, describes a board support package (BSP) as a reference design that can include design and configuration files alongside prebuilt hardware and software images. BSPs are obtained separately from the PetaLinux tools installer. AMD points users to each package’s README for BSP-specific details. The guide does not establish the contents of Avnet’s exact 2020.2 archive.
#1 Best Overall
- Development Board N76E003AT20 Development Board System Board Core Board Minimum System Module DIY Electronic
Get the exact BSP and inspect it before building
Avnet’s product page links to PetaLinux BSP resources, but the exact 2020.2 archive revision and its Wi-Fi or VNC contents are not established by that page. Obtain the board-specific package through Avnet’s resource link, then identify the archive’s exact filename and revision. Read its README before applying instructions or assuming it matches another release.
- Confirm that the archive is specifically for the Ultra96-V2 and PetaLinux 2020.2, rather than another board revision or tool release.
- Check the README and project configuration for the machine, hardware design, and any release-specific instructions.
- Inspect root filesystem package selections and kernel configuration for the wireless driver, firmware, network tools, and any VNC implementation.
- Check the device tree and hardware revision information against the actual board.
- Follow the package’s own instructions for writing and booting media. The documented uSD configuration memory does not establish a required card capacity or speed.
Do not infer that Wi-Fi or VNC is included simply because the board has Wi-Fi hardware or because a BSP exists. The exact archive README and configuration are the relevant evidence.
Import hardware into a PetaLinux 2020.2 project
If your workflow requires importing an exported hardware design, AMD documents the petalinux-config --get-hw-description command with the XSA path. UG1144 lists the Ultra96 machine identifier as avnet-ultra96-rev1. This is the documented machine name; it is not proof that any specific BSP archive has been configured correctly for a particular board or design.
- Obtain an XSA that matches the intended hardware design.
- From the PetaLinux project directory, import it with
petalinux-config --get-hw-description <path-to-xsa>, replacing the placeholder with the actual XSA path. - Review the resulting project configuration, including the machine setting
avnet-ultra96-rev1where applicable, and check the auto-configuration and subsystem settings. - Rebuild the project after configuration changes, then use the exact BSP and board instructions to write and boot the resulting image.
AMD explains that hardware import parses hardware details and updates project configuration, including device-tree and kernel/U-Boot configuration according to selected auto-config and subsystem settings. For the release-specific procedure, see UG1144: Steps to Import Hardware Configuration.
Verify Wi-Fi support on the target
Avnet’s board specifications establish Wi-Fi capability, including 802.11b/g/n support, but they do not identify the driver, firmware, network manager, or connection procedure enabled by a particular PetaLinux BSP. Before using wireless networking, confirm those details in the archive and validate them on the target board.
- Determine whether the image includes the required driver and firmware for the board’s wireless hardware.
- Identify the available network configuration tools and whether the intended use is client mode or access-point mode.
- Check how credentials are supplied and stored, and whether the configuration persists across reboot.
- Validate that the selected board revision and device tree match the actual hardware.
Do not treat generic Linux Wi-Fi commands as verified instructions for this board and release. The required commands depend on the packages and configuration present in the exact image.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify VNC support and its security model
The official product and PetaLinux material cited here does not establish that Avnet’s 2020.2 BSP contains a VNC server, which package it uses, or whether it can share a usable graphical session. A remote-desktop setup requires more than installing a server: the display or session backend, startup behavior, authentication, and network exposure all need to be understood.
Recommended Free Tools
- Confirm the VNC package and its dependencies in the BSP configuration or root filesystem.
- Establish which display or desktop session it serves and whether that session exists on the image.
- Determine how the server starts and whether it remains available after reboot.
- Configure and test authentication, and restrict access to an appropriate trusted network rather than exposing the service unnecessarily.
- Validate an actual connection from a client against the target image; package presence alone does not prove a usable remote desktop.
Until those checks are complete, describe VNC as a possible customization, not a feature of the named BSP.
What has and has not been confirmed
Official sources identify the board, its built-in wireless capability, the PetaLinux 2020.2 hardware-import flow, and the Ultra96 machine identifier. They do not establish the contents of the exact Avnet BSP archive or confirm a Wi-Fi connection or VNC session. No build, boot, wireless connection, or remote-desktop session is documented here as tested.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
