• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 305 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.

Does OMAP3530 support parallel 8bit Y + 8-bit C camera input?

Smokensparks
Intellectual 440 points
Other Parts Discussed in Thread: OMAP3530, AM3505

Hi,

My customer needs to interface OMAP3530 to a camera that has the following parallel output .  (Camera manufacturer calls this "BT.601" mode)

- 8 bits luminance

- 8 bits chrominance

- pxl clock

- HSYNC

- VSYNC

Does OMAP3530 support this mode?

Thanks,

Rick

 

  • 0
    TI__Intellectual 1280 points

    The parallel interace on OMAP3530 only supports up to 12 bits and not 16.  It supports following...

    • Up to 8-bit data at 130 MHz can be transferred to memory.

    • Up to 10-bit data at 75 MHz can be processed by the image pipeline or transferred to memory.

    • Up to 12-bit data at 75 MHz can be transferred to memory as is, or after processing.

    If your customer does not need ISP specific features of OMAP3530, they may want to look at AM3505/17 which does support 16-bit YCbCr format with discrete syncs.

     

     

     

     

     

     

     

     

     

     

  • 0 in reply to JamesJ35562
    Prodigy 10 points

    I'm confused about this answer because we had assistance from TI in order to connect with a camera that provides 16 bits of data which is grayscale intensity (our data path allows for RGB color data but I believe we are only retrieving grayscale data from the camera). We were instructed to use the “bridge” with an appropriate clock to split the data and to reintegrate it. The answer from the TI employee “JamesJ” here comes from the TI tech ref manual (SPRUF98G) on page 1310, 12.1.1. The problem with this answer is that the same lines quoted from the manual are also brought down on page 1392-3, section 12.4.6.11, with the following clarification of the CCDC interface: “It is a 16 bit interface. To raise this maximum 16-bit interface, the bridge data-lane shifter before the CCDC module allows the packing of 8-bit data into 16 bits (not supported with ITU mode)”. In section 12.4.5 of the same manual (page 1392), it further clarifies the role of this bridge data-lane shifter: “An optional bridge allows the packing of bytes into 16-bit words. When it is used, the maximum data rate allowed is increased. The placement of 8-bit data inside 16-bit words is configurable through the ISP_CTRL [3:2] PAR_BRIDGE register.” It seems that the correct answer is that if the two bytes of 8-bit data are properly clocked into the data inputs of the camera interface, they can be packed together in memory by means of use of this bridge.

     

    The remaining questions for me and my colleague, Dan, who already asked this question on this forum, but has not yet gotten any answers, are

    (1)   How we would set up the ISP registers to get it to pipe our data directly to memory, and

    (2)   How we would go about creating (or modifying) a driver to produce V4L2 output from that data?

  • 0 in reply to Norman Tuttle
    TI__Intellectual 1280 points

    Smokensparks wrote the following post at Thu, Aug 19 2010 1:07 PM:

    Norman,

    Some clarification...The parallel camera interface on OMAP3530 is only 12 bits as I mentioned...cam[d11:d0] but connection between bridge lane shifter and CCDC is 16 bits...D[15:0].  In regards to your comment, if camera you are connecting to 3530 parallel interface output sends 16 bits/pixel then data can be transmitted through 8 data lines at x2 pixel clock and bridge can be used to reassemble the 16-bits/pixel as noted.  In regards to your 1st question, if you want to pipe data directly to memory from CCDC, please reference 'write to memory' function in Table 12-51 of TRM (SPRUF98F).  I will ask a colleague of mine to comment on your 2nd question.

     

     

     

  • 0 in reply to Norman Tuttle
    TI__Intellectual 1665 points

    Norman,

     

    We have example applications in our PSP release which show how one can write to and read buffers and map them to V4l2 space. Please refer the saUserptrDisplay.c file in the examples folder, you can find more information on v4l2 driver at http://v4l2spec.bytesex.org/spec/

     

    Thanks, Punya

    ---------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    ---------------------------------------------------------------------------------------------------------