<?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中的主题 Re: ADV7280-m clock issue</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488573#M78262</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please create new thread for new questions&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 May 2016 01:58:04 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2016-05-05T01:58:04Z</dc:date>
    <item>
      <title>ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488561#M78250</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;Currently I am working on driver integration task for adv7280-m chip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And I got issue related to mipi csi clock. Mipi dphy driver detect Clock line as ULPS(ultralow power state).&amp;nbsp; You can see my &lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN&gt;oscilloscope images in this branch &lt;A href="https://ez.analog.com/thread/83191" title="https://ez.analog.com/thread/83191"&gt;adv7280-M clock problem | EngineerZone&lt;/A&gt; .&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;I am trying to understand what could be the reason of issue: adv7280-m chip or imx6. Could anybody, who&amp;nbsp; worked with this adv7280-m chip show me your signals on the mipi lines or analize my signals. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;I also interested in what should be switched on first: the decoder chip mipi dphy or&amp;nbsp; imx6 &lt;SPAN class="short_text" lang="en"&gt; mipi dphy&lt;/SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;As I understand. there are a lot of people who managed to get workable adv7280-m chip with imx6. Could you also share your mipi csi2 driver settup&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Apr 2016 12:10:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488561#M78250</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-04-29T12:10:01Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488562#M78251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Fan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest to configure properly i.MX6 mipi clock as described in&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;A href="https://community.nxp.com/thread/386395"&gt;A Simple tutor for writing i.MX6 mipi driver, use adv7480 as an example&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;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Apr 2016 13:58:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488562#M78251</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-04-29T13:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488563#M78252</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;Thank you for replay. I will examine the experience and patches for adv7480.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know whether I will see mipi clk sygnal&amp;nbsp; on the clk wire in case of wrong mipi clock configuration in imx6 processor?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Apr 2016 15:24:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488563#M78252</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-04-29T15:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488564#M78253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;actually adi support suggested easy way to debug that&lt;/P&gt;&lt;P&gt;as described in AN1337 on p.2:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;manually program the clock lane of the ADV7280-M, ADV7281-M&lt;/P&gt;&lt;P&gt;to enter and then exit LP mode. The easiest way to do this is by&lt;/P&gt;&lt;P&gt;toggling the CSITX_PWRDN bit (Address 0x00, Bit 7).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data and clock lanes can enter ulps state independently, for clock lane&lt;/P&gt;&lt;P&gt;one can follow comand given on p.52&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.analog.com/media/en/technical-documentation/evaluation-documentation/ADV7280_7281_7282_UG-637.pdf" title="http://www.analog.com/media/en/technical-documentation/evaluation-documentation/ADV7280_7281_7282_UG-637.pdf"&gt;http://www.analog.com/media/en/technical-documentation/evaluation-documentation/ADV7280_7281_7282_UG-637.pdf&lt;/A&gt; .&lt;/P&gt;&lt;P&gt;also please check&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/340563"&gt;i.MX6Q video capture issue with ADV7280-M&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2016 00:51:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488564#M78253</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-05-02T00:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488565#M78254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I of course tried all of these debug steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See below my oscilloscope images.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Low state mode: CSITX_PWRDN bit (Address 0x00, Bit 7) contains 1 value.&lt;/P&gt;&lt;P&gt;Mipi data:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_20160502_122426.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/56544iAC8CB5D45A6810E6/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_20160502_122426.jpg" alt="IMG_20160502_122426.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Mipi clk:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_20160502_122508.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/56367iEEE960C3EF263EEF/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_20160502_122508.jpg" alt="IMG_20160502_122508.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;2) Switching on to high speed mode: set CSITX_PWRDN bit (Address 0x00, Bit 7) in zero value.&lt;/P&gt;&lt;P&gt;Mipi data in high speed mode:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_20160502_122640.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/56377i2E2183A46F23251B/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_20160502_122640.jpg" alt="IMG_20160502_122640.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Mipi clk in high speed mode:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_20160502_122734.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/56427iC84A90D2394285A2/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_20160502_122734.jpg" alt="IMG_20160502_122734.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transient process from low power to high speed on mipi clk line:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_20160502_123107.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/56472i8BE6E0479E36C933/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_20160502_123107.jpg" alt="IMG_20160502_123107.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I switch on imx6 dphy(mipi_csi2_reset()) after clearing CSITX_PWRDN in ad7280-m, I get 0x200 in State register. If I switch on imx6 dphy before clearing CSITX_PWRDN, I get 0x210 in State register.&lt;/P&gt;&lt;P&gt;3) Just for experience: set both lines to ULPS mode, regarding to &lt;A class="jive-link-external-small" data-content-finding="Community" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.analog.com%2Fmedia%2Fen%2Ftechnical-documentation%2Fevaluation-documentation%2FADV7280_7281_7282_UG-637.pdf" rel="nofollow" target="_blank"&gt;ADV7280_7281_7282_UG-637.pdf&lt;/A&gt; documet P.52&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For both lines:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_20160502_124723.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/56497i5D93709DDB625501/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_20160502_124723.jpg" alt="IMG_20160502_124723.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;You can see, that MIPI lines pulled down in real ULPS mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also looked through this brunch &lt;A _jive_internal="true" data-containerid="2004" data-containertype="14" data-content-finding="Community" data-objectid="340563" data-objecttype="1" href="https://community.nxp.com/thread/340563"&gt;i.MX6Q video capture issue with ADV7280-M.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;But I think my problem is a little be different, as I can`t see clk sygnal physically. There could be several reasons for this issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) imx6 incorrect terminates mipi clk line. To exclude this version, It could be useful if anybody could show his mipi clk sygnal in case of switched off imx6 dphy and switched on dphy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) ad7280 incorrect pass clk sygnal. To exclude this issue I need to get example of clean mipi sygnal&amp;nbsp; from ADV7280-m with disconnected from mipi slave device wires.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) hardware issue on my board&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Than you for help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2016 11:12:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488565#M78254</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-05-02T11:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488566#M78255</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;Do you think it is correct that transition from 1.2V to 0.1-0,2V on CLK line was detected as ULPS by imx6(0x210 in state register)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 07:23:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488566#M78255</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-05-03T07:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488567#M78256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think yes it can be detected in MIPI_CSI_PHY_STATE register bit 9.&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>Tue, 03 May 2016 08:12:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488567#M78256</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-05-03T08:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488568#M78257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;But ULPS mode should have 0V level on lines. In our case we have 0,1-0,2V and it is high speed level according to DPHY specification.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 09:24:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488568#M78257</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-05-03T09:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488569#M78258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are you sure that this is not noise, as is ULPS mode&lt;/P&gt;&lt;P&gt;sensor can turn off supplies from lane.&lt;/P&gt;&lt;P&gt;Also this can be quality issue, so recommended to double&lt;/P&gt;&lt;P&gt;check behaviour on other board/sensor.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 09:29:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488569#M78258</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-05-03T09:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488570#M78259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I understand, imx6 should detect 1.2 &amp;gt;0.1V transition(low power -&amp;gt; high speed) and set termination on the line. If&amp;nbsp; it detect this transition as ULPS, it of course will not set termination and future signal on the line will be not correct(noise in my case as you said).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have any opportunity to get signal oscilloscope&amp;nbsp; images in case of correct imx6-adv7280-m work?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 09:46:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488570#M78259</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-05-03T09:46:10Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488571#M78260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have not adv7280 but one can attach external termination resistors and check.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 11:47:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488571#M78260</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-05-03T11:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488572#M78261</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately it is difficult to solder this termination resistor on our board. May be we will order ADV7280-m kit and connect it to CM-FX6 kit or Sabre board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you explane me some points related to MIPI_CSI_PHY_STATE. &lt;/P&gt;&lt;P&gt;First of all 9-th bit. Active low. Is that mean that clk lane in ULPS if the bit equel zero value?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;8-th bit. Clock lane actively receiving a DDR cloclk. Is that bit mean(1-value) that imx6 DPHY module clock is correctly configured. In my case it is always zero value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2016 13:50:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488572#M78261</guid>
      <dc:creator>kurkinalexandr</dc:creator>
      <dc:date>2016-05-04T13:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7280-m clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488573#M78262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please create new thread for new questions&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 May 2016 01:58:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7280-m-clock-issue/m-p/488573#M78262</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-05-05T01:58:04Z</dc:date>
    </item>
  </channel>
</rss>

