-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating XSA for KV260 returns issue #17
Comments
Can you look at vivado.log and see if there are any other messages? |
There isn't anything in here that looks suspect to me. There are 4 critical warnings about width mismatches, which I have seen cause no issues using the block designer in the past, this is just a flavor of 4 critical warnings The regular warnings are also of this nature (width mismatch) The only info comment looks interesting is the following one that appears 9 times The last commands the execute before this error pops up are: Looking into the sub-block of capture_pipeline, one of the blocks Video Frame Buffer Write or MIPI CSI-2 Rx Subsystem is to cause? I am just not getting any indicator as such. |
Can you browse into the following directories and check the runme.log file to figure out if it is MIPI or Frame buffer write that failed. platforms\vivado\kv260_ispMipiRx_vmixDP\project\kv260_ispMipiRx_vmixDP.runs\kv260_ispMipiRx_vmixDP_mipi_csi2_rx_subsyst_0_0_synth_1 platforms\vivado\kv260_ispMipiRx_vmixDP\project\kv260_ispMipiRx_vmixDP.runs\kv260_ispMipiRx_vmixDP_v_frmbuf_wr_0_0_synth_1 |
so whatever is happening, I don't actually end up with a *.runs folder. Running the script that make invokes from within Vivado, I get the same error. Then if I try to "generate output products" for the block design, the same error pops up, but it doesn't seem to be generating an error log or a useful error log from what I can find. |
Not sure if you are running into this issue with Vitis HLS (Frame Buffer Write IP is an HLS IP) which had a timestamp issue Can you check if you have this patch? |
From reading the app notes, and trying to install the patch, it doesn't apply to 2022.x versions, only previous. It appears to be a windows/linux thing. I spun up an Ubuntu VM and installed the same version of Vitis/Vivado on it, and made it past this step without issue. I wish the error log in windows gave me some better sense of what it is having issue with. Thanks for the help |
Hi, I'm following instructions from the Xilinx docs for the KV260 Defect Detect application here, and can't get through the vivado flow, running the following command as per the doc page
make xsa
Which then produces the following error:
ERROR: unexpected exception when evaluating tcl command
while executing
"generate_target all [get_files $proj_dir/${proj_name}.srcs/sources_1/bd/$proj_name/${proj_name}.bd]"
(file "scripts/main.tcl" line 60)
The same result occurs when attempting to create the XSA for the other applications and the error doesn't really provide any insight as to a root cause.
Pleas advise?
The text was updated successfully, but these errors were encountered: