<?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: otpmk in OEM_OPEN state in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133619#M239269</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;You are correct, the last contradicts, I thought you were discussing SRK keys for signing secure boot.&lt;/P&gt;
&lt;P&gt;OTPMK is a key unique to every chip, on SECO devices, such as the i.MX 8/8X family, a unique OTP Master Key (OTPMK) is used to encrypt and&amp;nbsp;wrap the DEK in a blob.&amp;nbsp;NXP provides the available U-Boot port with the capability of using these private keys through SECO firmware.&lt;/P&gt;
&lt;P&gt;It doesn't change between an open and a closed device.&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 01:33:17 GMT</pubDate>
    <dc:creator>JosephAtNXP</dc:creator>
    <dc:date>2025-07-15T01:33:17Z</dc:date>
    <item>
      <title>otpmk in OEM_OPEN state</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2131906#M239171</link>
      <description>&lt;P&gt;I am looking through the security manual for the iMX8QM and I am struggling to understand how the OTPMK changes between the OEM_OPEN and the OEM_CLOSED state.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Is the OTPMK used when the chip is in the OEM_OPEN state unique for each chip (i.e two i.MX8QM will have different OTPMK even in the OEM_OPEN state)?&lt;/P&gt;&lt;P&gt;- Is there a way from linux or u-boot to check what the the security state is? (Trusted, Secure, Non-Secure, etc.)&lt;/P&gt;&lt;P&gt;- If we needed to move to OEM_CLOSED, what does that processes look like for a linux/yocto based system?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Allan&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 18:04:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2131906#M239171</guid>
      <dc:creator>gilmoreat</dc:creator>
      <dc:date>2025-07-10T18:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: otpmk in OEM_OPEN state</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2131939#M239173</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thank you for your interest in NXP Semiconductor products,&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/nxp-imx/uboot-imx/blob/7376547b9e424b2d0f42dfe96394168c781ca297/doc/imx/ahab/guides/mx8_mx8x_secure_boot.txt#L266" target="_self"&gt;This is the guide&lt;/A&gt; for secure boot and it also contains the U-boot command that returns the closed or open state depending on the SoC.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 19:38:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2131939#M239173</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-07-10T19:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: otpmk in OEM_OPEN state</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2131953#M239175</link>
      <description>Hi Joseph,&lt;BR /&gt;&lt;BR /&gt;Thanks for the quick reply! Do you know if the OTPMK using in the OEM_OPEN state is unique per chip? We are using the iMX8QM and we would like to make sure that two of our device do not share the same key.</description>
      <pubDate>Thu, 10 Jul 2025 20:03:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2131953#M239175</guid>
      <dc:creator>gilmoreat</dc:creator>
      <dc:date>2025-07-10T20:03:01Z</dc:date>
    </item>
    <item>
      <title>Re: otpmk in OEM_OPEN state</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133525#M239259</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Keys are always 0 in fresh devices, you can burn unique keys to each one of your chips.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 20:12:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133525#M239259</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-07-14T20:12:03Z</dc:date>
    </item>
    <item>
      <title>Re: otpmk in OEM_OPEN state</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133558#M239261</link>
      <description>Hi Joseph,&lt;BR /&gt;&lt;BR /&gt;This seems to conflict directly with this previous post: &lt;A href="https://community.nxp.com/t5/i-MX-Processors/OTPMK-on-iMX8QM/m-p/1346985" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors/OTPMK-on-iMX8QM/m-p/1346985&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;After digging through the MRM and the SRM for the i.MX8QM, I don't see any method to set the OTPMK.&lt;BR /&gt;&lt;BR /&gt;Back to my original question, Does the OTPMK change between OEM_OPEN and OEM_CLOSED state and is the key unique for each chip when in the OEM_OPEN state?</description>
      <pubDate>Mon, 14 Jul 2025 21:59:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133558#M239261</guid>
      <dc:creator>gilmoreat</dc:creator>
      <dc:date>2025-07-14T21:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: otpmk in OEM_OPEN state</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133619#M239269</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;You are correct, the last contradicts, I thought you were discussing SRK keys for signing secure boot.&lt;/P&gt;
&lt;P&gt;OTPMK is a key unique to every chip, on SECO devices, such as the i.MX 8/8X family, a unique OTP Master Key (OTPMK) is used to encrypt and&amp;nbsp;wrap the DEK in a blob.&amp;nbsp;NXP provides the available U-Boot port with the capability of using these private keys through SECO firmware.&lt;/P&gt;
&lt;P&gt;It doesn't change between an open and a closed device.&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 01:33:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/otpmk-in-OEM-OPEN-state/m-p/2133619#M239269</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-07-15T01:33:17Z</dc:date>
    </item>
  </channel>
</rss>

