Release Notes

The 2019.1 release of theSDAccel™development environment introduces the following enhancements and features.

Alveo™Shell Enhancements

• Support forAlveoU280, built on theXilinx®16 nmUltraScale™architecture with 8 GB of HBM2 of in-package memory capable of 410 GB/s data transfers
• New Queue DMA (QDMA) platform supports low latency direct streaming between host and kernels. The new QDMA shell also offers kernel memory-to-memory direct access (M2M) to share buffers stored in DDR banks without involving orchestration from host
• Newest shells now default toPCIe®64-bit Base Address Registers (BARs)
  • No mixing of 32-bit and 64-bit BARs
  • Extended support of High-end servers with multiple acceleration cards
  • Servers must have BIOS turned on above 4 GB PCIe addressing
  • Support for reconfigurable BAR size (in other words, 4 GB to 64 GB)
• Platforms with M2M IP improve the performance of the clEnqueueCopyBuffer API, allowing much faster transfers of buffers from one DDR bank to another (within the same device)
• Improved general interoperability with other acceleration cards that are also present on the server
• AlveoU250 shell floorplan has been enhanced to support Digital Rights Management (DRM)

SDAccelTool Enhancements

• Support for QDMA development shells with direct host to kernel streaming
• Improved kernel-to-kernel streaming
  • Supports streaming in C++ kernels
  • New--scoption specifies kernel-to-kernel streaming connections for RTL and C++ kernels
  • Supports free-running RTL kernels, which do not require any start/done synchronization
    Note:Control-free kernels with an ap_ctrl_none execution model should only be packaged through scripts generated from the RTL Kernel Wizard. You cannot use package_xoindependently.
• ImprovedSDAccelapplication timeline trace integrating new streaming features andPCIepeer-to-peer
• The dataflow ping-pong buffers can be sized through the stream pragma

XilinxRuntime 2.2 (XRT)

• Support forPCIepeer-to-peer, QDMA, M2M
• Newxrt.iniconfiguration file, which replacesSDAccel.ini
• Newexampleson theXilinxMedia Accelerator (XMA) GitHub repository
• For more information on the XRT 2.2 release, see thechangelogon the XRT GitHub repository

Nomenclature

Alveo™Linux package shell names adhere to the nomenclature depicted in the figure shown below. The example denotes aXilinxshell designed for the U200 card with a main customization levelxdma. The shell was created with the 2018.3 release of the tools and has a minor shell revision (release) level of1

Figure:Shell Nomenclature Example

TheXilinxruntime (XRT) packages follow a similar nomenclature that also denotes the release number, such asxrt_u200_xdma_201830_1.

Life Cycle for the Alveo XRT and Shells

Beta

A pre-production version that is typically distributed through Xilinx-hosted secured web lounges. Shells are marked BETAand otherwise ESfor cards relying on engineering sample devices.

Production

Production shells are available on https://www.xilinx.com/, under their respective card product web page. They are supported with the servers and OS combinations documented in Getting Started withAlveoData Center Accelerator Cards(UG1301), or the VCU1525 Reconfigurable Acceleration Platform User Guide(UG1268).

Major Release

The major release version of a shell is denoted in the customization substring of its file name, as shown in the previous figure (for example, xdma_201830). A major release can include new features or capabilities.

Minor Release

Shell updates (bug fixes or enabling specific new features) have an incremented suffix (>1). It is recommended to update to the latest minor release of a shell whenever possible.

Superseded

Runtime or shells updated and replaced by a newer version, typically a minor release with backward compatibility.

Discontinued

XRT or shells that are no longer supported.

Shells and Tool Compatibility

• When developing applications, the XRT and theSDAcceldevelopment environment must have the same major release version.
• A shell for a given major release version can be used with the XRT andSDAcceldevelopment environment for the releases from the next calendar year. For example, 2018.3 shells will be supported with the XRT andSDAccelreleases from 2019.
• A specific release of theSDAcceldevelopment environment and XRT supports the use shells with a major release version from the prior calendar year, although some additional setup may be required.