01-26-2012 03:02 AM
w0utje, may I ask why you comment out the RTA? Does it take up CPU resources?
01-26-2012 03:31 AM
I was getting an error on a new labview for ARM system with the newest KEIL uVision.
Like tbet, I was getting the same error:
[quote]
O.K. - the problem could be solved by adding the include path : C:\Keil\ARM\RV31\LIB\Luminary
Anyway this failure message remains :
[10:58:29] Status: Error
Build target 'LabVIEW'
compiling RTX_Config.c...
C:\Keil\ARM\RV31\INC\RTX_lib.c(183): error: #29: expected an expression
compiling File_Config.c...
...
What to do ?
[/quote]
I looked at the code and saw that is has changed in the RTX_lib.c with code of the RTA
I never use RTA, so i comment out the define of RTA so it doesn't use it
It compiles when I comment it out.
I don't know if it takes up any resources, but
As far as I can see, RTA is for communicating with LabVIEW.
example:
you have a LabVIEW for ARM project and a VI with some indicators on the front panel.
In "normal" LabVIEW (on a pc) you press run and you see the program running, updating the indicators etc.
since I need standalone applications on an ARM I don't need debugging or this RTA agent.
if you have debugging on in you application build spec, your program won't run if you simple reset your device, it must be started with the run/debugging in LabVIEW on a PC.
also: I prefer debugging in C code in uVision (tools > ARM > open Keil) or using output on a UART/TCP