• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 840 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.

The issue about DM368 with Sony ITN2 platform video output

Justin_Liu
Intellectual 260 points

Dear All:

We use Sony ITN2 with IMX136 sensor base on DM368, and have a problem about the video output from DM368.

The IMX136 send YUV data at7.5fps to ITN2, and the Sony ITN2 send a YUV4:2:2 at 30fps,1080P data to DM368.

There are the video output from DM368 and can be download via the below link:

  1. ITN2_7.5_TI_30.avi  => Framerate to 30fps.
  2. ITN2_7.5_TI_8.avi    => Framerate to 8fps.

https://www.dropbox.com/sh/yn3fe30of07kddb/d4LzlTZVTe?lst#/

 

There is the question:

Can we modify the VD interrupt setting from DM368 to capture the correct frames?

 or any ideas to solve this issue?

 

Thanks.

 

 

===================================================

Green is VD.

Yellow is test pulse for DM368 check VD interrupt timing.

We found test pin is not sync with VD signal even in 30fps mode.

========================================

 

7.5fps

 

 

 

30fps

 

 

 

 

 

Best Regards,

Justin

 

 

  • 0
    TI__Guru 58890 points

    Yes, the VD interrupt timing may need adjustment if you use IPNC RDK S/W.

    Your ISIF VDINT0/1/2 are set to 0x2c0 (704) which is for 720P in RDK (not 1080P).

  • 0 in reply to Gang Hua
    Intellectual 260 points

    Dear Gang Hua:

     

     

    Thanks for your reply.

     

    I modify the VD interrupt register setting to YUV 16-bit 1080p, and the issue still not be solved.

    Should I do anything to change this VDINT0/1/2 settings? or any solution about this?

     

    0x01c71000: 00000001   00001080   00000000   00000000

     0x01c71010: 00000000   00000001   00000000   000007ff

     0x01c71020: 00000001   00000001   0000021f    0000ffff     

     0x01c71030: 000000ff    00000078   00000249   00000000      

     0x01c71040: 00000000   00000000   00000000   00000000

     0x01c71050: 00000200   00000200   00000200   00000200

     0x01c71060: 00000000   00000000   00000000   00000000

     0x01c71070: 0000021f   00000000   00000000   00000000

                             VDINT0      VDINT1       VDINT2

     0x01c71080: 00000000   00000003   00000800   00000000

     

     

     

     

    Best Regards,

    Justin

  • 0 in reply to Justin_Liu
    TI__Guru 58890 points

    I am not sure what you are doing here: "I modify the VD interrupt register setting to YUV 16-bit 1080p, and the issue still not be solved."

    Do you use TI's DM36x IPNC RDK S/W?

  • 0 in reply to Gang Hua
    Intellectual 260 points

    Dear Gang Hua:

     

     

    Yes, I use TI DM36x IPNC RDK version 3.1.0, and modify the VD interrupt setting.

    But the video output from DM368 looks like the same.

    Do you have any suggestion for ISIF register VD interrupt setting?

    Thanks.

     

     

    Best Regards,

    Justin

  • 0 in reply to Justin_Liu
    TI__Guru 58890 points

    RDK sets the VD timing according to the sensor input size.
    So, your sensor size may not be set properly, since the VD is set for 720P rather than 1080P.

    There is one line in DRV_isifSetParams() for VD timing setup in RDK 5.1 (RDK 3.1 shall be similar):
        vdInt = ((Uint32)gDRV_isifObj.imgsModeInfo.sensorDataHeight-32);
    You may trace the problem from there.