<?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>i.MX Processorsのトピックv5640mipi sensor not working!</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658724#M101072</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We used a ov5640_mipi sensor and connect with mipi-csi interface as is same to imx6dl sabresd reference board.&lt;/P&gt;&lt;P&gt;I just comment out the parrellel 0v5642 from device tree. and move the ov5640 from i2c2 to i2c1. we used i2c1. Other settings are reused the reference design with yocto imx-4.1-krogoth release.&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;ov564x_mipi: ov564x_mipi@3c { /* i2c1 driver */&lt;BR /&gt; compatible = "ovti,ov564x_mipi";&lt;BR /&gt; reg = &amp;lt;0x3c&amp;gt;;&lt;BR /&gt; clocks = &amp;lt;&amp;amp;clks 201&amp;gt;;&lt;BR /&gt; clock-names = "csi_mclk";&lt;BR /&gt; DOVDD-supply = &amp;lt;&amp;amp;vgen4_reg&amp;gt;; /* 1.8v */&lt;BR /&gt; AVDD-supply = &amp;lt;&amp;amp;vgen3_reg&amp;gt;; /* 2.8v, rev C board is VGEN3&lt;BR /&gt; rev B board is VGEN5 */&lt;BR /&gt; DVDD-supply = &amp;lt;&amp;amp;vgen2_reg&amp;gt;; /* 1.5v*/&lt;BR /&gt; pwn-gpios = &amp;lt;&amp;amp;gpio6 0 1&amp;gt;; /* active low: SD1_CLK */&lt;BR /&gt; rst-gpios = &amp;lt;&amp;amp;gpio6 1 0&amp;gt;; /* active high: SD1_DAT2 */&lt;BR /&gt; csi_id = &amp;lt;1&amp;gt;;&lt;BR /&gt; mclk = &amp;lt;24000000&amp;gt;;&lt;BR /&gt; mclk_source = &amp;lt;0&amp;gt;;&lt;BR /&gt; };&lt;/P&gt;&lt;P&gt;I see the log shows ov564x_mipi is probed, and the clk 24M is readback from DT, but when I use the scope to check the mclk pin, there is no clk here.&lt;/P&gt;&lt;P&gt;What configuration I am lost and any comments on how to check?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Wenming&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 May 2017 21:13:08 GMT</pubDate>
    <dc:creator>wenmingfeng</dc:creator>
    <dc:date>2017-05-02T21:13:08Z</dc:date>
    <item>
      <title>v5640mipi sensor not working!</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658724#M101072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We used a ov5640_mipi sensor and connect with mipi-csi interface as is same to imx6dl sabresd reference board.&lt;/P&gt;&lt;P&gt;I just comment out the parrellel 0v5642 from device tree. and move the ov5640 from i2c2 to i2c1. we used i2c1. Other settings are reused the reference design with yocto imx-4.1-krogoth release.&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;ov564x_mipi: ov564x_mipi@3c { /* i2c1 driver */&lt;BR /&gt; compatible = "ovti,ov564x_mipi";&lt;BR /&gt; reg = &amp;lt;0x3c&amp;gt;;&lt;BR /&gt; clocks = &amp;lt;&amp;amp;clks 201&amp;gt;;&lt;BR /&gt; clock-names = "csi_mclk";&lt;BR /&gt; DOVDD-supply = &amp;lt;&amp;amp;vgen4_reg&amp;gt;; /* 1.8v */&lt;BR /&gt; AVDD-supply = &amp;lt;&amp;amp;vgen3_reg&amp;gt;; /* 2.8v, rev C board is VGEN3&lt;BR /&gt; rev B board is VGEN5 */&lt;BR /&gt; DVDD-supply = &amp;lt;&amp;amp;vgen2_reg&amp;gt;; /* 1.5v*/&lt;BR /&gt; pwn-gpios = &amp;lt;&amp;amp;gpio6 0 1&amp;gt;; /* active low: SD1_CLK */&lt;BR /&gt; rst-gpios = &amp;lt;&amp;amp;gpio6 1 0&amp;gt;; /* active high: SD1_DAT2 */&lt;BR /&gt; csi_id = &amp;lt;1&amp;gt;;&lt;BR /&gt; mclk = &amp;lt;24000000&amp;gt;;&lt;BR /&gt; mclk_source = &amp;lt;0&amp;gt;;&lt;BR /&gt; };&lt;/P&gt;&lt;P&gt;I see the log shows ov564x_mipi is probed, and the clk 24M is readback from DT, but when I use the scope to check the mclk pin, there is no clk here.&lt;/P&gt;&lt;P&gt;What configuration I am lost and any comments on how to check?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Wenming&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 May 2017 21:13:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658724#M101072</guid>
      <dc:creator>wenmingfeng</dc:creator>
      <dc:date>2017-05-02T21:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: v5640mipi sensor not working!</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658725#M101073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Wenning,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You settings are no problem, but you should notice that on SabreSD board based on i.mx6dl, 24MHz MCLK was routed through GPIO_0 PAD, so it's IOMUX was degined as :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; imx6qdl-sabresd {&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;pinctrl_hog: hoggrp {&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;fsl,pins = &amp;lt;&lt;BR /&gt;...&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;STRONG&gt;MX6QDL_PAD_GPIO_0__CCM_CLKO1&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x130b0&lt;/STRONG&gt;&lt;BR /&gt;...&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; };&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&amp;nbsp;So please check your schematic, which PAD was used to output 24MHz clock for MCLK of OV5640!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC Weidong Sun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 May 2017 08:52:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658725#M101073</guid>
      <dc:creator>weidong_sun</dc:creator>
      <dc:date>2017-05-03T08:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: v5640mipi sensor not working!</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658726#M101074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Wigros,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your quick response.&lt;/P&gt;&lt;P&gt;The schematic we used is below: The&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt; &amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold; font-size: 14px;"&gt;MX6QDL_PAD_GPIO_0__CCM_CLKO1&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x130b0 &lt;/STRONG&gt;is actived in my DT settings.&lt;/P&gt;&lt;P&gt;&lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold; font-size: 14px;"&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Is there any internal connection or settings I need to check with imx6RM document?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/18953iD6C45918D6C7E23F/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Best regards!&lt;/P&gt;&lt;P&gt;Wenming&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 May 2017 13:46:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/v5640mipi-sensor-not-working/m-p/658726#M101074</guid>
      <dc:creator>wenmingfeng</dc:creator>
      <dc:date>2017-05-03T13:46:08Z</dc:date>
    </item>
  </channel>
</rss>

