<?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: UTEST memory area for factory data in S32K</title>
    <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1893310#M36875</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;No. You cant rewrite data in OTP as customer.&lt;/P&gt;
&lt;P&gt;The UTEST flash is made OTP via burning out TEST mode fuse in NXP factory.&lt;/P&gt;
&lt;P&gt;There is no reverse possibility. It is permanent.&lt;/P&gt;
&lt;P&gt;You simply tune the OTP in your development, which will maybe require several chips to be used for that purpose. But for factory production you will go with only one config as majority of customers.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jun 2024 04:47:38 GMT</pubDate>
    <dc:creator>petervlna</dc:creator>
    <dc:date>2024-06-25T04:47:38Z</dc:date>
    <item>
      <title>UTEST memory area for factory data</title>
      <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1887240#M36572</link>
      <description>&lt;P&gt;Hello there,&lt;/P&gt;&lt;P&gt;I am looking for a memory location on the S32K324 to store our factory data like the user hardware revision, softwar version, bootloader version and so on and I stumbled uppon the dcf_client_sdid0-15 entries in the UTEST Memory area and the DCF Clients sheet which apparently are made for that. But I am a bit confused about this Memory since the processor uses this area for some setups during boot as far as I did understand it. So I was wondering if this is even the right place to store my factory data?&lt;/P&gt;&lt;P&gt;regards,&lt;BR /&gt;Felix.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 18:24:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1887240#M36572</guid>
      <dc:creator>FelixR</dc:creator>
      <dc:date>2024-06-13T18:24:04Z</dc:date>
    </item>
    <item>
      <title>Re: UTEST memory area for factory data</title>
      <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1887519#M36588</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You can store your factory data in the following location:&lt;/P&gt;
&lt;P&gt;The first 2 marked locations are made for that purpose.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="petervlna_0-1718341041871.png" style="width: 694px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/284143i067E4CB66187731C/image-dimensions/694x274?v=v2" width="694" height="274" role="button" title="petervlna_0-1718341041871.png" alt="petervlna_0-1718341041871.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;In case you require more space you can also use DCF records space, but you must pay attention here to not overwrite DCFs.&lt;BR /&gt;In such case it is best to add it after stop record which is represented here by 0xFFFF_FFFF. I would do this only once DCFs are finalized and no more will be added. Also I will leave a enough space in case some will be added in future.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jun 2024 05:00:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1887519#M36588</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2024-06-14T05:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: UTEST memory area for factory data</title>
      <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1892622#M36848</link>
      <description>Ah I see. One last quick question. I read in the reference manual that the UTEST area is OTP but it is a bit ambiguous "when" it is OTP. The reference manual says that "the UTest NVM sector is an OTP sector (assuming Test mode disable seal is written)". Does that mean that until I write the Test mode disable seal I can write multiple times inside my UTest Area, probably over my planned factory data just in case I write it wrongly?</description>
      <pubDate>Mon, 24 Jun 2024 06:21:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1892622#M36848</guid>
      <dc:creator>FelixR</dc:creator>
      <dc:date>2024-06-24T06:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: UTEST memory area for factory data</title>
      <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1893310#M36875</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;No. You cant rewrite data in OTP as customer.&lt;/P&gt;
&lt;P&gt;The UTEST flash is made OTP via burning out TEST mode fuse in NXP factory.&lt;/P&gt;
&lt;P&gt;There is no reverse possibility. It is permanent.&lt;/P&gt;
&lt;P&gt;You simply tune the OTP in your development, which will maybe require several chips to be used for that purpose. But for factory production you will go with only one config as majority of customers.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2024 04:47:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/1893310#M36875</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2024-06-25T04:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: UTEST memory area for factory data</title>
      <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/2251346#M54925</link>
      <description>&lt;P&gt;hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/203228"&gt;@FelixR&lt;/a&gt;&amp;nbsp; &amp;nbsp;did u get the solution ?&amp;nbsp; If yes please do share the solution&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 18:15:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/2251346#M54925</guid>
      <dc:creator>Sanjana_k</dc:creator>
      <dc:date>2025-11-28T18:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: UTEST memory area for factory data</title>
      <link>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/2252228#M54955</link>
      <description>Hey &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252149"&gt;@Sanjana_k&lt;/a&gt;, in the end I started using a slice of the DCFrecord area for my OTP data. As stated by &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/13836"&gt;@petervlna&lt;/a&gt; in the solution, I could have used the two application areas inside the OTP data but... that's not feasable since they are to small.&lt;BR /&gt;&lt;BR /&gt;I just ensure during build that the Data I plan to write into this is not accidentally formated like DCF start Record (See the reference Manual Table 223) so I don't corrupt any processor functionality.</description>
      <pubDate>Mon, 01 Dec 2025 10:29:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/UTEST-memory-area-for-factory-data/m-p/2252228#M54955</guid>
      <dc:creator>FelixR</dc:creator>
      <dc:date>2025-12-01T10:29:35Z</dc:date>
    </item>
  </channel>
</rss>

