UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 66230

SDK - SDK Release Notes and Known Issues

Description

This is the Release Notes Answer Record for SDK.

Solution

SDK 2016.3

What is New?

  • General
    1. Automated Hardware platform generation via drag-and-drop of HDF files.
    2. Updated Memory tests to include Eye tests
    3. Added support for downloading additional WebTalk information
    4. Support added for additional flows for QEMU in SDK
      • Launch via "Debug As System Debugger QEMU"
      • STDOUT shown in the QEMU console log.
    5. XSCT/XSDB Enhancements
      • Commands Included
        • Backtrace (bt)
        • Verify
          • .elf
          • .data
        • XSCT User Guide re-formatted for better readability and more examples added.
  • Toolchain and libraries
    1. Toolchain version update
      • Compiler Toolchain updated to 5.2 version (all)
    2. Support added for ARMCC as a useable 3rd party compiler
      • requires working ARMCC license
      • Need to have the ARMCC toolchain in the PATH
      • Only available for Zynq-7000 (A9) in the 2016.3 release
    3. Library project creation feature in SDK
      • Library types are 'Shared Library' (Linux Only) and 'Static Library'
      • OS Platforms are 'Linux' and 'Standalone'
      • FreeRTOS
      • Users can create Shared libraries only on Linux.
      • Users can specify extra settings under Advanced --> Extra Compiler Flags
  • Cross-triggering Setup GUI
    • Use Cross triggering functionality to debug Hardware & Software
    • Option to create/remove breakpoints as a part of debug configuration dialog
    • Display list of cross signals based on hardware design
    • Cross triggering breakpoints displayed in 'Breakpoints' window
  • MicroBlaze Improvements
    1. MB Hardware-based (Non-Intrusive) Profiling
      • Select the program and the address range that needs to be profiled
      • Select if the instructions/cycles should be counted
      • Start/stop profiling as needed
      • Additional command in XSDB to support (mbprofile)
      • Only available if hardware profiling is enabled in the MicroBlaze system
    2. GPIO register view available from MDM
      • If the IP instance is in the MDM address map, then it will be shown in that context
      • If the IP is not available in MDM address map, then it will be shown from MicroBlaze context
    3. MB compiler tool chain optimization for performance
      • LTO (Link Time Optimizations) to eliminate dead code
      • Smaller footprint for PMU firmware
  • System Performance Analysis
    1. Advanced Mode features for PS APM
      • PSU has 9 AXI Interfaces monitored by 4 APMs
        • 6 DDR controller Ports
        • CCT to Core Switch
        • OCM Interface
        • LPD switch to FPD switch
      • DDR APM has 10 counters, the other 3 APMs each have 8
    2. STM use example for FreeRTOS
      • STM provides software trace instrumentation
      • Data written to STM buffer is emitted in the form of MIPI STPv2 trace packets
      • Trace OS and application events with global timestamp
        • Integrated with FreeRTOS BSP
        • Timeline view of the RTOS events
        • Start/stop collecting trace when needed
      • Multiple channels for multiple processors shared without conflict
      • QTV Demo in Q4
    3. Display Cleanup
  • XMD End of Life 2nd Step: Hidden
    1. XMD is Hidden
      • Still available but not directly from SDK Menus
      • XSDB should work for everything
    2. Use XSCT Console
      • Replace XMD console in the Debug Perspective
      • Also available as separate tools from the start menu
      • Can also be installed without the SDK GUI.

SDK 2016.2

This release is focused on quality. A number of quality related issues were addressed in this release.

SDK 2016.1

What is New?

  • General
    1. Linux OS Aware Debug
      • Processes on Linux Kernel
      • Threads in each process
      • Call stack for each thread
    2. Zynq UltraScale MPSoC Support Enhancements
      • Linux application debugging using TCF agent for Cortex A53, and Cortex R5
      • GUI Support for Bootgen
      • Cross triggering support through XSDB
      • SPM design for PS-PL interface performance and Cortex A53/R5 Performance
      • Flash Support
    3. XSCT Enhancements
      • No group name prefix for SDK/XSDB commands
      • No need to mix HSI and XSCT commands for complete flow
      • PetaLinux commands over XSCT shell
      • Compiler options settings from XSCT
      • See (Xilinx Answer 66629) for more info
    4. XSDB Enhancements
      • Source level debugging
      • gprof support
    5. Compiler Tool chain
      • Hard Float support for Cortex A9 compiler
      • Linaro compiler for Cortex A9, Cortex A53 and Cortex R5 version 4.9.x
      • MicroBlaze Compiler upgraded to version 5.2
      • Default toolchain for A9 is Linaro
    6. XMD is deprecated

SDK 2015.4

What is New?

  • General
    1. This release is focused on quality. A number of quality related issues were addressed in this release.
    2. Added support for filtering application templates based on the processor and OS
    3. Added new commands in XSCT (get_projects, delete_projects, set_build_config, and get_build_config)
    4. Updated XSCT command, import_sources, to allow for inclusion of the linker script in the import
    5. Added new option to the xsdb memmap command to relocate the address map of the program sections for self-relocating code
    6. Delivered new BETA hardware template for Zynq UltraScale+ MPSoC ZCU102 development board.


SDK 2015.3

What is New?

  • Installer
    1. Xilinx SDK now supports stand-alone installation of the following:
      • Xilinx Software Development Kit (XSDK) - An Eclipse-based integrated development environment (IDE) for creating, debugging, optimizing, and downloading software applications for Xilinx processors.
      • Xilinx Software Command-Line Tool (XSCT) - A unified scriptable interface for creating, building, and debugging software applications, creating bootable images, programming FPGA and writing flash devices.
    2. In both of the installation modes, you can deselect the ARM Cortex-A53 and ARM Cortex R5 compilers.


  • General
    1. Support for MultiBD designs from Vivado
    2. Source Control support in SDK: Git plug-in integration
    3. TCF agent for MicroBlaze allowing Linux application debug using System Debugger
    4. Soft IP register view in debugging view
      • GPIO, CAN and I2C
    5. Improved performance views using the Trace Compass Framework
      • More configurable control (interface name display, session configuration)
      • Tool tips
      • Selectable graph display
    6. Offline Trace Support
    7. SDK New Terminal


  • Help
    1. Quick access to OS and library documentation
    2. Improved SDK driver API documentation
    3. Content reorganization

SDK Install Requirements

2016.3:

https://www.xilinx.com/html_docs/xilinx2016_3/SDK_Doc/index.html?q=/html_docs/xilinx2016_3/SDK_Doc/xsct/intro/xsct_system_requirements.html

Driver Change Log:

https://github.com/Xilinx/embeddedsw/blob/master/doc/ChangeLog

Older Releases

  • Release notes of older releases can be found here:
http://www.xilinx.com/support/documentation/sw_manuals/xilinx2015_3/SDK_Doc/SDK_concepts/sdk_c_whatsnew_archive.html

Limitations, Known Issues, and FAQs

Limitations

  1. Support for SVF Format discontinued. Use an earlier release of SDK for SVF support.
  2. Support for 6 Series and below devices discontinued. Use an earlier release of SDK for support of 6 Series and below devices.


FAQs

  1. How can I set the register display format so that it defaults to "Hexadecimal"?
  2. Can I debug more than one application at the same time?
  3. I have a large ELF application file to debug, and SDK seems to time out when I am downloading the ELF file. How can I increase the time-out period?
  4. I have my board connected on one machine, and I would like to debug my application using SDK running on another machine. How do I set up the Launch Configuration to perform this remote debug operation?
  5. I want to debug an ELF file using SDK without creating a C/C++ Project. How do I do that?
  6. During Debugging (or Running) the application, I would like to download my data files along with my application's ELF file. How do I do this?
  7. How do I specify the Reset options to be used when a Debug (or Run) session is launched?
  8. In which scenario should I use Xilinx System Debugger or Xilinx C/C++ Debugger (XMD+GDB)?
  9. How can I tell Xilinx System debugger to start at program entry?
  10. Debug after re-launch does not stop on breakpoints.
  11. Cannot set more than 5 breakpoints/watchpoints for ARM targets
  12. Launching hw_server gives a "missing FTD2XX.dll" error message.

Known Issues

  1. While debugging the BSP code, some variable values are displayed as N/A
  2.  Exporting project to GIT server causes problems in BSP/Application Compilation
  3. Projects created in the default location may cause compilation issues
  4.  After installing SDK on Ubuntu machines, toolchain paths are not accessible from SDK
  5. Ucos application project creations fail due to non-availability of pre-compiled libraries and source code
  6. Debugging or running of A53 32-bit application requires board reset
  7. MSS Viewer does not refresh automatically
  8. Renaming hardware platforms causes compilation errors
  9. Restore defaults in C/C++ Build Settings causes settings to be lost
  10. Operations on XMD console can confuse the internal state of SDK
  11. When SDK launches, it does not display the correct menus, the correct icons, or the C/C++ Perspective
  12. After any reset, the debugger hangs when accessing DDR3 memory
  13. SDK internal state gets out of sync with actual target status if Zynq board is switched off during execution of an application
  14. Debug System Reset does not work on a 2.0. Zc706 board that has the 2.0 silicon
  15. SDK Hangs After Design Changes in Block Design and Export Hardware (Design with User IP)
  16. While Initializing the bitstream with an ELF file, SDK uses bootloop
AR# 66230
Date Created 12/13/2015
Last Updated 11/21/2016
Status Active
Type Release Notes
Devices
  • Kintex-7
  • Kintex-7Q
  • Artix-7Q
  • More
  • Artix-7
  • Virtex-7 HT
  • Virtex-7
  • Virtex-7Q
  • Zynq-7000
  • Zynq-7000Q
  • Less
Tools
  • Vivado Design Suite - 2015.4