04-23-2018 09:31 AM
Dear all,
after export hardware with bitstream and running SDK I got many critical waring into the XSCt Console:
CRITICAL WARNING: [Board 49-71] The board_part definition was not found for digilentinc.com:cmod_a7-35t:part0:1.1. The project's board_part property was not set, but the project's part property was set to xc7a35tcpg236-1. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command. Check if board.repoPaths parameter is set and the board_part is installed from the tcl app store
Going back in VIVADO running the TCL command:
get_board_parts
I got the following list:
digilentinc.com:arty-a7-100:part0:1.0 digilentinc.com:arty-a7-35:part0:1.0 digilentinc.com:arty-s7-50:part0:1.0 digilentinc.com:arty-z7-10:part0:1.0 digilentinc.com:arty-z7-20:part0:1.0 digilentinc.com:arty:part0:1.1 digilentinc.com:basys3:part0:1.1 digilentinc.com:cmod_a7-15t:part0:1.1 digilentinc.com:cmod_a7-35t:part0:1.1 digilentinc.com:nexys4:part0:1.1 digilentinc.com:nexys4_ddr:part0:1.1 digilentinc.com:nexys_video:part0:1.1 digilentinc.com:zedboard:part0:1.0 digilentinc.com:zybo-z7-10:part0:1.0 digilentinc.com:zybo-z7-20:part0:1.0 digilentinc.com:zybo:part0:1.0 em.avnet.com:zed:part0:0.9 em.avnet.com:zed:part0:1.0 em.avnet.com:zed:part0:1.1 em.avnet.com:zed:part0:1.2 em.avnet.com:zed:part0:1.3 xilinx.com:ac701:part0:1.0 xilinx.com:ac701:part0:1.1 xilinx.com:ac701:part0:1.2 xilinx.com:ac701:part0:1.3 xilinx.com:kcu116:part0:1.0 xilinx.com:kcu116:part0:1.1 xilinx.com:kcu116:part0:1.2 xilinx.com:zc702:part0:1.0 xilinx.com:zc702:part0:1.1 xilinx.com:zc702:part0:1.2 xilinx.com:zc702:part0:1.3
where my Cmod A7-35T is listed hence I don't know what I've to do to solve this warning into the SDK. Could you please let me know?
Thank!
04-25-2018 04:46 AM
The warnings can be ignored as there is no benefit of having your board files in the SDK. This is used for the HW creation.
02-20-2019 12:36 AM
You can try to setup the board repository path before issueing the concerned command with
hsi set_param board.repoPaths path_to_board_directory
It solved the critical warning in some other context for me (Vivado 2018.2)