dm6446 preview engine hangs

Is there a reason you are using the beta 02.00.00.00.110 software as opposed to the release 02.00.00.140 software which is included in the officially released DVSDK.  Beta software tends to be more buggy than release software.

Hi Juan,

I just tried it on the release 2.00.00.140 and i got the same results. The Previewer would just hang.

-clint

Hi Juan,

Any updates or ideas as to why the previewer would hang on the dm6446?

No idea clint, I have not played with previewer much.  Perhaps someone more knowledgeable in this area can help.

Hi Juan,

Can you ask anyone at TI, perhaps the driver author as to why this is happening. I would assume that TI has tested the previewer driver on the DM6446 extensively.

thanks!

Does anybody here in the forum ran into the same problem with the previewer on dm6446 hanging?

I have also experienced the same problem in dm6446 but the data path in my case is ccdc -> ddr2 --> previewer --> ddr2 (file). I am operating previewer in one-shot mode, after capturing few frames it used to hang.

It seems this is a known issue and a workaround is mentioned (not yet tried) in the silicon errata available here: http://focus.ti.com/lit/er/sprz241m/sprz241m.pdf

Have a look at page 31 of this document (Advisory 2.1.37) to see if your problem is similar to what is explained there.

--

Best Regards

Arun

Hi Arun,

This is basically the problem I'm having. So if I understood the workaround correctly: everytime i need to use the previewer, i have to do the ff:

while()

{

    read raw frame; 

    FMTCFG.VPEN = 0

    DoPreview()

 FMTCFG.VPEN = 1

}

thanks!

Sorry clints, I can't help you, but I have a problem to submit to you. I have ordered a MT9v024 headboard to develop an application with evm648 or evm6437, but I can not receive datasheet from aptina yet and I don't know why. Can you help me?!

Regards,

   David

david,

you can use the mt9v022 data sheet, they are practically the same sensor.

clints said:

while()

{

    read raw frame; 

    FMTCFG.VPEN = 0

    DoPreview()

 FMTCFG.VPEN = 1

}

Clint, are you using H3A at all?  If not, I would disable H3A and simply set VPEN=0 all the time.  Did you have success implementing this work-around?

Hi,

Can you please clarify following?

a) What is the data source of the preview engine? Is it DDR2 or the video port?

b) Are you using H3A as well?

Regardless of whether H3A is used or not, if the preview engine is sourcing data directly from the video port, the advisory would not be applied to your case. However, if preview engine is getting data from DDR2 and H3A is used, would it be possible for you to turn off H3A module and check if the preview engine works fine with one-shot mode only i.e. data sourced from DDR2?

Prateek

Hello Prateek,

In my case preview engine gets input from DDR2 but H3A was enabled (FMTCFG.VPEN=1). As per your suggestion I disabled H3A (VPEN=0) with preview engine set in one-shot mode. It seems the preview engine is not hung any more.

Thanks for your help.

--

Best Regards

Arun

Hi Prateek,

We are sourcing the data from DDR (ccdc -> ddr -> previewer -> ddr -> file). I believe I have the H3A enabled, how do I check if this is enable or not?

The previewer is set to one-shot mode.

I'm still experiencing the problem.

thanks!

btw, how do I disable the H3A (VPEN = 0)?

thx!

Check Section 5.7.2 and 5.8.2 of the VPFE USer Guide - you will need to disable AEW, AF, Histogram module

http://focus.ti.com/general/docs/litabsmultiplefilelist.tsp?literatureNumber=sprue38e