11-29-2017 03:08 PM
I'm the FAE supporting the customer that posted this thread in August:
. The customer tried the workaround that was suggested, and was unsuccessful. However, even if the workaround had been successful, this would not be an acceptable solution. Automated scripts are being used to create the Sysgen model, and the Reed Solomon blocks are configured and instantiated on-the-fly. Black boxes cannot be configured.
The IP licenses and the Vivado license are in the same license file. We have verified that the IP license is valid in a Vivado flow. In a Sysgen flow, the netlister works if there are no IP cores. This indicates that sysgen is finding the license file. However, when IP is added, the netlister runs, but errors out on the IP license.
You stated that this is a known issue - is there a different workaround that will allow the IP to be used in an automated/scripted Sysgen flow?
11-29-2017 08:28 PM
I believe it should work as tested by other customers. Are you able to generate IP in Vivado design flow. License check only happen during core generation . So when you generate core successfully you should able to integrate in sysgen . can you please share test case to reproduce this issue (you Vivado design block imported in sysgen). For your question about sysgen license not working please share your license file through mail . We will review your sysgen license.
Please provide list of tools you are using at your end and make sure you have all the compatible versions .
Here is list of supported matlab tools
11-30-2017 02:19 AM
Can you please share the license files and the env.txt generated from running this command in tcl console:
report_environment -file env.txt
I believe the customer is using Vivado 2016.1 and is able to generate the IP in Vivado, but not in Sysgen. Please correct me if i am wrong.
11-30-2017 05:03 PM
11-30-2017 05:05 PM
Some additional information from the customer:
I decided to do some experimentation this morning. I changed the device to a Virtex 7 and it actually netlisted successfully! I then changed the device back to the one we use (Kintex UltraScale xcku115-1-cflvd1924), and it failed again. After that I attempted to do a sysgen netlist of a variant of the part we use (Kintex UltraScale xcku115-1-cflvf1924) and it netlisted successfully. For some reason there is something about our particular fpga device that sysgen doesn’t like. This has to be a sysgen bug, doesn’t it?
12-04-2017 03:51 AM
It seems this is bug in the sysgen tool . I will report to development tool. You can go ahead and use the workaround by using industrial part and later change correct part in vivado . It should be fine. The main difference between Industrial device and commercial device is temperature range supported.
So its absolutely fine to use your workaround flow