FPGA Compile Error due to error in mapping process

[mikeeeee]

Received the following error while trying to compile a FPGA VI on a PC. (Refer to attachment for details). My PC has a fresh installation of English Windows 2000 with sp4. No other software is installed except LabVIEW 8.2 & FPGA Module 8.2 & NI-RIO.

I have checked this KB and confirmed that regional settings are English. But the error still exists. I tried compiling the same VI on my laptop with Windows 2000 sp4 and it was successful. Can someone help me? Thank you very much!

FPGA Compile Error When Compiling LabVIEW FPGA VI

Error found in mapping process, exiting...
Errors found during the mapping phase.  Please see map report file for more
details.  Output files will not be written.

Design Summary
--------------
Number of errors   :  17
Number of warnings :   8
ERROR:Xflow - Program map returned error code 2. Aborting flow execution...

Message Edited by maimai on 01-08-2007 01:00 AM

[JLS]

Hello,

The key will of course be to isolate differences between your machines.

I wonder if the following more specific language setting could be the lingering problem.  LabVIEW is a non-unicode program, and there is a language setting in Windows (at least XP) specifically for non-unicode programs.  Try the following (or it's Win2K equivalent) if you haven't already:

0. Open "Control Panel"

1. Open the "Regional and Language Options"

2. On the Advanced tab, choose English (United States) from the drop-down menu under the top section "Language for non-Unicode Programs"

- This language setting is different from the setting on the "Regional Options" tab. 

Any other differences you can isolate would be potentially insightful - if you have the same software versions installed in the same order on both machines, we may be looking for something a bit subtle, such as the suspected language setting.

Best Regards,

JLS

[jdigiova]

Are you using Windows 2000 Professional? The Xilinx Compiler that ships with FPGA 8.2 requires Windows 2000 Pro.  Another problem that had been seen is with file index tools such as Google Desktop.  If you have a third party utility that indexes files for fast searches than you will need to filter such that the C:\NIFPGA8.2 folder is not included in the indexing.

Regards,

Joseph

[jdigiova]

Are you still having the problem?  A number of people of seeing this issue and so far the only thing in common is Windows 2000. I would like to get a better explanation as to the problem.  Can you include the coregen.log file from a failed compile?  You should find it in the c:\NIFPGA8.2\svrTmp directory under the folder for the project you are trying to compile.

Regards

Joseph D.

National Instruments