• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 101 subscribers
  • Views 639 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DM8168 HDVPSS TRM and Docs

Colin Hankins
Intellectual 570 points
Other Parts Discussed in Thread: TVP5150AM1, TVP5150

HI, how can we obtain the HDVPSS TRM and other technical documentation detailing the processes in the HDVPSS?

We are having difficulty capturing and displaying NTSC video with the TVP5150AM1 and feel we could finish the project if we had a full understanding of what is taking place inside the HDVPSS. 

  • 0
    TI__Guru**** 397370 points
    Hi Colin,

    You could contact your local TI FAE to get the details.
    But i dont think you really need it. NTSC is correctly being output on SDVENC. There is no issue, did you try NTSC output from SD VENC.
    TVP5150 is input chip, it is used to capture data on the VIP port. VIP is just a port, it will capture whenever there is data.
    It looks like TVP is not configured correctly so not outputting data.. can you please check the configuration..

    Rgds,
    Brijesh
  • 0
    TI__Guru**** 170625 points
    Colin,

    Until you get the DM816x HDVPSS TRM from your local TI FAE, you can use the similar DM38x HDVPSS TRM which is public:

    www.ti.com/.../spruhi7a.pdf

    Regards,
    Pavel
  • 0 in reply to Brijesh Jadav
    Intellectual 570 points
    Thank you Brijesh.

    We are using the saLoopBackScale demo and have removed the scaling. We see the image but it looks like the top and bottom are slightly cropped. And the frame rate is a little low.

    The bigger issue is with the saLoopBackFbdev demo which acquires and converts to RGB, then we display it through a graphics channel. We see the same top and bottom cropping issue and a few other problems.

    1. It looks like the very first frame is read but is never overwritten in later acquisition. So as the buffers are looped through in the acquire/display loop, you see the current image with every other buffer but then the first buffer displays the original acquisition.

    2. It also looks like each frame being displayed is only one field of the interlaced frame.
  • 0 in reply to Pavel Botev
    Intellectual 570 points
    Thank you. I will go through that until I can get the DM816x docs.