<?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: LS1043A SRK REVOCATION in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1167862#M6786</link>
    <description>&lt;P&gt;I would say, unless the goal is to leave the system in a non-usable state,&lt;BR /&gt;you need both to blow a fuse and to update image headers when &lt;BR /&gt;revoking a key. The former is required to mark the key as revoked, the latter&lt;BR /&gt;have to be done to let the system use a key that remains active to validate boot&lt;BR /&gt;images.&lt;/P&gt;
&lt;P&gt;Note that NXP LS1043A-RDB is a development system. It is not designed to be used&lt;BR /&gt;as a field-deployed, end-user device. Such devices, if remote key revocation &lt;BR /&gt;is required, have to have provisions in the design to control the required&lt;BR /&gt;power supply lines in software.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Platon&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Oct 2020 01:25:07 GMT</pubDate>
    <dc:creator>bpe</dc:creator>
    <dc:date>2020-10-15T01:25:07Z</dc:date>
    <item>
      <title>LS1043A SRK REVOCATION</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1167680#M6784</link>
      <description>&lt;P&gt;I'm trying to revoke SRK in an LS1043A BOARD. I have to make this revocation for a list of 1000 boards.&lt;/P&gt;&lt;P&gt;I am confused whether or not I should blow the fuses in the SFP’s OEM Security Policy Register (SFP_OSPR) to revoke the compromised key or just I have to update the key number indicated in the CSF header.&lt;/P&gt;&lt;P&gt;The problem with blowing fuse is that I need to apply 1.8V on TA_PROG_SFP to make SFP writable and this need manual action in my case so the best way is to make it through a simple remote software update.&lt;/P&gt;&lt;P&gt;How can I manage this case?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2020 20:12:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1167680#M6784</guid>
      <dc:creator>mohamed_hamzaou</dc:creator>
      <dc:date>2020-10-14T20:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043A SRK REVOCATION</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1167862#M6786</link>
      <description>&lt;P&gt;I would say, unless the goal is to leave the system in a non-usable state,&lt;BR /&gt;you need both to blow a fuse and to update image headers when &lt;BR /&gt;revoking a key. The former is required to mark the key as revoked, the latter&lt;BR /&gt;have to be done to let the system use a key that remains active to validate boot&lt;BR /&gt;images.&lt;/P&gt;
&lt;P&gt;Note that NXP LS1043A-RDB is a development system. It is not designed to be used&lt;BR /&gt;as a field-deployed, end-user device. Such devices, if remote key revocation &lt;BR /&gt;is required, have to have provisions in the design to control the required&lt;BR /&gt;power supply lines in software.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Platon&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2020 01:25:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1167862#M6786</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2020-10-15T01:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043A SRK REVOCATION</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1168113#M6789</link>
      <description>&lt;P&gt;Thanks Platon for your answer but let me ask you some questions.&lt;/P&gt;&lt;P&gt;When you said that LS1043A-RDB is not intended for end user, I think you refer to RDB and I hope this is not the case for all LS1043A based board because I use a SoM called MPX-LS1043A2 (Microsys) based on NXP LS1043A processor.&lt;/P&gt;&lt;P&gt;Also, in the NXP documentation we can found that LS1043A is for industrial use also not only development: "&lt;SPAN&gt;This SoC is a purpose-built solution for small-form-factor networking and industrial applications with BOM optimizations for economic low layer PCB, lower cost power supply and single clock design."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Finally, if I understand your answer,&amp;nbsp;we should have designed the SoM so that the POVDD input (TA-PROG-SFP) changes the power supply state with a software way which will allow us to revoke by simple update. So, are you sure there is no other software way to revoke as the fuses are not powered with a 1.8V input to allow blowing?&lt;BR /&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2020 08:46:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1168113#M6789</guid>
      <dc:creator>mohamed_hamzaou</dc:creator>
      <dc:date>2020-10-15T08:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043A SRK REVOCATION</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1168680#M6802</link>
      <description>&lt;P&gt;&lt;BR /&gt;As I have already explained, there is no way to revoke am SRK without fuse programming,&lt;BR /&gt;which in turn requires switching PROG_SFP on and off. That is a chip-level&lt;BR /&gt;requirement. As of the third-party development system you mentioned, consult at&lt;BR /&gt;it's documentation and/or manufacturer on what features it supports and in what way.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Platon&lt;/P&gt;</description>
      <pubDate>Fri, 16 Oct 2020 07:28:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043A-SRK-REVOCATION/m-p/1168680#M6802</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2020-10-16T07:28:21Z</dc:date>
    </item>
  </channel>
</rss>

