<?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: 1 ROT+IMG key for MCXN546 Not Working in MCUXpresso Secure Provisioning Tool</title>
    <link>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1919220#M412</link>
    <description>&lt;P&gt;Hello Assaf,&lt;/P&gt;
&lt;P&gt;I confirm this bug in the SEC v8, that is fixed in the upcoming v9 (stay tuned this week). The unused key slots must be configured in the CMPA - v9 takes the care, while in the v8 you have to do it manually in the RoTK_USAGE register:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="liborukropec_0-1722242238257.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/290695i657C27D3EABBBF50/image-size/medium?v=v2&amp;amp;px=400" role="button" title="liborukropec_0-1722242238257.png" alt="liborukropec_0-1722242238257.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to wait for SEC v9.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using just 1 key seems like corner case and I'm interested about the use case; recommended is to use all 4 slots to be able do key revocation in the future.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Libor&lt;/P&gt;</description>
    <pubDate>Mon, 29 Jul 2024 08:41:49 GMT</pubDate>
    <dc:creator>liborukropec</dc:creator>
    <dc:date>2024-07-29T08:41:49Z</dc:date>
    <item>
      <title>1 ROT+IMG key for MCXN546 Not Working</title>
      <link>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1918544#M410</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to build signed image for MCXN546 using NXP secure provisioning tool.&lt;/P&gt;&lt;P&gt;When I'm generating 4 ROT+IMG keys everything works well. However, when I'm using a single key, "Write Image" step fails. I suspect the tool generate wrong certificate block for images with single ROT+IMG keys.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mosesrs_0-1722169266627.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/290621iA77907A640856750/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mosesrs_0-1722169266627.png" alt="mosesrs_0-1722169266627.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please verify this?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 28 Jul 2024 12:21:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1918544#M410</guid>
      <dc:creator>mosesrs</dc:creator>
      <dc:date>2024-07-28T12:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: 1 ROT+IMG key for MCXN546 Not Working</title>
      <link>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1918547#M411</link>
      <description>&lt;P&gt;Attached image is wrong. here is the correct screenshot:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mosesrs_0-1722169369027.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/290622iF352F76C587219F6/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mosesrs_0-1722169369027.png" alt="mosesrs_0-1722169369027.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 28 Jul 2024 12:22:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1918547#M411</guid>
      <dc:creator>mosesrs</dc:creator>
      <dc:date>2024-07-28T12:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: 1 ROT+IMG key for MCXN546 Not Working</title>
      <link>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1919220#M412</link>
      <description>&lt;P&gt;Hello Assaf,&lt;/P&gt;
&lt;P&gt;I confirm this bug in the SEC v8, that is fixed in the upcoming v9 (stay tuned this week). The unused key slots must be configured in the CMPA - v9 takes the care, while in the v8 you have to do it manually in the RoTK_USAGE register:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="liborukropec_0-1722242238257.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/290695i657C27D3EABBBF50/image-size/medium?v=v2&amp;amp;px=400" role="button" title="liborukropec_0-1722242238257.png" alt="liborukropec_0-1722242238257.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to wait for SEC v9.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using just 1 key seems like corner case and I'm interested about the use case; recommended is to use all 4 slots to be able do key revocation in the future.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Libor&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 08:41:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/1-ROT-IMG-key-for-MCXN546-Not-Working/m-p/1919220#M412</guid>
      <dc:creator>liborukropec</dc:creator>
      <dc:date>2024-07-29T08:41:49Z</dc:date>
    </item>
  </channel>
</rss>

