Visibility into the FPGA.

EXOSTIV Dashboard for Xilinx – Release Notes

EXOSTIV Dashboard for Xilinx – Release Notes

Version 1.9.2

  • Build 191024
  • Fixed netlist browsing issue
  • Fixed deadlock in communication with Vivado
  • Minor bug fixes
  • Build 190920
  • Bug fixes in TCL libraries.
  • Bug fixes in node hierarchical search.
  • Fixed issue with launching Exostiv Dashboard from Vivado on Windows platforms.
  • Added some explanatory messages in core inserter.
  • Build 190902
  • Released Exostiv Dashboard for Windows in 64-bits version to overcome memory limitations with 32-bits version.
  • Build 190820
  • Added support for Vivado up to 2019.1
  • Added nodes hierarchical search in core insertion
  • Added trigger counter and data qualification event counter
  • Added software automatic update check
  • Bug fixes

Limitations and known issues

  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • The output clock connector of EXOSTIV Probe is a deprecated feature that will not be supported in the future on EP6000 and EP12000 probes.

Version 1.9.1

  • Build 190225
  • Fixed issue occurring with clock 1 selection for transceivers.
  • Fixed issue occurring when attempting to re-connect to target without re-programming it in HDMI connection mode.
  • Build 190220
  • Transceiver reference clock can now be shared between the existing design and the EXOSTIV IP
  • Bug fixes

Limitations and known issues

  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • The output clock connector of EXOSTIV Probe does not always match the specified clock. Contact us if you want to use the output clock feature of the probe.

Version 1.9.0

  • Build 190118
  • Added support for optical fiber
  • Added support for Vivado 2018.3
  • Added support for Ubuntu 18.04
  • Fixed Vivado button installation script.
  • Extended TCL support
  • Bug fixes

Limitations and known issues

  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • The output clock connector of EXOSTIV Probe does not always match the specified clock. Contact us if you want to use the output clock feature of the probe.

Version 1.8.5

  • Build 180813: Fixed output clock port generation for GTY / GTH.
  • Build 180809: Wave export speed up.
  • From Build 180806 and on: added output clock signal to EXOSTIV IP.
  • Added support for Vivado 2018.1 and 2018.2
  • Fixed constraints issues for Vivado 2017.3 and 2017.4
  • Added bandwidth calculator / link efficiency check (helper) at core insertion
  • Bug fixes

Limitations and known issues

  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • The output clock connector of EXOSTIV Probe does not always match the specified clock. Contact us if you want to use the output clock feature of the probe.
  • (Windows version) Installing the Vivado shortcut button sometimes leads to Vivado not starting for Vivado 2017.4 and later. See this article in our knowledge base to correct this.

Version 1.8.4

  • Build 180426 – Windows OS only: corrected an issue that prevented from linking Vivado with Exostiv Dashboard in case not network was present.
  • From Build 180416 and on: added support for starting and linking Exostiv Dashboard from Vivado in batch and/or TCL mode + some bug fixes.
  • Added support for Vivado 2017.3 and 2017.4
  • Added TCL scripting interface
  • Fixed GTH transceiver support issue for Virtex-7
  • Stability enhancement and minor bug fixes

Limitations and known issues

  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • The output clock connector of EXOSTIV Probe does not always match the specified clock. Contact us if you want to use the output clock feature of the probe.

Version 1.8.3

  • Corrected bug affecting runs with multiple capture units simultaneously.
  • Improved the robustness / noise immunity of the link in SFP mode. Requires re-generating the IP.
  • Made DRC optional before implementation to avoid excessively strict DRC issues
  • Added support for Debian 9
  • Minor interface bug fixes

Limitations and known issues

  • Vivado 2017.3 is NOT supported in this version
  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • Some frequencies that cannot be reached at the back ‘output clock’ connector of the EXOSTIV Probe can be selected in the Dashboard

Version 1.8.2

Limitations and known issues

  • Running multiple capture units at the same time can crash the application. In such a case, power off the probe and restart the application. Try to limit usage at one capture unit at a time.
  • Vivado 2017.3 is NOT supported in this version
  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • Some frequencies that cannot be reached at the back ‘output clock’ connector of the EXOSTIV Probe can be selected in the Dashboard

Version 1.7.6

  • License server speed up
  • Fixed timing violation in Ultrascale+ devices
  • Improved robustness of nodes selections in Vivado netlist flow
  • Minor bugs fixes

Limitations and known issues

  • Vivado 2017.x is under test and not currently supported
  • Vivado and EXOSTIV Dashboard must run on the same machine in Netlist Insertion mode.
  • On Win 7 machines, connecting to the EXOSTIV Probe in USB 3.0 sometimes fail, depending on the USB 3.0 host. Working around this solution include using USB 2.0 cable to force USB 2.0 usage and/or using Win 10 based machines, where the USB 3.0 support is native.
  • EXOSTIV Dashboard v.1.7.x cannot recall a stored project archive generated with EXOSTIV Dashboard v. 1.6.x or older. EXOSTIV Dashboard v.1.7.x is able to load a project generated with EXOSTIV Dashboard v. 1.6.1, though.
  • A bandwidth problem can appear in some circumstances with small bursts belowe 256 samples. This issue creates an unexpected overflow and sometimes a software crash. Please refer to the following knowledge base article for more information: ‘I received an unexpected overflow error with a burst size smaller than 256 or 512 samples. What happens?’.
    This is due to an issue detected in EXOSTIV Probe, which will be fixed in the next version.
  • Some frequencies that cannot be reached at the back ‘output clock’ connector of the EXOSTIV Probe can be selected in the Dashboard.

Version 1.7.5

  • Introduced Ultrascale+ devices support.
  • Fixed issue preventing from exporting waves from the waveform viewer.
  • Fixed issue corrupting the first 4 samples of a capture depending on specific capture size conditions.
  • Released support for Vivado 2016.4.

Version 1.7.4

  • Corrected issue preventing the floating license server from starting up properly in some cases.
  • Made DRC step optional before launching implementation in Core Inserter (netlist flow).
  • Provided control for switching between automatic and manual data upload to PC.

Version 1.7.3

  • Corrected issue preventing from using custom instance name in netlist flow insertion in versions 1.7.x.

Version 1.7.2

  • Corrected offline activation lockup in case of re-activation
  • Added example template for Verilog in RTL flow
  • Changed the EXOSTIV IP port structure in order to avoid array of array to enable full support of Synopsys Synplify as a synthesis tool
  • Corrected issue affecting the application of timing constraints to Kintex-7 devices
  • Updated floating license server – requires re-installing the server
  • Added check on undriven signals for Vivado netlist insertion

Version 1.6.1

  • Added synchronization pattern scrambling to improve link robustness
  • Updated IP timing constraints
  • Fixed PLL issues for 12G probes
  • Minor updates and bug fixes

Version 1.6.0

  • Fixed trigger positioning issue
  • Increased max. line rate to 12.5 Gbps
  • Enhanced floating license management
  • Fixed trigger positioning slider – did not update when changing the capture size
  • Enhanced firmware update for EP6000 and EP12000 probes
  • Minor GUI enhancements
  • Improved log notifications for oscillator errors
  • Modified IP cache to take IP local RAM into account
  • LPM and DFE modes support while trying to connect to the IP
  • Fixed possible overflow when accessing probe registers in burst mode
  • IP connection procedure now restarts when BER test fails

STAY IN TOUCH