LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

fpga compile does not start

I have Xilinx 11.5 FPGA complie tools installed on WinXP 32 bit machine installed from a .iso image avalible at ni.com.

 

When I try compile a bit file, the complier 1st goes into "waiting in queue", then into "Starting compilation", then back into "waiting in queue"

 

Below are some messages from wokerLog.txt:

 

 

CompileWorker.exe Error: 0 : 5/20/2011 11:05:45 AM This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.   at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()   at NI.LV.FPGA.CompileWorkerUI.CwUtilities.getMD5HashFromString(String stringToHash)   at NI.LV.FPGA.CompileWorkerUI.XmlPipes.OutputXmlForPipes(Boolean closePipes)   at NI.LV.FPGA.CompileWorkerUI.XmlPipes.SetStepInfo(String stepProcessName, Int32 stepNumber)   at NI.LV.FPGA.CompileWorkerUI.UnitOfWork.Run(IFpgaFarmCapability capabilityObject)   at NI.LV.FPGA.CompileWorkerUI.CompileWorkerThread.ThreadMain()BHwY6r9: Pulsed Field dIdV/FPGA Target/Run test pattern: 1: PlanAhead: DbgStdErr: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.CompileWorker.exe Error: 0 : 5/20/2011 11:05:45 AM We recieved an exception while trying to cleanup the job with the pipes existing. Exception: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.CompileWorker.exe Error: 0 : 5/20/2011 11:05:45 AM An exception occurred: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.CompileWorker.exe Error: 0 : 5/20/2011 11:05:45 AM The Unit Of Work (path: C:\NIFPGA\jobs\BHwY6r9_z3nuQ21) did not finish properly because of an exception: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.CompileWorker.exe Information: 0 : 5/20/2011 11:05:45 AM Finishing thread.  SessionId PO5kq2R WorkerId z3nuQ21 Job BHwY6r9CompileWorker.exe Information: 0 : 5/20/2011 11:05:47 AM UI info changed. SessionId: PO5kq2R Registered Capabilities: ( 'Xilinx 11.5' ) CompileWorker.exe Warning: 0 : 5/20/2011 11:05:47 AM For session: PO5kq2R workerId: z3nuQ21 -- while trying to reportWorkerState to readyToWork we recieved error: kNIFarmResultMissingExpectedUploadedFileCompileWorker.exe Error: 0 : 5/20/2011 11:05:47 AM NationalInstruments.NIFarm.NIFarmException: ErrorCode: kNIFarmResultNoWorkerIsReadyToWork StackTrace:    at NationalInstruments.NIFarm.NIFarmClient.HandleFarmResult(NIFarmResult result)   at NationalInstruments.NIFarm.NIFarmClient.IsAnyWorkAvailable(String& workerId, String& jobId)   at NI.LV.FPGA.CompileWorkerUI.CompileWorkerThreadManager.MainInfiniteLoop(Dictionary`2 sessionIdToFarmClient, String zipFileDir)   at NationalInstruments.NIFarm.NIFarmClient.HandleFarmResult(NIFarmResult result)   at NationalInstruments.NIFarm.NIFarmClient.IsAnyWorkAvailable(String& workerId, String& jobId)   at NI.LV.FPGA.CompileWorkerUI.CompileWorkerThreadManager.MainInfiniteLoop(Dictionary`2 sessionIdToFarmClient, String zipFileDir)StackTrace:    at NationalInstruments.NIFarm.NIFarmClient.HandleFarmResult(NIFarmResult result)   at NationalInstruments.NIFarm.NIFarmClient.IsAnyWorkAvailable(String& workerId, String& jobId)   at NI.LV.FPGA.CompileWorkerUI.CompileWorkerThreadManager.MainInfiniteLoop(Dictionary`2 sessionIdToFarmClient, String zipFileDir)CompileWorker.exe Information: 0 : 5/20/2011 11:05:47 AM UI info changed. SessionId: PO5kq2R This session is no longer in contact with the compile server. 

0 Kudos
Message 1 of 11
(4,680 Views)

I tried changing HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy to 0 and now it took the compile, but please tell me what's up with this Labview FPGA FIPS noncompliance??? 

0 Kudos
Message 2 of 11
(4,668 Views)

Hello Fedor,

 

I found a Corrective Action Request on this same problem. The 2010 FPGA Compile Worker generates an MD5 checksum during the compilation process.  The MD5 algorithm is not compliant with the Federal Information Processing Standard and an exception is thrown if a machine is configured to require FIPS cryptography.  This results in the compile worker continually starting jobs that are cancelled due to the .NET exception.

 

The workaround is to change the registry setting for FIPSAlgorithmPolicy to disabled (set to 0).  This will allow your FPGA code to compile without issue. This problem has been corrected and is set to be released with LabVIEW FPGA 2011.

 

 

0 Kudos
Message 3 of 11
(4,643 Views)

Thanks for looking into this.

 

The problem is that the policy in mandated by the domain and the suggested fix is not sustainable. Is there any other fix you could come up with?

0 Kudos
Message 4 of 11
(4,641 Views)

Changing the registry setting for FIPSAlgorithmPolicy to 0 is the only workaround at the moment. This would mean you would need to change this setting when you needed to compile.

 

Jordan

0 Kudos
Message 5 of 11
(4,625 Views)
Is there a fix planned for this yet? I have the issue with labview fpga 2012.
0 Kudos
Message 6 of 11
(4,479 Views)

My "fix" was to convince domain admins to put the PCs in question in separate GPO with relaxed registry flag as outlined above. 

0 Kudos
Message 7 of 11
(4,474 Views)

I do not think that is an option at my current organization.

0 Kudos
Message 8 of 11
(4,471 Views)

Hey Acquisition,

 

Could you please post the "workerlog.txt" file located at "C:\Program Files (x86)\National Instruments\FPGA\CompileWorker" here? I'd like to see if the error is exactly the same, or if it's a new bug.

Cheers!

TJ G
0 Kudos
Message 9 of 11
(4,468 Views)

workerLog.txt attached

0 Kudos
Message 10 of 11
(4,438 Views)