<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: i.MX6Q video capture issue with ADV7280-M in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329837#M44452</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Saurabh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the link. I wonder if you could clarify for me section C.2 of the doc &lt;/P&gt;&lt;P&gt;regarding the writes in PHY_TST_CTRL1 register as they are not documented in&lt;/P&gt;&lt;P&gt;the i.MX6 RM. The MIPI-CSI2 driver in our kernel does the following writes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PHY_TST_CTRL0 = 0x00000001&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL1 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000002&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL1 = 0x00010044&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL1 = 0x00000014&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000002&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;According the doc for a MIPI clock of 108 MHz the value of 0x40 needs to be&lt;/P&gt;&lt;P&gt;written to PHY_TST_CTRL1, but how does that fit in the above sequence?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Jan 2015 16:31:32 GMT</pubDate>
    <dc:creator>stathisv</dc:creator>
    <dc:date>2015-01-29T16:31:32Z</dc:date>
    <item>
      <title>i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329835#M44450</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the VAR-SOM-MX6 custom board from Variscite and the ADV7280-M EVM.&lt;/P&gt;&lt;P&gt;The I2C and MIPI lines of the 2 boards are connected in order to capture video.&lt;/P&gt;&lt;P&gt;The ADV7280-M has been configured to use VC1 and is therefore routed to CSI-1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to use the Freescale mxc_v4l2_capture.out application to capture into a file.&lt;/P&gt;&lt;P&gt;However, no frames become available for dequeing and when I print out the contents&lt;/P&gt;&lt;P&gt;of the MIPI_CSI_ERR1 register bits 0 (start of TX error on data lane 0) and 28 (header&lt;/P&gt;&lt;P&gt;ecc contains 2 errors) are set. The contents of MIPI_CSI_PHY_STATE indicate that&lt;/P&gt;&lt;P&gt;the MIPI clock from the video decoder is being detected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this just down to H/W (cabling issues) or some configuration issue?&lt;/P&gt;&lt;P&gt;The video decoder outputs interlaced video and the MIPI clock rate is 108 MHz.&lt;/P&gt;&lt;P&gt;Is there some clock setting on the i.MX6 side that needs to be configured to match that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jan 2015 06:18:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329835#M44450</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-01-29T06:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329836#M44451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please go through the&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-94312"&gt;Debug steps for customer MIPI sensor.docx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Saurabh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jan 2015 06:53:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329836#M44451</guid>
      <dc:creator>saurabh206</dc:creator>
      <dc:date>2015-01-29T06:53:45Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329837#M44452</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Saurabh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the link. I wonder if you could clarify for me section C.2 of the doc &lt;/P&gt;&lt;P&gt;regarding the writes in PHY_TST_CTRL1 register as they are not documented in&lt;/P&gt;&lt;P&gt;the i.MX6 RM. The MIPI-CSI2 driver in our kernel does the following writes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PHY_TST_CTRL0 = 0x00000001&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL1 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000002&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL1 = 0x00010044&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL1 = 0x00000014&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000002&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;PHY_TST_CTRL0 = 0x00000000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;According the doc for a MIPI clock of 108 MHz the value of 0x40 needs to be&lt;/P&gt;&lt;P&gt;written to PHY_TST_CTRL1, but how does that fit in the above sequence?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jan 2015 16:31:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329837#M44452</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-01-29T16:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329838#M44453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can look also&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/message/328301"&gt;Some Experience When Enable MIPI Camera&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Feb 2015 08:57:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329838#M44453</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2015-02-05T08:57:50Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329839#M44454</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had seen that thread and it actually helped me to configure the MIPI-CSI2 DPHY&lt;/P&gt;&lt;P&gt;correctly to match the frequency of the ADV7280-M MIPI clock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can now grab frames but the video is not correct and bit 0 of IPU_INT_STAT_5 &lt;/P&gt;&lt;P&gt;gets set, meaning a new frame before end-of-frame error. Do you have any tips on&lt;/P&gt;&lt;P&gt;what may cause that? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From what I can see the IPU clock is running at 264 MHz and the pixel clock&lt;/P&gt;&lt;P&gt;at 198 MHz.&lt;/P&gt;&lt;P&gt;My path is to capture video through CSI1 to memory, without going through the IC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Feb 2015 14:59:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329839#M44454</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-05T14:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329840#M44455</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you can decrease frame rate from sensor&lt;/P&gt;&lt;P&gt;so IPU had time to process frames.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Feb 2015 15:37:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329840#M44455</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2015-02-05T15:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329841#M44456</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your reply. &lt;/P&gt;&lt;P&gt;The sensor is capturing NTSC resolution at either 60 fields/sec or 60 frames/sec,&lt;/P&gt;&lt;P&gt;ie I have tried both interlaced and progressive output from the sensor, as it has that option.&lt;/P&gt;&lt;P&gt;As explained earlier the MIPI clock rate fro the sensor is 108 MHz for interlaced or 216 MHz &lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; font-size: 13.3333330154419px;"&gt;for progressive.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;According to the Freescale doc mentioned earlier in this thread, the IPU and pixel clock that&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;I have should be fast enough?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Stathis&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Feb 2015 15:46:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329841#M44456</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-05T15:46:33Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329842#M44457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this may depend on processor bus loading, so this frequency may not&lt;/P&gt;&lt;P&gt;be sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Feb 2015 01:48:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329842#M44457</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2015-02-06T01:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329843#M44458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem solved! &lt;/P&gt;&lt;P&gt;The clocks were OK. It looks like the 'v_channel' property of the MIPI-CSI2 device tree node &lt;/P&gt;&lt;P&gt;needs to be set to 0, although the sensor transmits at MIPI Virtual Channel 1. The value from the &lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;device tree &lt;/SPAN&gt;is used by the IPU driver to configure the SMFC_MAP register, so I do not think it has&lt;/P&gt;&lt;P&gt;anything to do with the MIPI Virtual Channels, despite its name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Feb 2015 23:08:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329843#M44458</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-10T23:08:40Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329844#M44459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks like I have a same problem that you solved. What value did you set in the "PHY_TST_CTRL1" register?&lt;/P&gt;&lt;P&gt;- When I set 0x40 (108 MHz) I have an error in the MIPI_CSI_ERR1 register.&lt;/P&gt;&lt;P&gt;- When I set 0x26 (216 MHz) - MIPI_CSI_ERR1 is cleared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks like it is necessary to set double freq...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Yury.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Feb 2015 14:40:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329844#M44459</guid>
      <dc:creator>yurykocherov</dc:creator>
      <dc:date>2015-02-19T14:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329845#M44460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yury,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's correct. The value that you set in PHY_TST_CTRL1 corresponds to the received bit rate.&lt;/P&gt;&lt;P&gt;Since the MIPI link captures at double data rate (DDR), ie both edges of the clock, the bit rate&lt;/P&gt;&lt;P&gt;will be double the clock rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Feb 2015 10:09:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329845#M44460</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-23T10:09:58Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329846#M44461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much! It gives me one more correct value!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Yury.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2015 06:28:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329846#M44461</guid>
      <dc:creator>yurykocherov</dc:creator>
      <dc:date>2015-02-24T06:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329847#M44462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yury,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are welcome! Have you got video capture working now with the ADV7280-M?&lt;/P&gt;&lt;P&gt;I wonder if I could ask you about a strange issue that I see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) I program the device registers and enable MIPI TX by writing 0x00 to CSI reg[0x00] on the ADV7280-M&lt;/P&gt;&lt;P&gt;2) From that point it starts capturing frames OK&lt;/P&gt;&lt;P&gt;3) If I do a register read on the ADV7280-M (eg STATUS1) it seems to stop capturing any more frames.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is, if I read a register while MIPI is active then it does not give me any more frames.&lt;/P&gt;&lt;P&gt;The I2C read itself succeeds and returns the expected value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2015 17:03:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329847#M44462</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-24T17:03:40Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329848#M44463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, I have started capturing via adv7281-m. :smileyhappy:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding your question: I don't work with I2C line after enable MIPI TX (writing 0x00 to CSI reg[0x00]). I will try to repeat it on my equipment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One question, do you have captured video correct? Because I see that my video scrolling vertically time to time... I am capturing NTSC video (adv7281m in auto detect mode) so dimensions are 720 x 480. IPU registers shows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[54820.153681] imx-ipuv3 imx-ipuv3.0: IPU1_INT_STAT_1 =&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x08800000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[55331.874591] imx-ipuv3 imx-ipuv3.0: CSI_SENS_CONF =&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x04000A00&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[55331.874609] imx-ipuv3 imx-ipuv3.0: CSI_SENS_FRM_SIZE = 719 x 524&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[55331.874627] imx-ipuv3 imx-ipuv3.0: CSI_ACT_FRM_SIZE = 719 x 479&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These values I see every time and when video scrolling, and when video normal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you seen something like this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Yury.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Feb 2015 07:04:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329848#M44463</guid>
      <dc:creator>yurykocherov</dc:creator>
      <dc:date>2015-02-25T07:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329849#M44464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yuri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No, I did not have any problem with scrolling lines. It could be a vertical locking issue maybe?&lt;/P&gt;&lt;P&gt;You could configure the adv7281-m in free-run mode with the boundary box pattern and &lt;/P&gt;&lt;P&gt;check if that works OK or you see the white line of the pattern scrolling. It that is all OK it could&lt;/P&gt;&lt;P&gt;be your video source to blame.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would really appreciate it if you could do a quick test for my issue, although your device is &lt;/P&gt;&lt;P&gt;slightly different. You could just add in your driver a read of eg. the STATUS1 register just &lt;/P&gt;&lt;P&gt;after you enable MIPI TX. If I do that I do not get any video.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Feb 2015 13:53:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329849#M44464</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-25T13:53:06Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329850#M44465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stathis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have done this short test. My result - all works OK. Below my debug output:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Power-up MIPI part of AFV7281-M:&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 80.815408] ADV7280: Dbg: adv7280_write_config[0]: reg = 0xde, value = 0x02&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 80.823417] ADV7280: Dbg: adv7280_write_config[1]: reg = 0xd2, value = 0xf7&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 80.832851] ADV7280: Dbg: adv7280_write_config[2]: reg = 0xd8, value = 0x65&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 80.840092] ADV7280: Dbg: adv7280_write_config[3]: reg = 0xe0, value = 0x09&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 80.847676] ADV7280: Dbg: adv7280_write_config[4]: reg = 0x2c, value = 0x00&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 80.855104] ADV7280: Dbg: adv7280_write_config[5]: reg = 0x00, value = 0x00&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (with pause 255 ms after)&lt;/P&gt;&lt;P&gt;2) Readout iMX MIPI status:&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.130975] ADV7280: Trace: adv7280_wait_mipi_ready&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.135871] ADV7280: Dbg: mipi_csi2_dphy_status = 0x0300&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.141233] ADV7280: Dbg: mipi_csi2_error1 = 0x0000&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.146900] ADV7280: Dbg: mipi_csi2_error2 = 0x0000&lt;/P&gt;&lt;P&gt;3) Readout ADV7281-M status:&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.151837] ADV7280: Trace: adv7280_show_status&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.156970] ADV7280: Dbg: Status1 = 0x0D&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.161519] ADV7280: Dbg: Status2 = 0x00&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.165724] ADV7280: Dbg: Status3 = 0x69&lt;/P&gt;&lt;P&gt;4) Readout iMX MIPI status:&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.169659] ADV7280: Trace: adv7280_wait_mipi_ready&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.174588] ADV7280: Dbg: mipi_csi2_dphy_status = 0x0300&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.180424] ADV7280: Dbg: mipi_csi2_error1 = 0x0000&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp; 81.185708] ADV7280: Dbg: mipi_csi2_error2 = 0x0000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And after that I can see captured image.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Yury.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Feb 2015 14:47:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329850#M44465</guid>
      <dc:creator>yurykocherov</dc:creator>
      <dc:date>2015-02-25T14:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329851#M44466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yury,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for doing the test.&lt;/P&gt;&lt;P&gt;What I get in step 4 is DPHY status 0x0200, meaning that the i,MX does not see a clock any more.&lt;/P&gt;&lt;P&gt;I think it is a H/W issue, we improved the grounding between the 2 boards and now it does&lt;/P&gt;&lt;P&gt;seem to work occasionally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stathis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Feb 2015 21:59:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329851#M44466</guid>
      <dc:creator>stathisv</dc:creator>
      <dc:date>2015-02-26T21:59:58Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329852#M44467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would deeply appreciate if someone can upload a patch file for the changes that are required to be made in the kernel to capture video via mipi interface from ADV-mipi video decoder. Kind of facing similar issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanking in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Faisal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Apr 2015 12:01:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329852#M44467</guid>
      <dc:creator>faisaltaj</dc:creator>
      <dc:date>2015-04-10T12:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329853#M44468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I am also facing the problem of capturing frames from ADV7280M. I am using custom encoder board connected to IMX6q module from Toradex, which was tested and worked fine with other SOC (Tegra3).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently I'm using modified ov5640_mipi driver (with 3.10.17 kernel) and configure the ADV7280M to work in free-run mode with colorbars (480p). I've only changed the virtual channel to 1 (0x0D MIPI-CSI register)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try to capture an image I use gstreamer:&lt;/P&gt;&lt;P&gt;gst-launch -v mfw_v4lsrc device=/dev/video2 capture-mode=1 ! mfw_v4lsink&lt;/P&gt;&lt;P&gt;and I am getting a timeout error:&lt;/P&gt;&lt;P&gt;ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0&lt;/P&gt;&lt;P&gt;No sync interrupts appeared (iMX6 register IPUx_INT_STAT_1 = 0), no CSI errors occured (MIPI_CSI_ERR1 = MIPI_CSI_ERR2 = 0),&lt;/P&gt;&lt;P&gt;bit 8 of MIPI_CSI_PHY_STATE is 1, which means the pixel clock is being received properly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would also deeply appreciate any patches or hints....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Wojtek B.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 14:26:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329853#M44468</guid>
      <dc:creator>wojtekbe</dc:creator>
      <dc:date>2015-05-20T14:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6Q video capture issue with ADV7280-M</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329854#M44469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hallo Stathis,&lt;/P&gt;&lt;P&gt;Would you please share yor driver? I am also trying to interface adv7280-m with imx6q. The driver with kernel 4.1.15 does not work with imx6.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hasan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Jul 2016 23:02:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6Q-video-capture-issue-with-ADV7280-M/m-p/329854#M44469</guid>
      <dc:creator>arslan</dc:creator>
      <dc:date>2016-07-17T23:02:29Z</dc:date>
    </item>
  </channel>
</rss>

