08-30-2023 10:56 AM
Hi.
I have a labview project with a sbRIO real-time target. I can successfully build both the real-time application and the fpga using their respective build specifications. However when I try to build it from the command line (setting up a script for continous integration), the FPGA build fails with the following error:
Error Code : 1370
Error Message : mxLvErrorHandler.vi:2660001
An error occurred while running the ExecuteBuildSpec operation.
This is the command I try to execute:
"labviewcli.exe -OperationName ExecuteBuildSpec -ProjectPath "C:\labview_CI_test\lv_ci_test_rt\utilities\build_scripts\..\..\src\lv_ci_test_rt.lvproj" -TargetName "FPGA Target" -BuildSpecName "FPGA""
I know that the paths and target names etc. resolves correctly as if I change any of them I get more descriptive file not found errors.
Anyone know what the problem might be?
System info:
LabVIEW 2020 SP1 32-bit
Windows 10
03-20-2025 05:51 AM - edited 03-20-2025 05:54 AM
Hello oakl,
This thread is a bit old but I am encoutering the same problem. I am trying to build a fpga dummy project to see if we could include the fpga build process in our CI.
I tried with the following command:
LabVIEWCLI -OperationName ExecuteBuildSpec -ProjectPath "C:\Users\LCLMATCUST\Desktop\testFPGA\testFpga.lvproj" -BuildSpecName main -TargetName "FPGA"
and received the following error :
LabVIEWCLI started logging in file: C:\Users\LCLMATCUST\AppData\Local\Temp\lvtemporary_346158.log
"LabVIEWPath" command line argument is not passed. Using last used LabVIEW: "C:\Program Files (x86)\National Instruments\LabVIEW 2019\LabVIEW.exe"
Connection established with LabVIEW at port number 3363.
Operation output:
Error Code : 1370
Error Message : mxLvErrorHandler.vi:2660001
An error occurred while running the ExecuteBuildSpec operation.
ExecuteBuildSpec operation failed.
Have you found a solution to this issue?
Best regards,
03-20-2025 06:50 AM
I think building in LabVIEW FPGA is a different call (see how it is in VI Server) than it is with LabVIEW for Desktop (windows).
There are 'hidden gems' in the RVI folder of LabVIEW.
03-20-2025 06:56 AM
Hi Terry,
I thank you for your message. I have found this article in the knowledger base
Looks like I could try to use niFpgaBuild_GenerateCode and niFpgaBuild_Compile to try to build something that would be able to build and manage the result. I have also asked the NI support if they have something more official to support this use case. If I come to something interesting, I will repost here.
03-20-2025 08:46 AM
Here I could manage to have something that could work. But I don't know for how long since we are not supposed to use directly some of the used VIs.
In appendix I have joined a projet called testFpga.lvproj with a dummy fpga vi that juste do a simple calculation (main.vi). In the "My Computer" target there is a vi called fpgaAutoBuild.vi that used two vi that every installation of labview should include. I have set the connector pane as documented here (RunVI - LabVIEW Wiki) to allow the vi to be execute from the Labview CLI.
The following command should launch the build process of the fpga vi
LabVIEWCLI -OperationName RunVI -VIPath "Path to fpgaAutoBuild.vi" "path to testFpga.lvproj" FPGA main
Hope this example will help
Regards,
Arnaud