09-03-2009 09:48 PM
I've got labview 2009, corrosponding ARM module and a Luminary LM3s8962.
Because of the size of my project I had to disable debugging to make it fit. But now that I want to start debugging, (removed a loop to make it fit) I can't get breakpoints to break and the probes don't update. I did check the debug box in the build, but it still doesn't work...
Any ideas anyone???
09-04-2009 01:47 PM
Disable/Enable debugging works well for me.
I would suggest a Rebuild All (Generate C Code... window should appear), but before doing this remember that "Enable Debugging" in "Application Information" panel don't overwrite settings from "Source File Settings".
How is the running arrow of the top level VI?
07-26-2012 04:38 PM
Aaah, time moves on and the past continues to repeat itself...
But this time I'm using labview 2011 real-time and on cRIO and PXI chases.
I'm experiencing the same problems I had before in that even though debugging is enabled. I try to debug using execution highlighting and breakpoints and they don't do jack. this is especially true if timed loops are involved. Now the processor is not anywhere near maxed out. I have pretty much given up trying to use these tools when this happens, but today a co-worker experienced the same problem and asked me what is going on.
So, Someone tell me what is going on!
07-27-2012 02:03 PM
Yes, that is one way, and it is also a great way to log initialization progress without resorting to writing a log file. But while there are work arounds I would still like to understand why the tools don't work as advertised.
Thanks for the reply.
07-30-2012 12:42 PM
You'll probably have better luck giving a complete description of the problem over at the RT Forums. Providing explicit steps for recreating what you're seeing will allow helpful people to figure out what's going on a bit faster!