• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 454 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.

PAL video output on EVMDM365 showing garbage on lines 23 to 25

Jinh
Expert 2315 points

When I execute the demo encodedecode, there are garbage shown on line 23, 24 and 25 and the pointer I get from the function Buffer_getUserPointer points me to the next line but I need to put data in line 24 which is the first "visible" full line after the half line on 23 on field 1.  How do I manage to get data on line 24 instead of the "default" couple of solid lines?  Is it a dmai feature or something in another driver?  The frame bitmap below shows the solid white lines on the top:

 The edge data on the left I insert starting at the pointer returned from the function and adding a full line to be able to distinguish my data.  The watermark is from the frame capture software as the video was first recorded with a dvd and played back into the frame capture app.  The lines on the top though are there right at the output of the composite port on the evmdm365 board.

Thanks, Jihn T.

  • 0
    Expert 2315 points

    Something I noticed yesterday switching the system on again was that after the kernel is loaded the lines sit on the screen before executing my demo application.  This means that it is not something that the VPFE after capturing frames from the Video Pattern Generator puts there but probably the VPBE driver that powers the DAC's on the DM365.  should I look in the Linux drivers for the VPBE or is it a DM365 hardware setting on the DAC's that I should look for?

    Thanks, Jinh T.

  • 0 in reply to Jinh
    TI__Expert 3925 points

    Hi,

     

    It looks like it is getting shifted down because of some timinig parameters misamatch. Can you see if timing parameters for your mode are correct in DAC?

     

    Thanks,

    Brijesh

  • 0 in reply to Jinh
    TI__Expert 6385 points

    Hi Jinh,

    Which release are you using? Can you please try with the latest DVSDK 3.10 release if not using already to see if there have been any fixes to address this in recent releases?

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_10/latest/index_FDS.html

    Thanks,

    Sekhar

  • 0 in reply to Brijesh Jadav80
    Expert 2315 points

    I am using dvsdk_2_10_01_18 and have downloaded 3_10_00_16 a while ago but not installed it as well as 3_10_00_19 today.  We bought CCS this month and I still have to install after sorting out my workstation PC's and will then start to use 3_10_00_19.  I was hoping to finish my evaluation on 2.10 before upgrading which I will probably do as there is only some process timing issues between my synchronised camera and synchronised data over ethernet that needs to be sorted out to conclude the evaluation.  At this stage the lines are not the end of the world but do you think just upgrading to 3.10's latest release will solve the anomaly we see on the video output?

    Thanks, Jinh T.

  • 0 in reply to Brijesh Jadav80
    Expert 2315 points

    Should I look at settings in the VDAC_CONFIG register of ARM subsystem or another one?

    Thanks, Jinh T.

  • 0 in reply to Jinh
    TI__Expert 4245 points

    Hi Jinh,

    Jinh said:

    I am using dvsdk_2_10_01_18 and have downloaded 3_10_00_16 a while ago but not installed it as well as 3_10_00_19 today.  We bought CCS this month and I still have to install after sorting out my workstation PC's and will then start to use 3_10_00_19.  I was hoping to finish my evaluation on 2.10 before upgrading which I will probably do as there is only some process timing issues between my synchronised camera and synchronised data over ethernet that needs to be sorted out to conclude the evaluation.  At this stage the lines are not the end of the world but do you think just upgrading to 3.10's latest release will solve the anomaly we see on the video output?

    Thanks, Jinh T.

    We have released DVSDK 4.0 Beta (4.00.00.17) a few days back and have not observed any such issue on it. Instead of evaluating 3.10.00.16 or 3.10.00.19, I would suggest you directly evaluate 4.00.00.17. DVSDK 4.00.00.17 is available for download at http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

    --Sid