<?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>Other NXP ProductsのトピックRe: IIC specification</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715604#M19140</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Dear Xin,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;these data were tested and validated long time ago. It is difficult to answer your questions. When designing your system, please keep the timing data within the boundaries stated in the UM10204. You need to adjust the waveforms with your MCU, so it will look similar to the required waveform for the Slave you want to communicate with. It depends from component to component. But the timings must be within the boundaries state in the UM10204.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jozef&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 01 Sep 2023 07:16:22 GMT</pubDate>
    <dc:creator>JozefKozon</dc:creator>
    <dc:date>2023-09-01T07:16:22Z</dc:date>
    <item>
      <title>IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1713897#M19116</link>
      <description>&lt;P&gt;I am learning NXP UM10204, there is a question that confuses me.&lt;/P&gt;&lt;P&gt;On page 44, table 11, note3.&amp;nbsp;Why does the holding time have a maximum value？&lt;/P&gt;&lt;P&gt;In my understanding, there is usually no requirement for a maximum holding time.&lt;/P&gt;&lt;P&gt;Why data must has a valid time?&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a host, can't I keep my data valid all the time?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 08:59:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1713897#M19116</guid>
      <dc:creator>posedge_clk</dc:creator>
      <dc:date>2023-08-30T08:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1713981#M19118</link>
      <description>&lt;P&gt;Dear Xin,&lt;/P&gt;
&lt;P&gt;you probably have an older UM10204 version. Please check the UM10204 attached.&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 10:47:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1713981#M19118</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2023-08-30T10:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1714523#M19121</link>
      <description>&lt;P&gt;As shown in the following figure, i don't understand the max data valid time.&lt;/P&gt;&lt;P&gt;As a host, can't i keep the data is valid all the time until setup next data?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="posedge_clk_0-1693445138560.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/238944i0CA25B4413E43325/image-size/medium?v=v2&amp;amp;px=400" role="button" title="posedge_clk_0-1693445138560.png" alt="posedge_clk_0-1693445138560.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 01:43:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1714523#M19121</guid>
      <dc:creator>posedge_clk</dc:creator>
      <dc:date>2023-08-31T01:43:21Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1714646#M19125</link>
      <description>&lt;P&gt;Dear Xin,&lt;/P&gt;
&lt;P&gt;the tHD;DAT maximum time is not a must. It could be up to the defined maximum time, but the minimum value is also sufficient.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 05:05:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1714646#M19125</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2023-08-31T05:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1714822#M19127</link>
      <description>&lt;P&gt;What will happen if the maximum value of data valid time is exceeded ?&lt;/P&gt;&lt;P&gt;For example, in fast mode, the speccification requires the max data hold time is 900ns, what will happen if i hold it for 1us?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="posedge_clk_0-1693470155606.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/239014i520FD8E873F4D1E1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="posedge_clk_0-1693470155606.png" alt="posedge_clk_0-1693470155606.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 08:24:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1714822#M19127</guid>
      <dc:creator>posedge_clk</dc:creator>
      <dc:date>2023-08-31T08:24:09Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715023#M19129</link>
      <description>&lt;P&gt;Dear Xin,&lt;/P&gt;
&lt;P&gt;the tHD;DAT never can be longer, than tVD;DAT or&amp;nbsp;tVD;ACK. If you increase the&amp;nbsp;tHD;DAT length, the&amp;nbsp;tVD;DAT and tVD;ACK are automatically also increased.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JozefKozon_0-1693481831010.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/239086iDB6AD4A43A827516/image-size/medium?v=v2&amp;amp;px=400" role="button" title="JozefKozon_0-1693481831010.png" alt="JozefKozon_0-1693481831010.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 11:37:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715023#M19129</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2023-08-31T11:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715449#M19135</link>
      <description>&lt;P&gt;Yes, I know the&amp;nbsp;&amp;nbsp;the tHD;DAT never can be longer than tVD;DAT or&amp;nbsp;tVD;ACK.&lt;BR /&gt;But why?&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. What is the purpose of designing tVD;DAT and tVD;ACK ?&lt;/P&gt;&lt;P&gt;In the above example, I did not see any points where exceeding&amp;nbsp;tVD;DAT and tVD;ACK may cause problems.There is 300ns free time, as a host, I think i can keep the data is valid until next setup.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="posedge_clk_0-1693533260392.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/239199i98D182CD25E4DA5A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="posedge_clk_0-1693533260392.png" alt="posedge_clk_0-1693533260392.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;2. In my experience, design usually only imposes constraints on the minimum data valid time and not on the maximum data valid time. Why does this specification define the maximum data valid time?&lt;/P&gt;&lt;P&gt;3. Also, if this maximum data valid time is violated, will the slave not be able to receive data correctly？&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 02:09:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715449#M19135</guid>
      <dc:creator>posedge_clk</dc:creator>
      <dc:date>2023-09-01T02:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: IIC specification</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715604#M19140</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Dear Xin,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;these data were tested and validated long time ago. It is difficult to answer your questions. When designing your system, please keep the timing data within the boundaries stated in the UM10204. You need to adjust the waveforms with your MCU, so it will look similar to the required waveform for the Slave you want to communicate with. It depends from component to component. But the timings must be within the boundaries state in the UM10204.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jozef&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 07:16:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/IIC-specification/m-p/1715604#M19140</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2023-09-01T07:16:22Z</dc:date>
    </item>
  </channel>
</rss>

