How to solve the problem of the file "system_top_wrapper.bit is not found"?
조회 수: 9(최근 30일)
I tried to program my Zedboard through Matlab HDL coder and unfortunately I received an error message, telling me that system_top_wrapper.bit not found. Check file name and file permissions.
ERROR: [Labtools 27-2149] File ./C:/hdl_prj/vivado_ip_prj/vivado_prj.runs/impl_1/system_top_wrapper.bit not found. Check file name and file permissions.
ERROR: [Labtools 27-2163] Unable to read xicom bitstream ./C:/hdl_prj/vivado_ip_prj/vivado_prj.runs/impl_1/system_top_wrapper.bit
I run the Matlab as an administrator. When I configured the first step (1.1.Set Target Device and Synthesis Tool) through my HDL Workflow Advisor, the advisor asked me to change the default project folder path "C:\Program files\Matlab\Matlab Production Server\R2015a\hdl_prj" because path containing white space is not supported. Therefore, I manually changed the path to C:\hdl_prj. Please let me know your suggestion for solving this problem. By the way, I'm using Vivado 2014.2. When I run the following command
hdlsetuptoolpath('ToolName', 'Xilinx Vivado', ...
I received a message as follows:
Prepending following Xilinx Vivado path(s) to the system path: C:\Xilinx\Vivado\2014.2\bin.
I'm not sure if this is related to the error messages above.
Wang Chen 2016년 4월 20일
This is a bug in HDL Workflow Advisor. Thanks for reporting this! This bug is already fixed in MATLAB version R2016ad.
For R2015a, please use relative path in the "Project folder" box. To avoid the error message about path containing white space, you can start HDL Workflow Advisor from a folder without the white pace, for example, "C:\work".
Walter Roberson 2016년 4월 19일
The bit about prepending is an information message, not an error.
The message about File ./C:/hdl_prj/vivado_ip_prj/vivado_prj.runs/impl_1/system_top_wrapper.bit not found suggests to me that it requires something or other to be a relative location rather than an absolute path. Notice it put the "./" before the C: . It should have been able to detect that C: was the drive and not put the ./ there but since it does not, that might be causing problems.