I've recently begun having some issues with compilation failures,
resulting in an error code 6. Unfortunately, suggestions on this topic
in other posts have not fixed the problem.
I'm trying to compile code for a 9505 Servo Drive Module onto a
cRIO-9103 FPGA (there is also a cRIO-9004 attached). To test the error,
I put together a very simple VI that just sets the drive direction and
offers control of the motor. I've attached a screenshot of the VI as
well as the actual VI at the end of this message for anyone who may
have a similar setup and who can test the code. The code was written in
LV 8.0.1, using LV FPGA 8.0. I have NI-RIO 2.0.1 installed on my
computer.
Here's a copy of the last few lines of the compile report, which
includes the error code (the whole compile report is included as an
attachment):
Entity <XNode_h14268238_n3a4_000007e8> compiled.
ERROR:HDLParsers:837 -
"C:/NIFPGA80/srvrTmp/LOCALH~1/CRIODE~1/XNode_h14268238_n3a4_000007e8.vhd"
Line 106. Index size for dimension 1 of s000059e4 is not 8.
-->
Total memory usage is 87596 kilobytes
Number of errors : 1 ( 0 filtered)
Number of warnings : 1 ( 0 filtered)
Number of infos : 0 ( 0 filtered)
ERROR:Xflow - Program xst returned error code 6. Aborting flow execution...
I have been able to compile code that utilizes these functions for the
9505 in the past without any errors. I started seeing this error after
accidentally saving the Drive Direction typedef in LV 8.2 in order to
debug some supporting code... I couldn't save the typedef back to LV
8.0.1, so I went through and uninstalled FPGA 8.0 and reinstalled it. I
came across the same error again, so I created a new VI (the one
included below) in a new project and tried another compile but came
across the same error.
Has anyone had problems with this in the past? More importantly, does
anyone have suggestions on how to fix it? I think I might try to
uninstall both NI-RIO and FPGA 8.0 and start fresh from there, but I'm
not sure if this will fix things. I'm also a little confused as to what
is actually causing the error-- is it the change to the typedef that
triggered it, or is there something else under the hood that is causing
the compiler to fail? It might be a good sanity check to see if anyone
else has problems with the VI that I've included, but please be careful
not to corrupt your own development environment with the file I've
provided in case there is something wrong with the file.
Thanks for your help...
Mountain Goat
