ISS and VPSS video capture?

It appears that the "capture" link (Vcap) is what I'm looking for. Are there any samples showing this link working, the required configuration parameters, and/or gotchas that I need to be aware of?

Or, even better, some documentation for the Links architecture in general and the Vcap link specifically?

Thanks,
Chris

Hi Chris,

I suggest that you should upgrade to the latest release ver 3.0.0 for IPNC RDK. For doing VPSS capture you should use the Capture link. 

Brief documentation for Capture link is included in the release package.

Regards,

Rajat

Hi Chris,

I was wondering if you wouldn't mind sharing with me if there were significant changes you had to make to the IPNC camera code to get it to work with the 8148EVM and the5MP imager through the stock daughercard. We just started looking into doing that ourselves with version 3.0 of the software and its not going smoothly. If you had no problems with 2.0 maybe we will drop back to that version and try it. Anything your willing to share would be greatly appreciated!

Thanks,

Mark

Mark,

V2.0 has been the most stable for me so far. I attempted to use the v2.8 build but because of the file system corruption and the difficulty in getting the build to run correctly on the 8148 EVM, I gave up. I have v3.0 and will be trying it shortly.

I'm not using the stock daughter card -- I'm using my own custom interface to the parallel interface. Nothing special, but I had to comment out a bunch of the "board detect" type i2c code. The biggest problem was finding and fixing all of the random (uint*)0x12341234 = 0x1234123 type register modifications littered throughout the code. Why the obvious "FVID2_setPixelClockInvert()" functions couldn't have been used instead, I really don't know. And right there I've given away what cost me the vast majority of time: the IPNC has an FGPA that inverts the pixel clock. If you want to use your own camera, and you don't have the matching inversion, you'll have to set that register correctly.

I also had to rewrite the i2c driver for my sensor. It's a standard Aptina sensor, but I couldn't make it work in 16 bit address mode. I had to rewrite it for 8 bit.

Good luck,
Chris

Thanks for the information Chris. It's always nice to know that what your trying to do is actually doable!

We'll be looking at 3.0 over the next few days. If we run into any surprises that we solve we'll be sure to pass them on to you as well.

~Mark

Hi Mark, 

B.t.w we have validated the ver.3.0 release on EVM+VCAM daughtercard configuration. But the validation was done with MT9j003 sensor.

Please let us know if you face any problems with MT9P031.

Regards

Rajat

I think we have a major failure in the design of all TI image sensor processing systems: http://free-electrons.com/pub/video/2011/elce/elce-2011-pinchart-camera-stack-nokia-n9.webm

The answer isnt to endlessly patch bugs in a bad design with cheaply outsourced engineers, but to fix the design.

Hi Rajat,

Thanks for the information. It's good to know that its been validated with some sensor on the EVM. Two quick questions for you:

First can you tell me where to get the VCAM daughter-card. I have the video conferencing card, the security camera card, and the I/O card, but I have never heard of of the VCAM card. If its not easily accessible can you get me the schematics for it so i can compare it to the cards we do have?

Second I'm having a little trouble recompiling the IPNC 3.0 code for the EVM. It appears that when it builds the kernel it chooses the defconfig based on a combination of the platform, the system, and the IPNC_Filesystem defined in the Rules.make file. However, when looking in the configs folder for the kernel there are defconfigs that combine the ipnc along with a chosen file system type. But none that work for the EVM and a file system type, as a result whenever i try to compile for the EVM it throws an error when it gets to building the kernel. Can you tell me what parameters were chosen in the Rules.make file to validate the MT9j003 on the EVM?

Thanks!!

~Mark

Hi mkeramaty, 

You should be able to get the VCAM from the same source you got VC / VS daughtercards. VCAM is also made by Mistral. Please do send me the security camera card serial number, I just want to make sure its not the same as VCAM. 

I apologies for your inconvenience as we have missed the EVM defconfigs in the release package. I'll be updating the release package, meanwhile I have attached the defconfigs in this post.

Regards

Rajat

Rajat,

Thank you very much for posting the def configs. I greatly appreciate it. We will take a shot at getting things to compile for the EVM again today.

The Video Security Board serial number is NVA_1009116. It looks like it was made for the 816x originally.Is there a separate one for the 814x that might have the connector for the imager on it?

Is there a serial number, or specific name I should ask for when I ask for the VCAM board? Until then is there any chance you could pass on a schematic to me so that we could compare ti to our custom daughter-card?

Again, thank you for your time! We really appreciate it.

~Mark

Mark, 

The schematics are NDA and cannot be shared in this forum. Can you please ask the local TI representative to get it for you.

Regards

Rajat