Hello:
I have two tasks running on a DM6437: a capture task, and another computation task. The capture task looks a lot like video preview example (capture/display). The capture task has the highest priority. The computation task is "nearly" unrelated to the capture task and it takes much longer than 30 ms to complete. (Lets assume the two tasks are completely unrelated for this question).
All are compiled with Software Pipelining disabled (-mu) with the hopes that the capture task can smoothy capture every frame. When the computation task is running though, the capture/display are not perfectly smooth. I am observing odd timing on a GPIO and oscilloscope. Is there something besides software pipelining that could affect the interrupt handling in the capture drivers? When the code from the computation task is replaced by a function that "wastes" the same or more time (a "for" loop with some conditionals) the capture/display are smooth.
Maybe software pipelining is not really disabled? How can I tell?
What else, besides software pipelining could impact the capture tasks interrupt handling?
bandeg