AnsweredAssumed Answered

VDK State History and ADI_TOOLS_IOE

Question asked by Tim on Jul 16, 2010
Latest reply on Oct 7, 2010 by Tim

In debugging my VDK program with VisualDSP 5.0 I noticed that the thread status does not appear to plot correctly.  In the plot below the Flag_Control graph shows no status until the far right after an event occurs and then it correctly displays event blocked.  However prior to that point the Flag_Control should have been plotted as event blocked which is the normal status of that thread.  Is the no status display a limitation of the tool or am I interpreting the plot wrong?  Is the control the track a program from beginning to end?

 

A second question I have concerns the ADI_TOOLS_IOE threads.  Often times I find when my program fails due to CPU overload the 3rd instance of this thread has numerous status changes and semaphore posts.  The other two instances always appear as semaphore blocked.  What part of the VDK creates these threads, how many instances should be created, what is the function they provide?

 

VDK State History.bmp

Outcomes