06-29-2010 04:40 PM
Also monitor the error wire if you can during debug so we can see if anything is happening after that first read.
06-29-2010 04:46 PM
crashed...let me clean up a bit, make sure none of the build specs have changed and then restart everything to get a clean load.
Back in a few...or maybe even in the morning.
Thanks.
06-29-2010 05:04 PM
ran it again...it crashed...(will explain in detail tomorrow).
Ran the example again looking for a way to monitor the error variable value with a probe...but need some help with how to do diagnostics...(just create an indicator and then rebuild?)
Thanks.
Hummer 1
06-30-2010 08:49 AM
You need to enable debugging in the Application properties (in the Application Information category) and choose the appropriate debug method (in the Advanced Debugging Options category). I use my JTAG connector because you can see the block diagram in highlight execution just like you would for a VI on Windows. I use this type of debugging along with probes to see what the code is doing.
If you don't have a JTAG or can't get the TCP or Serial debugging to work, then programmatic things like blinking an LED if there is an error can be helpful.
06-30-2010 09:17 AM
We have a JTag, but haven't used it yet...looks like it is time to break it out.
Thanks.
Will post again when we have done that.
Hummer1
06-30-2010 11:20 AM
Hummer1,
Here is a great help file on setting up Blackfin application for debugging and your options (http://zone.ni.com/reference/en-XX/help/371653C-01/lvblackfinhelp/bf_debugging/). Check it out when setting up your application later.
07-02-2010 12:55 PM
The JTAG devise is attached but we are trying the RTC periodic example. It fails when the ezToggleLED.dll is changed to the ToggleLED.vi...we get a KernelPanic. I posted this on another thread...Thanks.
Hummer1