• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 285 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

video processing frame lost

shimon akrish
Prodigy 110 points

Normal 0 false false false EN-US X-NONE HE

Hello

I'm using the TMS320DM6437 EVM, and developing in CCS v3.3 + flashburn DSK v3.11

My project is based on "Accessing_Pixels_In_A_Frame_1_03"  

In this project I receive NTSC video and applying some video manipulations (Zoom with the resizer and histogram equalization (HE)) and then output the manipulated video.

The manipulations supposed to be in real time, I checked the processing time and it's less than 30ms per frame).

The problem:

When I'm watching the results in the monitor for +-15 min everything is working great but after that some frames aren't processed, I am starting see flashes of unprocessed frame.

Tried many thing but nothing worked…

 

 

Thank you for your time

              Shimon akrish

  • 0
    TI__Mastermind 41665 points

    Since your issue seems to only happen after ~15 minutes, my first guess would be that there is some sort of memory overflow problem going on which builds up but takes that long to get to a failure state. Unfortunately since it sounds like your code has been modified quite a bit from the original accessing pixels in a frame example it is hard to say waht could be wrong with it.

    In general, I have not seen the accessing pixels in a frame project have this sort of problem after 15 minutes or longer, but the project was never really tested and validated as a ‘production’ reference design, it was more of an example test case. One thing you could try to do is step back your changes until you stop seeing the failure, as I imagine something that was added to the accessing pixels in a frame project is what is leading to the problem. In any case I think this will require some debugging, stepping through and verifying the frame pointers make sense when it gets into the bad state.