Puma20Top.ucf

[creed]

I am Trying to compile a design, but i am getting the following error;

Reading NGO file
"C:/NIFPGA2009/srvrTmp/localhost/16TapFir_FPGATarg~A7_16TapFir_rbt0komm~F7/Puma2

0Top.ngc" ...
ERROR:NgdBuild:765 - "Puma20Top.ucf" Line 647: A parsing error has occurred
  while reading the constraint file. The value 'RISING' at column 74 is
  invalid.
ERROR:NgdBuild:31 - Errors found while parsing .ucf file "Puma20Top.ucf".
  Please check for syntax errors in the UCF file.  For more information on
  legal UCF constraints, please see the Constraints Guide for more
information
  on this attribute.

Writing NGDBUILD log file "Puma20Top.bld"...
ERROR:Xflow - Program ngdbuild returned error code -1. Aborting flow
  execution...

I am running 32-bit Labview on a 64-bit Win7 system.  The file seems to be generated automatically.

I have been able to successfully compile the design on a remote 32-bit XP system, but I'd like to be able to

work locally.  I've checked the line in question and it looks the same on both systems;

TIMEGRP "Sync100Grp" OFFSET = IN 2.5 ns VALID 3.0 ns BEFORE "PXIeClk100" RISING;

Any thoughts on how I can get past this error would be appreciated.

Thanks

Chuck Reed

[dsangree]

Chuck,

Specifically which product are you compiling for? I would find it odd if that error came from a PXIe-5641R compile.

-Daniel

[creed]

Sorry.  Initially I was unable to find the 5641R device so I chose another device that used

the same FPGA.  I see the error when compiliing for the PXIe-7965R.

-Chuck

[dsangree]

Chuck,

If you have the NI-5640R driver installed, the devices will show up under IF-Transceivers. Right-click "My Computer" in the project > New > Targets and Devices... > New Target or Device > IF- Transceivers > Your Device. If you are not seeing this menu then you may not have the NI-5640R driver installed. If you need to download the driver you can just Google "NI-5640R 1.4". That driver contains support for LabVIEW 2009 and both the PCIe-5640R and the PXIe-5641R.

Now back to your error... Seeing as this error is unlikely related to the NI-5640R driver, I have pointed someone in the FlexRIO team to your forum post. They should be able to help you further.

-Daniel

[creed]

Thanks!  I don't know why I don't see the 5641R as a target when I'm creating a new design, but I was able

to add the 5641 by following your instructions.  I then deleted the 7965R and added my vi under the 5641R

target.  When I compiled the design, it completed successfully on both machines.  I don't know why that

would fix a syntax issue, but it works for me.

Now it's on to my next issue.

Thanks for your help.

Regards,

-Chuck

[BrowningG]

Hi Chuck,

I wanted to try to get to the bottom of your original issue.  I would like to see if I can reproduce the issue on my computer, so I have a few questions.  What version(s) of LabVIEW are you compiling on?  Did this issue always occur on your local (Windows 7) machine?  Knowing how often the error occurred and the compile server used on both machines can provide some insight.  

Would it be possible for you to zip up a copy of the project that causes the error and attach it to this forum?  A copy of the Xilinx log you referenced in your first post would also be helpful to determine if there are any issues earlier in the compile that relate to this failure.  If you are using an Component-Level IP (CLIP) in your design, it would be helpful to include it (if possible) for when I compile this on my computer.  

I am looking to see if this error is based on a particular project configuration or if the contents of the VI (and CLIP) are affecting this error.

[creed]

BrowninG,

I've attached (hopefully) the files you asked about.  I was able to recreate the error by switching back

to the PXIe-7965R target.  Regarding your other questions:

I'm running Labview 2009 SP1 in 32-bit mode on a Win7 64-bit laptop.

The error occurs on every attempt to compile with the PXIe-7965R target

The vi and lvproj associated with design should be attached. I'm new to the labview FPGA flow so

      bear with me.

I've attached the Xilinx log file and two copies of the Puma20Top.ucf file.  Both had a timestamp that

      was consistent with the compile so I'm not sure which one was used (and caused the errror).

If you need anything else please let me know.

Regards,

-C.

[BrowningG]

Hi Chuck,

I forgot to ask, but what version of NI-RIO do you currently have installed?  As we release new copies of NI-RIO we update some of the FlexRIO fixed logic files to fix bugs and improve performance.  I wanted to make sure I was emulating your system as closely as possible. 

[creed]

We have NI-RIO 3.4 Installed.

Regards,

-Chuck

[BrowningG]

Hi Chuck,

Thanks for the information.  I am still working to reproduce this issue and I have run into something interesting.  I was looking through the UCF files you sent me, and they appear to from the LabVIEW FPGA 2009 installation and not 2009 SP1.  Is it possible that your laptop still has 2009 installed while your remote server is running 2009 SP1?

I can perform a check to ensure that your computer has all of the correct target files installed for 2009 SP1.  Could you send me a zipped copy of the following directory?

C:\Program Files (x86)\National Instruments\LabVIEW 2009\Targets\NI\FPGA\RIO\79XXR

I will be able to compare the files in this directory to ensure that they match all of the correct install files. 

Also, LabVIEW keeps copies of some of the generated compile files after a compilation is finished.  I wanted to reproduce your issue so I could look through this file stack.  Since I am still trying to create a failing compile it looks like I will need your files.  You can find the compile files in C:\NIFPGA2009\clntTmp.  The name of the failing directory is based on a unique name generated by LabVIEW, so I usually use timestamps to find the correct directory.  Could you send me a zipped copy of the failing compile directory?

Based on the failure reported in your log file, it seems like this failure should reproduce with a blank VI.  Do you know if a blank VI compiles successfully for a PXIe-7965R on your local machine?