AR# 68925

2017 Vivado - Known Issues for Vivado 2017.x User Interface (GUI) and Project Management


This answer record contains a list of Vivado Design Suite graphical user interface and project management known issues for Vivado IDE 2017.x.


Outstanding Known Issues in Vivado Design Suite 2017.4

(Xilinx Answer 55418)Message suppression rules are not editable
(Xilinx Answer 66978)Implementation log file (.vdi) in the reports view gets overwritten if Generate Bitstream is rerun
(Xilinx Answer 68249)Code editor is truncating large files at 2MB
(Xilinx Answer 69186)Vivado 2017.x only supports fuzzy font scaling on Windows OS
(Xilinx Answer 69320)Design fails in opt_design with a black-box error for a module implemented in a conditional statement (using generic or parameter value) - Partially fixed in Vivado 2017.2 and 2017.3
(Xilinx Answer 69846)The hierarchy source view in Vivado 2017.x is incorrect or takes a long time to update compared with Vivado 2016.x - Partially fixed in Vivado 2017.2 and 2017.3
(Xilinx Answer 70018)Users are not able to change the board part of an existing project
(Xilinx Answer 70036)After using the set_msg_config command to suppress a message, the command history is not available in GUI mode
(Xilinx Answer 70038)pwd command incorrectly returns C:\ (root directory) after changing directory from another drive (cd C:)
(Xilinx Answer 70333)Changing constraints in the DDR4 Memory Byte Planner crashes the Vivado IDE
(Xilinx Answer 70442)Vivado IDE crashes during startup on a Linux OS running Vivado with GNOME using Wayland

Known Issues Resolved in Vivado 2017.4

(Xilinx Answer 69908)Vivado does not launch with Windows 10 Fall Creators Update
(Xilinx Answer 69929)The Message console does not allow filtering of the displayed messages by severity
(Xilinx Answer 69933) Opening an exported example design gives ERROR: [Common 17-53] User Exception: Project already exists on disk, please use '-force' option to overwrite
(Xilinx Answer 70015)New ES board definition files result in a Critical Warning [Board 49-67] The board_part definition was not found
(Xilinx Answer 70027)Clocking Wizard IP core is not displayed in the Vivado hierarchy
(Xilinx Answer 70035)Create_runs returns an error when creating a run with a name that includes the '$' character
(Xilinx Answer 70086)Vivado gives an Internal Exception when running 2017.3 over Xterm

Known Issues Resolved in Vivado 2017.3

(Xilinx Answer 69484)Missing source file cannot be removed from a project
(Xilinx Answer 69529)ERROR: [filemgmt 56-220] Caught exception before/during exec of srcscanner. - Known cause fixed in Vivado 2017.3
(Xilinx Answer 69692)Vivado hangs when selecting specific nets in schematic or netlist view

Known Issues Resolved in Vivado 2017.2

(Xilinx Answer 69088)Java Error Messages when opening implemented design due to extra protobuf-java-3.1.0.jar file.
(Xilinx Answer 69509)Vivado Source files - Hierarchy missing components due to Generate Statement
(Xilinx Answer 70039)Launching Vivado gives: "" when vivado.xml file has read only permission

Known Issues Resolved in Vivado 2017.1

(Xilinx Answer 66827)Code Editor shows gargled text for long lines on RHEL 7.1 OS
(Xilinx Answer 68295)Saving constraints gives "ERROR: [Common 17-53] User Exception: A file was added to constraint set constrs_1 after the implementation design was open
(Xilinx Answer 68914)Code Editor: Inserting white space in column mode overwrites first character of each line.
(Xilinx Answer 69157)Red Hat Enterprise Linux 5.x (RHEL5) is no longer on the list of officially supported operating systems for Vivado

AR# 68925
Date 04/09/2018
Status Active
Type Known Issues