<?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>Vybrid Processors中的主题 Re: 128-bit unique chip identifier</title>
    <link>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357254#M3665</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan,&lt;/P&gt;&lt;P&gt;there is "only" 64-bit unigue ID on the Vybrid (OTP Bank 0 word 1 and 2). 128 bit can be achieved by combining this and some unused space in OTP block.&lt;/P&gt;&lt;P&gt;But generally just 64 unigue ID from the factory.&lt;/P&gt;&lt;P&gt;/Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Mar 2015 07:09:29 GMT</pubDate>
    <dc:creator>jiri-b36968</dc:creator>
    <dc:date>2015-03-31T07:09:29Z</dc:date>
    <item>
      <title>128-bit unique chip identifier</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357253#M3664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to the Reference Manual Rev. 7, Chapter 2.2 Feature Set, the device supports a "128-bit unique chip identifier". However, the only unique chip identifier I found so far is the 64-Bit long "&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Device Unique ID" in the fuses&lt;/SPAN&gt; (OCOTP_CFG0 and OCOTP_CFG1). Is there another unique ID or is the feature set wrong about the length of this unique chip identifier?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2015 09:47:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357253#M3664</guid>
      <dc:creator>falstaff</dc:creator>
      <dc:date>2015-03-27T09:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: 128-bit unique chip identifier</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357254#M3665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan,&lt;/P&gt;&lt;P&gt;there is "only" 64-bit unigue ID on the Vybrid (OTP Bank 0 word 1 and 2). 128 bit can be achieved by combining this and some unused space in OTP block.&lt;/P&gt;&lt;P&gt;But generally just 64 unigue ID from the factory.&lt;/P&gt;&lt;P&gt;/Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Mar 2015 07:09:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357254#M3665</guid>
      <dc:creator>jiri-b36968</dc:creator>
      <dc:date>2015-03-31T07:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: 128-bit unique chip identifier</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357255#M3666</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Vybrid Security manual &lt;EM&gt;Table 6-2. BOOT eFuse Descriptions&lt;/EM&gt;&lt;/STRONG&gt; mentions some sub-field definitions.&amp;nbsp; If the sub-fields are correct then you can verify if chips are from a similar run.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Mar 2015 17:24:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/128-bit-unique-chip-identifier/m-p/357255#M3666</guid>
      <dc:creator>billpringlemeir</dc:creator>
      <dc:date>2015-03-31T17:24:13Z</dc:date>
    </item>
  </channel>
</rss>

