01-01-2019 09:48 PM
I've faced this problem a couple of times. Module not found error especially for framebuffer read/write IPs are little frustrating.
Initially I thought this error could be due to path length violation and tried reducing the path length.
This did help me sometimes but not always. Also, I tried resetting & regenerating the IPs in the BD.
I've checked various forum posts and so far I see all these as temporary workarounds. I have not been able to figure out actual cause for this error and fix it.
Today, Again I'm facing these issues and I want someone out there to help me resolve this.
01-03-2019 01:09 PM
Module not found errors can occur for different reasons. Not having a valid license, an incorrect path, corrupted directory among others.
For help with yours specifically, please post what error you are seeing.
01-03-2019 09:09 PM
01-04-2019 03:38 AM
Vivado should generate a vivado_hls.log in the output product folder for the frame buffer IP. This file usually contains the error which lead to the failure for the output product.
Could you look for this file?
By experience I have seen the following root causes:
1. No license
2. Path length
3. enable_beta_devices in the vivado_init.tcl file
4. Unexpected character in the path (see AR#71759)
01-10-2019 02:10 AM
Do you have any updates on this? Did you find the vivado_hls.log file?
If your question is answered or your issue is solved, please kindly mark the response which helped as solution (click on "Accept as solution" button below the reply)
If this is not solved/answered, please reply in the topic giving more information on your current status.
Thanks and Regards,
01-10-2019 06:59 PM
I'm still not able to figure out this issue.
I've changed the path, tried resetting and generating output products as well but no improvements.
I will check the log and update you. Please let me if you could get any clue on this problem.
01-11-2019 12:28 AM
As mentioned, usually we can find the error from the vivado_hls.log file which is generated in the frame buffer output product. Please share this file
01-11-2019 05:04 AM
Thank you for sharing the vivado_hls.log file. The error is pretty clear:
ERROR: [IMPL 213-66] The file name(s) for '<path>.runs/hdmi_example_zcu102_v_frmbuf_rd_1_0_synth_1/hdmi_example_zcu102_v_frmbuf_rd_1_0/prj/impl/.pcores/hdmi_example_zcu102_v_frmbuf_rd_1_0_v_frmbuf_rd_top_v1_0/simhdl/verilog/hdmi_example_zcu102_v_frmbuf_rd_1_0_Block_crit_edge447.v' would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.
The issue is still that the overall path is too long. You should use a shorten bd name as it appears multiple times in the path. Change "hdmi_example_zcu102" to simply bd_0. Also you can reduce the instances name for the frame buffer IPs, from v_frmbuf_rd to vfbrd for example.
01-16-2019 06:22 AM
Do you have any updates on this?
My suggestion (offline) was to rename the bd using save bd as. Did it work for you?
01-18-2019 02:08 AM - edited 01-18-2019 02:12 AM
I tried things you've suggested and there's no much improvements. However, I was able to get IPs generated and compiled for the first time after the changes. If I try regenerating one more time, I see same errors during OOC runs.
Change the IP name to "vfbrd" in the properties. But I get this below warning while changing component name
set_property CONFIG.Component_Name vfbrd [get_bd_cells /path/vfbrd_0]
WARNING: [BD 5-263] Attempt to change 'Component_Name' on 'vfbrd_0' to 'vfbrd' is not allowed and is ignored.
Is it possible to change component name as well?
Also, I'm not able to change the instance name as IPs are part of BD.
01-18-2019 03:03 AM
You might want to use write_bd_tcl. This way you should be able to make all the changes you want in the TCL file.
01-24-2019 01:29 AM