<?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 lifecycle transition in s32k3 in S32K</title>
    <link>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1812713#M31909</link>
    <description>&lt;P&gt;I know that the transition from CUST_DEL to OEM_PROD or IN_FIELD is only possible if the application debug key / password (ADKP) is provisioned as the specification.&lt;/P&gt;&lt;P&gt;the current lifecycle is OEM_PROD debug key / password (ADKP) is provisioned.&lt;/P&gt;&lt;P&gt;Is it possible to change&amp;nbsp;OEM_PROD to&amp;nbsp;IN_FIELD if&amp;nbsp;the application debug key / password (ADKP) is provisioned?&lt;/P&gt;</description>
    <pubDate>Wed, 21 Feb 2024 09:58:10 GMT</pubDate>
    <dc:creator>HyunungPark1</dc:creator>
    <dc:date>2024-02-21T09:58:10Z</dc:date>
    <item>
      <title>lifecycle transition in s32k3</title>
      <link>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1812713#M31909</link>
      <description>&lt;P&gt;I know that the transition from CUST_DEL to OEM_PROD or IN_FIELD is only possible if the application debug key / password (ADKP) is provisioned as the specification.&lt;/P&gt;&lt;P&gt;the current lifecycle is OEM_PROD debug key / password (ADKP) is provisioned.&lt;/P&gt;&lt;P&gt;Is it possible to change&amp;nbsp;OEM_PROD to&amp;nbsp;IN_FIELD if&amp;nbsp;the application debug key / password (ADKP) is provisioned?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 09:58:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1812713#M31909</guid>
      <dc:creator>HyunungPark1</dc:creator>
      <dc:date>2024-02-21T09:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: lifecycle transition in s32k3</title>
      <link>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1813029#M31930</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222596"&gt;@HyunungPark1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In section&amp;nbsp;32.5.2 (Address LC configuration word) of the&amp;nbsp;S32K3xx Reference Manual, Rev. 8 states that "To advance LC, you must program a valid 32-bit wide value at an address given in IVT at an address offset of 24h."&lt;/P&gt;&lt;P&gt;Also, "The chip provides an LC mechanism for an irreversible progression of restrictions to access the chip's security-related content. You cannot reverse the chip's LC, so it is only possible to mature the chip. SBAF advances the chip through the LC:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;CUST_DEL --&amp;gt; OEM_PROD or IN_FIELD&lt;/LI&gt;&lt;LI&gt;OEM_PROD --&amp;gt; IN_FIELD"&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;B.R.&lt;/P&gt;&lt;P&gt;VaneB&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 18:10:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1813029#M31930</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2024-02-21T18:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: lifecycle transition in s32k3</title>
      <link>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1819928#M32378</link>
      <description>&lt;P&gt;This issue is resolved&lt;/P&gt;</description>
      <pubDate>Sun, 03 Mar 2024 08:53:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/lifecycle-transition-in-s32k3/m-p/1819928#M32378</guid>
      <dc:creator>HyunungPark1</dc:creator>
      <dc:date>2024-03-03T08:53:02Z</dc:date>
    </item>
  </channel>
</rss>

