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

I'm having problem capturing data from ISIF

Person Lin
Intellectual 610 points
Other Parts Discussed in Thread: TVP5158, TVP5150, TVP7002

Hi,

I have modified the mcvip test program of UDWORK reference design to capture image.
It could receive the correct image if soruce is bt656.
However, it got the green image from 1080p in YCC16bit.

This YCC 16bit signal was verified by another chip mdin-275, so I think the source is ok.

The green image is captured from the following blue path.

I already set the registers listed below.

1.  MODESET.INPMOD = 1 (0x01c71004= 0x1084)
2.  REC656IF.R656ON = 0 (0x01c71084 = 0x0)
3.  CCDCFG.YCINSWP=0 && CCDCFG.BW656 = 0 (0x01c71088 = 0x8802)
4.  Both CCD[15:0] and YI[7:0] / CI[7:0] are input
5.  CAM_VD, CAM_HD and CAM_WEN_FIELD are input
6.  PINMUX0 (0x01C40000) = 0xFD0000
7.  LNH=0x87f, LNV=0x45f, VDINT0=0x43b
8.  0x1c71004 = 0x1080
9.  0x01c71230 = 0x8
10. 0x01c71204 = 0x40c

B.R.

 

  • 0
    TI__Mastermind 19985 points

    Hi,

    DVR Ref Design uses TVP5158 for multiplexed capture. Did you remove that and connect any other input sensor or ADC to get 1080P input? Is the UV data captured as output of ISIF coming out correct?

    mcviptest.out is configured to demultiplex multiple D1 channel inputs and then do resize operation on them. Not sure if you have removed multiplexing and the trying to capture your frame output at resizer.

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Intellectual 610 points

    Hi,

    1. Yes, I did. We could capture frame from the external camera in bt656 without TVP5158.

    2. We have tried two kinds of sources to connect our board, but the other one is 720P YCC 16bit. The results are similar.

    Best Regards,

    Person

  • 0 in reply to Person Lin
    TI__Mastermind 19985 points

    Hi,

    What APIs are you calling to capture the data from the sensor? Are you getting a complete frame during capture? Can you share the YUV data that is dumped into the DDR after ISIF? I am still concerned that the changes done in mcviptest.out to capture single channel might not be complete and hence causing the problem, but i can comment better after looking at the YUV data.

    BTW, why are you using DVR Ref Design for implementing single channel capture solution. I would recommend looking at somethign like IPNC Ref Design which is single channel system, although the framework for both of them is same.

     

    Regards,

    Anshuman 

  • 0 in reply to Anshuman Saxena
    Intellectual 610 points

    Hi,

    1. Capturing data still comes from csl_ccdc driver. I modified the v4l/mcvip functions such as MCVIP_isifSetParams, mcvip_demux....

    I just bypass the frame in the mcvip_demux because our input source is progssive mode.

    2. The attachment is data that was captured after ISIF. 1780.IMG_after_isif.zip

    3.We don't need the ISP function and our functions of product similar to DVR reference design. The approach of IPCAM is more complex for this project.

    By the way, we did a product using tvp5150 and DVR reference design.

     

    Best Regards,

    Person

  • 0 in reply to Anshuman Saxena
    Intellectual 610 points

    Hi Anshuman,

    Do you have any idea?

    Regards,

    Person

  • 0 in reply to Person Lin
    TI__Mastermind 19985 points

    Can you provide the resolution of the YUV data?

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Intellectual 610 points

    Hi,

    The resoultion is 2176x1120.

    Regards,

    Person

  • 0 in reply to Person Lin
    TI__Mastermind 19985 points

    Hi,

    Do you have a TI DM365 EVM and can you run the encode demo with HD input coming to TVP7002? TVP7002 also gives 16 bit YUV output. Using that ou can compare the registers. It is just the register configuration that is wrong for ISIF that is causing this problem.

    Let me know if you want me to dump the registers for TVP7002 input configuration and share it with you.

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Intellectual 610 points

    Hi,

    Sure, please kindly dump the registers for TVP7002.

    The following result is our register setting.

    [ISIF]

    root@192.168.3.27:~# devmem 0x01c71000 0x100

    /dev/mem opened.

    Memory mapped at address 0x40020000.

         memory address: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f

    01c71000 - 01c7100f: 03 00 00 00 84 10 00 00 00 00 00 00 00 00 00 00

    01c71010 - 01c7101f: 00 00 00 00 01 00 00 00 00 00 00 00 7f 08 00 00

    01c71020 - 01c7102f: 00 00 00 00 00 00 00 00 5f 04 00 00 ff ff 00 00

    01c71030 - 01c7103f: ff 00 00 00 88 00 00 00 00 00 00 00 2b 04 00 00

    01c71040 - 01c7104f: 00 9f 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    01c71050 - 01c7105f: 00 02 00 00 00 02 00 00 00 02 00 00 00 02 00 00

    01c71060 - 01c7106f: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    01c71070 - 01c7107f: 3b 04 00 00 3b 04 00 00 3b 04 00 00 00 00 00 00

    01c71080 - 01c7108f: 00 00 00 00 00 00 00 00 02 88 00 00 00 00 00 00

    Regards,

    Person

  • 0 in reply to Person Lin
    TI__Mastermind 19985 points

    Following are our registers

    00000  00000001 00001000 00000000 00000000
    00010  00000000 00000000 00000000 000004FF
    00020  00000001 00000001 000002CF 0000FFFF
    00030  000000FF 00000050 00000000 00000000
    00040  00000000 00000000 00000000 00000000
    00050  00000200 00000200 00000200 00000200
    00060  00000000 00000000 00000000 00000000
    00070  000002CF 00000169 00000000 00000000
    00080  00000000 00000003 00000800 00000000
    00090  00000000 00000000 00000000 00000000
    000A0  00000000 00000000 00000000 00000000
    000B0  00000000 00000000 00000000 00000000
    000C0  00000000 00000000 00000000 00000000
    000D0  00000000 00000000 00000000 00000000
    000E0  00000000 00000000 00000000 00000000
    000F0  00000000 00000000 00000000 00000000
    00100  00000000 00000000 00000000 00000000
    00110  00000000 00000000 00000000 00000000
    00120  00000000 00000000 00000000 00000000
    00130  00000000 00000000 00000000 00000000
    00140  00000000 00000000 00000000 00000000
    00150  00000000 00000000 00000000 00000000
    00160  00000000 00000000 00000000 00000000
    00170  00000000 00000000 00000000 00000000
    00180  00000000 00000000 00000000 00000000
    00190  00000000 00000000 00000000 00000000
    001A0  00000000 00000000 00000000 00000000
    001B0  00000000 00000000 00000000 00000000
    001C0  00000000 00000000 00000000 00000000
    001D0  00000000 00000000 00000000 00000000
    001E0  00000000 00000000 00000000 00000000
    001F0  00000000 00000000 00000000 00000000
    00200  00000000 00002000 00000000 00000000

  • 0 in reply to Anshuman Saxena
    Intellectual 610 points

    Hi Anshuman,

    This problem was solved.

     I just rebuilt the source code, dvsdk and kernel.

    I don't know what is real root cause.

    Thanks for your help!!