When I open my project in Vivado 2017.3 I get a critical warning similar to the following:
Critical Warning [Board 49-67] The board_part definition was not found for xilinx.com:vcu118:part0:1.1. This can happen sometimes when you use custom board part.
You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.
I am not using a custom board part. My project uses a Xilinx board part that worked correctly in Vivado 2017.2.
Additionally, once I open the old project in Vivado 2017.3, because the board part cannot be found, Vivado selects a part instead of a board and loses board awareness.
In Vivado 2017.3, Xilinx added ES# to the board part for VCU118-ES1 and ZCU102-ES2 board files.
This allows stand-alone tools to differentiate between ES silicon boards and production silicon boards.
However, when opening a project from Vivado 2017.2 which uses one of these board parts, the above Critical Warning will be issued.
To resolve this, all VCU118-ES1 and ZCU102-ES2 and earlier designs should be re-targeted to new parts available in 2017.3.
The new parts are:
AR# 70015 | |
---|---|
日期 | 11/21/2017 |
状态 | Active |
Type | 综合文章 |
Tools |