11-04-2013 07:08 AM
I created a webpack license for use with Vivado 2013.2, along with a couple evaluation licenses and free licenses for image processing, resulting in four license files in the .Xilinx directory. When I run synthesis, implementation, and bitstream generation, the console log shows messages such as
INFO: [Common 17-78] Attempting to get a license: Implementation
WARNING: [Common 17-301] Failed to get a license: Implementation
WARNING: [Vivado 15-19] WARNING: No 'Implementation' license found. This message may be safely ignored if a Vivado WebPACK or device-locked license, common for board kits, will be used during implementation.
INFO: [Common 17-78] Attempting to get a license: Synthesis
WARNING: [Common 17-301] Failed to get a license: Synthesis
INFO: [Common 17-78] Attempting to get a license: Internal_bitstream
WARNING: [Common 17-301] Failed to get a license: Internal_bitstream
This gives a mixed message as to whether I have sufficient license to continue, but the build process continues and I eventually see a message saying that the bitstream has been generated, i.e.,
Writing bitstream ./design_1_wrapper.bit...
INFO: [Vivado 12-1842] Bitgen Completed Successfully.
write_bitstream: Time (s): cpu = 00:01:14 ; elapsed = 00:01:09 . Memory (MB): peak = 1388.797 ; gain = 378.340
However, when I try to export the hardware to SDK, "include bitstream" is ghosted and I am unable to export.
It isn't clear what the webpack enables. Can somebody explain what's going on here and what is needed to get a bitstream that I can export?
11-04-2013 09:03 PM
You can safely ignore these warnings as the message indicates.
You are getting these warnings since you are using WEBPACK license.
Can you attach the sanpshot of the error that was poping up when you are trying to export hardware?
Also attach Xinfo file
11-05-2013 06:41 AM
The error I get is a popup that says "ERROR: [Common 17-39] 'export_hardware' failed due to earlier errors." Not very informative. The implementation stage of processing shows 1 critical warning "did not meet timing requirements" but that shouldn't have prevented a bitstream creation. In fact, there is a bitstream file (design_1_wrapper.bit) in the hardware/vivado/project/my_project.runs path with a timestamp that says it was created with my last build.
11-05-2013 05:53 PM
You may want to look at the Message tab in Vivado GUI to see if there're any ealier errors in running export hardware.
11-05-2013 07:56 PM
Aha, and there is the culprit. In the Vivado Commands section of the Message tab, there's a message that points to the problem
It doesn't make sense to me that the block design must be open to export hardware. This seems like a bug to me unless there's some logical reason for why the IP integrator panel has to be visible to export hardware.
Thanks for the help, but if you could explain the logic for this, I'd appreciate it.
11-06-2013 06:44 AM
On further inspection, the export hardware process still doesn't work. I no longer get the error mentioned previously, but the "include bitstream" selection on the "Export Hardware for SDK" popup is ghosted. The files that are exported are the design_1.xml file and all the ps7_init files in the hw directory, but nothing else.
Could this be a licensing problem? An IP status report shows all the modules are "up-to-date" with all the licenses being either "included", "purchased", or "hardware_evaluation"
04-20-2014 09:11 PM
This is NOT a licensing problem.
Look at the message tab for the information on new error message.
Also post it here to provide you a solution for the error message.