When I try to compile a Labview fpga project on our new system, it fails with the following error summary (the full Xilinx log is attached):
LabVIEW FPGA: The compilation failed due to a xilinx error. Details: ERROR:LIT:536 - IBUF symbol "aUserGpio<1>_IBUF" (output signal=aUserGpio<1>_IBUF) has the attribute IOBDELAY set to value NONE and it is driving an IODELAY. If the IOBDELAY attribute is on the driving PAD, it has precedence over the IBUF one. Either the constraint or the design need modification to prevent an unroutable situation. Errors found during logical drc. Design Summary -------------- Number of errors : 1 Number of warnings : 349 Process "Map" failed Start Time: 10:31:49 AM End Time: 10:55:32 AM Total Time: 00:23:43
The Project uses the 5761 low speed clip and a DRAM FIFO.
I tried to compile it before installing any patch, after installing the DRAM patch, and after installing both patches and always got a Xilinx error after ~10 minutes compile time. The error summary shown above and the attached Xilinx log are from compiling with both patches installed.
It compiled correctly on our older system:
Any help / suggestions greatly appreciated,
Would it be possible to post your code so that we can reproduce and investigate this failure?
We have a similar issue with 2012 - it was OK with 2011 - We get the same error message from the xilinx layer.
Did the issue ever get resolved? If so, what was the resolution?
Thanks in advance for any help...
Can you tell me what version of FlexRIO Adapter Module Support you are using?
The 5761 Low Speed CLIP has a constraint that doesn't work properly with some versions of the compilation tools. In order to solve this you should be able to upgrade to our latest version of FAM support, or go change the constraint manually.
For the latest version of FAM support, go to http://ni.com/info and enter code "famsoftware"
If you've modified constraint files before and feel comfortable doing it yourself, let me know and I can provide you with the details on how to do that.
Thanks for the response.
The FAM software update has fixed the problem!