<?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: PF0100A OTP</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304221#M38826</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Satoshi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You´re correct, the OTP_&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;FUSE_PORx&lt;/SPAN&gt; only applies for the &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt; and &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100A&lt;/SPAN&gt;, the &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;MMPF0100F&lt;/SPAN&gt;xxxx is already factory programmed, hence the final user can ignore table 2 since it only applies for&amp;nbsp; &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt; and &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt;A, not &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt;F.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Mar 2014 17:47:40 GMT</pubDate>
    <dc:creator>Joshevelle</dc:creator>
    <dc:date>2014-03-26T17:47:40Z</dc:date>
    <item>
      <title>PF0100A OTP</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304219#M38824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question about PF0100A OTP.&lt;/P&gt;&lt;P&gt;Please see Table 2 in MMPF0100 datasheet (Rev.7.0).&lt;/P&gt;&lt;P&gt;It says "It is required to set FUSE_POR1, FUSE_POR2, and FUSE_POR3 bits during OTP programming." in description of OTP_FUSE_PORx register &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;setting during OTP programming.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I understand user should note this difference only when using MMPF0100NPAxx.&lt;/P&gt;&lt;P&gt;On the other hand, all MMPF0100FxAxx OTP is programmed before shipping, so FUSE_PORx bits have already been set to "1" for MMPF0100FxAxx &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;when user get the chip.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;So user can ignore this difference when using MMPF0100FxAxx.&lt;/P&gt;&lt;P&gt;Is my understanding correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Satoshi Shimoda&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2014 04:14:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304219#M38824</guid>
      <dc:creator>satoshishimoda</dc:creator>
      <dc:date>2014-03-26T04:14:08Z</dc:date>
    </item>
    <item>
      <title>Re: PF0100A OTP</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304220#M38825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Joshevelle"&gt;Joshevelle&lt;/A&gt;, Can you please comment?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2014 15:56:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304220#M38825</guid>
      <dc:creator>jamesbone</dc:creator>
      <dc:date>2014-03-26T15:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: PF0100A OTP</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304221#M38826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Satoshi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You´re correct, the OTP_&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;FUSE_PORx&lt;/SPAN&gt; only applies for the &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt; and &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100A&lt;/SPAN&gt;, the &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;MMPF0100F&lt;/SPAN&gt;xxxx is already factory programmed, hence the final user can ignore table 2 since it only applies for&amp;nbsp; &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt; and &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt;A, not &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;PF0100&lt;/SPAN&gt;F.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2014 17:47:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/PF0100A-OTP/m-p/304221#M38826</guid>
      <dc:creator>Joshevelle</dc:creator>
      <dc:date>2014-03-26T17:47:40Z</dc:date>
    </item>
  </channel>
</rss>

