<?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>topic Re: OTP on Layerscape in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1163207#M6743</link>
    <description>&lt;P&gt;Which exactly processor is in question?&lt;/P&gt;</description>
    <pubDate>Tue, 06 Oct 2020 04:50:40 GMT</pubDate>
    <dc:creator>ufedor</dc:creator>
    <dc:date>2020-10-06T04:50:40Z</dc:date>
    <item>
      <title>OTP on Layerscape</title>
      <link>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1163123#M6742</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; Is there any sort of serial number or ID marked in the layerscape di?&amp;nbsp; Apart from Zone-of-Trust HSK, is there any ability to set an identifying serial number per device?&amp;nbsp; I would simply like to read a number in U-Boot and pass it to the Linux application, which is a unique number identifying the device.&amp;nbsp; If necessary, I will use the Security Secret Key, but exposing this in Linux Configuration space would be a security risk&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2020 21:09:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1163123#M6742</guid>
      <dc:creator>mrmichaelt86</dc:creator>
      <dc:date>2020-10-05T21:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: OTP on Layerscape</title>
      <link>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1163207#M6743</link>
      <description>&lt;P&gt;Which exactly processor is in question?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 04:50:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1163207#M6743</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2020-10-06T04:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: OTP on Layerscape</title>
      <link>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1166138#M6759</link>
      <description>&lt;P&gt;Processor in Question:&amp;nbsp; LS1046A&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 14:15:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1166138#M6759</guid>
      <dc:creator>mrmichaelt86</dc:creator>
      <dc:date>2020-10-12T14:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: OTP on Layerscape</title>
      <link>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1166208#M6760</link>
      <description>&lt;P&gt;Security fuse processor (SFP) contains 64-bit Factory Unique ID in two 32-bit registers (FUIDR0/1).&lt;/P&gt;
&lt;P&gt;The FUIDR is set (and write protected) by NXP prior to part shipment to provision a&lt;BR /&gt;pseudo-random software readable value, which can be (optionally) included as part of the&lt;BR /&gt;digital signature that is validated by the ISBC. This allows OEMs to create images that&lt;BR /&gt;can only pass secure boot on a specific chip. OEM can consider this to be an unalterable&lt;BR /&gt;highly unique value for the purposes of chip identification.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 16:09:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1166208#M6760</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2020-10-12T16:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: OTP on Layerscape</title>
      <link>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1315430#M8596</link>
      <description>&lt;P&gt;Hi. Is there something similar for the LX2160?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jul 2021 17:49:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/OTP-on-Layerscape/m-p/1315430#M8596</guid>
      <dc:creator>guignbt2v</dc:creator>
      <dc:date>2021-07-29T17:49:21Z</dc:date>
    </item>
  </channel>
</rss>

