• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 532 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.

AM437x VPFE features

Kanae
Guru 10085 points

Hi all,
I would like to make sure AM437x VPFE features.

TRM 14.1.1 is shown "support for up to 16-bit input".
However Unsupported feature is shown "16-bit input".

My customer needs the 16-bits input feature.
Can AM437x VPFE support 16-bit input?
If it does not support, is there any workaround?

Best regards,
Kanae

  • 0
    TI__Guru* 86540 points
    The VPFE module can support 16-bit, however, only 12-bits are externally available on the AM437x interface. AM437x can support a single port 12-bit interface or a dual port 8/10 bit BT656 interface.

    Regards,
    James
  • 0 in reply to JJD
    Guru 10085 points

    Hi James,

    Thank you for your reply.

    I still cannot understand that "the VPFE module can support 16-bit".
    How the VPFE module can support 16-bit input internally?
    Could you please explain the specific example?

    I agree AM437x VPFE cannot support 16-bits input externally
    because of only ccdc_data[11:0] pinned out.
    However if it suports 16-bits input internally, I would like to know
    the way of 16-bit input from FPGA signal using other pins such as GPIOs.
    Is it possible to realize this?

    Best regards,
    Kanae

  • 0 in reply to Kanae
    TI__Guru* 86540 points
    Simply put, the AM437x only supports 12-bit camera input. There is no way to support 16-bit input. The system integration of the module limits its full capabilities.

    Regards,
    James
  • 0 in reply to JJD
    Guru 10085 points


    Hi James,
    Thank you for your reply.

    My understanding is that VPFE of AM437x cannot support 16-bit input both internally and externally.
    Is it correct?

    If so, why is TRM described "Support for up to 16-bit input"?
    I suppose it makes confusing to anyone.

    Do you know a plan to revise this feature on TRM? 

    Best regards,
    Kanae