• Resolved

DLPC3436: 3D support: How the AP will generate 3DR to FPGA

Prodigy 100 points

Replies: 3

Views: 29

Part Number: DLPC3436

As we know DLPC3436 supports 3D by input to FGPA the pin "FPGA IN_3DR" as mentioned in http://www.ti.com.cn/cn/lit/ds/symlink/dlpc3436.pdf page 25.

The questions is how the AP (Android system) could output this signal to the FPGA, in terms of software and hardware?

In hardware, I believe we have to connect a GPIO to FPGA from the AP.

In software, will an 3D player in Android be able to drive this GPIO?

The question might be a bit out of scope for DLPC3436, but it is related, and may help others who need to understand how 3D works. I believe TI expert understand the full picture, and would be much appreciated if it could be helped. 

  • Hi Jimmy, 

    Welcome to TI E2E Forums! Our expert will look at your query and get back soon. 



    Regards,

    Mayank

  • In reply to Mayank Khandelwal:

    Jimmy,

    Your frontend (Android in this case) needs to be able to provide the 3D signal in the format specified in the DLPC3436 datasheet.

    http://www.ti.com/lit/ds/symlink/dlpc3436.pdf

    In particular, you should have a signal that differentiates between left eye frame and right eye frame. Whether or not this is supported out of the box by your system will likely depend on the 3D frame format used by your video player.

    Let me know if you have further questions.

    Regards,

    Philippe Dollo

    If a post answers your question, please click the "Verify Answer" button.

  • In reply to Philippe Dollo:

    Thanks Philippe anyway.

    For others who may want to understand this, It looks to me that:

    1. the Video player needs to output the correct resolution and fps according to the TI document. 

        it is both software and hardware issue. As software needs to output correct resolution and fps. and hardware will needs to support these resolutions and fps.

    2. the GPIO toggling to indicate left and right frames.

        This is also both software and hardware issue. As software needs to drive the GPIO, while Android system needs to expose this gpio for the software to access. I am not sure there is an standard android API supporting this.