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# 67915

2016.2 Vivado - Deleting a PBLOCK which contains objects selected in an open Timing window causes internal Exception

Description

I have an implemented design open in the Vivado Device window.  I select a path in the Timing window which also selects the path in the Device window.
If the selected path is contained within a PBLOCK (for example, pblock_1) and that PBLOCK is deleted from the Physical Constraint window (or I use the "delete_pbock pblock_1" Tcl command), I see errors similar to the following:

ERROR: [Vivado 12-106] *** Exception: ui.g.e: Can't find floorplan for PBlock (See C:/Users/<username>/AppData/Roaming/Xilinx/Vivado/vivado_pid15200.debug)
ERROR: [Vivado 12-106] *** Exception: ui.g.e: Can't find floorplan for PBlock (See C:/Users/<username>/AppData/Roaming/Xilinx/Vivado/vivado_pid15200.debug)
ERROR: [Vivado 12-106] *** Exception: java.lang.NullPointerException (See C:/Users/<username>/AppData/Roaming/Xilinx/Vivado/vivado_pid15200.debug)
ERROR: [Common 17-39] 'delete_pblocks' failed due to earlier errors.

Solution

The Timing results table is not being correctly refreshed after the pblock is deleted and the stale data results in the exception.

This issue has been fixed in Vivado 2016.3.

AR# 67915
Date Created 09/22/2016
Last Updated 09/27/2016
Status Active
Type General Article
Tools
  • Vivado Design Suite - 2016.2