DM365: Direct feed camera

Hello,

Which PSP version and kernel version are you using ?

Cheers,
--Prabhakar Lad

Hi Prabhakar,

I am using the TI DVSDK 4_02_00_06 and the PSP version that was included with it. The PSP version 03.01.01.39 and the kernel in that is at 2.6.32.17.

Thank You,
George

Hello,

simple way could be remove/comment out all the subdev calls from the driver. I dont have the driver handy or else i could have made changes for you.

Cheers,
--Prabhakar Lad

Hi Prabhakar,

I am new to the whole Davinci TI stuff and v4l2. I started out with the TVP7002 driver, which had a lot of I2C control data passing back and forth which I removed since the camera is always on. The sub device was giving me a problem when it was registering because it was null, which it looked like the TVP7002 read information over the I2C bus from the sensor and created that structure. So I created a structure for the sub device which gets the driver and VPFE up and running. When I go to use the driver with gstreamer it hangs accessing something in the driver with no messages. I will be at my computer in about a half hour and so and can share more of the code and logs, if you are willing to help. Do you have any suggestions on a driver to use as the starting point? From what I understand since the data feed is already existing and needs no configuration I just need to get a driver in place to configure the VPFE since there isn't a direct way of doing it (what I gathered from the forums and documentation). So the driver is just tricking the VPFE, with a dummy decoder that configures the VPFE for the BT656 data stream.

Thank You Again,
George

Hi,

If you can attach the driver files removing your changes i can give you the diff to remove the subdev calls.

Cheers,
--Prabhakar Lad

Hi Prabhakar,

Thank you so much. I have attached two drivers not sure which one I should use for what i am trying to accomplish. I attached the TVP7002.c, TVP514x.c and .h file. Not sure which one to use.

Link to zipfile
www.dropbox.com/.../Drivers.zip

Thank You Again,
George

Hello,

I was asking for the capture driver the VPFE.

Cheers,
--Prabhakar Lad

Hi Prabhakar,

I apologize for the misunderstanding here is the link to the vpfe capture driver.

www.dropbox.com/.../vpfe_capture.zip

Thank You,
George

Hi Prabhakar,

Was the last post of files the ones that you needed for modification?  Just want to make sure I have given you the right files.  I look forward to the patch so that I can see what portions of the coded needed to be removed.

Thank You,

George

Hi,

Sorry maybe I misread your question which camera do you have is it i2c/spi interfaced ? or is it a fpga connected to capture pins ?
I suspected you had fpga connected when you mentioned dummy driver .

Cheers,
--Prabhakar Lad

Hi Prabhakar,

Yes it is a FPGA connected to c0-c7 and pclk. It is always on as soon as power is applied and sends bt656 formatted video.

Thank you
George

Thank you for the help, I do see the comments and will work on getting this working, thank you again for the help.

-George

Hi Prabhakar,

I was able to incorporate your changes in the driver and it looks like it loads properly. I still am not getting any video data. I had a question that you may know the answer to, does the VPFE support NTSC Square Pixel Format? That is the format the FPGA is sending, and I don't see anywhere in the documentation where it is supported, the resolution is different than std NTSC and the pixel clock frequency is different.

Thank You,
George

Hello,

Sorry was busy with other stuff. what do you mean by square pixel ?

What is your FPGA output ? yuv/raw bayer ?

Cheers,
--Prabhakar Lad

Hi Prabhakar,

No worries, the FPGA outputs BT656 square pixel variation with a 24.54MHz clock used for 525/60 video systems (640x480active resolution). Which is YUV, I am trying to use the BT656 capabilities to decode the video, but the decoder never receives a SAV. The actual format of the video isn't listed anywhere in the DVSDK. I appreciate that you responded back.

Thank You,
George

Hi,

what YUV format is it ? YUV422 ?
Are you getting proper HSYNC and VSYNC signals ?

Cheers,
--Prabhakar Lad

Hi Prabhakar,

It is embedded sync from the following doc and excerpt from page 2:

www.intersil.com/.../an9728.pdf

Square Pixel Variation

A variation using square pixels has been developed,
although not endorsed by the BT.656 standard. Instead of a
27MHz clock, a2 4.54MHz clock is used for 525/60 video
systems (640x480 active resolution), and a 29.5MHzclock is
used for 625/50 video systems (768x576 active resolution).

I created a test fixture for the camera using a ADV7393 video decoder that can decode the signal when the registers are set for this
format but cannot decode the signal when set to BT656 8-bit standard, the chip directly supports the following formats:

640 × 480 I 29.97 24.54 NTSC Square // configuration works
720 × 480 I 29.97 27 ITU-R BT.601/656 // does not decode signal


This is what prompted me to ask the question. I am trying to get the camera manufacturer to provide firmware that outputs YUV with
HSYNC and VSYNC signals.

Thanks,
George

Hello,

The driver is configured to work with separate syncs ie HSYNC and VSYNC and not with embedded syncs.

Cheers,
--Prabhakar Lad

Hi Prabhakar,

Thank you for the reply, is there a way to configure the driver for embedded sync such as BT656 standard format. The VPFE documentation does state that it supports standard BT656 at the standardized clock rates.

Thank You,
George

Hello,

Oops sorry my bad, it should work with BT656 standard format (embedded sync).

Look at this register REC656IF in [1]

[1] www.ti.com/.../sprufg8c.pdf

Cheers,
--Prabhakar Lad

Hi Prabhakar,

I configured it for REC656IF but I believe that I am not seeing the SAV because the clock is not the standard frequency and resolution is VGA. Other chipsets allow adjusting of the parameter but the DM365 looks like a black box it is either on or off. Since the camera is not sending true BT656 data according to the specification, I believe that it isn't decoding it. Just trying to get verification whether I am doing something wrong or it truly isn't supported. I found the following posts that kind of hint to it not being supported.

e2e.ti.com/.../25683

Thank You,
George