<?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>S32KのトピックS32K148 flash partitioning without deleting data flash</title>
    <link>https://community.nxp.com/t5/S32K/S32K148-flash-partitioning-without-deleting-data-flash/m-p/1254300#M10380</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I face a problem that data flash (part of FlexNVM) is deleted during flash partitioning command 0x80 (PGMPART). I would like to flash a code to the code flash and also data to the data flash during production flashing via JTAG interface (e.g. J-link from Segger). But when the code is executed first time, it recognize that flash is not partitioned and executes flash partitioning command 0x80 (PGMPART) which erases complete FlexNVM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Please can somebody suggest an approach to flashing data flash and flash partitioning?&lt;/LI&gt;&lt;LI&gt;Is there a way to do the flash partitioning during flashing via JTAG (without executing code calling partitioning command PGMPART)? For example by direct flashing value to SIM-&amp;gt;FCFG1. I want to keep the production flashing process simple and fast.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried also the opposite approach. I have flashed code doing flash partitioning, started this code and then flashed the data to data flash. It works, but only when I erase only sectors in the range 0x10000000 - 0x1005FFFF. When I erase more, the partitioning is corrupted and must be repeated on the next code execution. It makes sense to me. Sectors from 0x10060000 are probably used for EEE backup (64KB). I would like to ask whether this approach is save.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;What else can corrupt the partitioning?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any hints,&lt;/P&gt;&lt;P&gt;Libor Waszniowski&lt;/P&gt;</description>
    <pubDate>Tue, 30 Mar 2021 14:00:37 GMT</pubDate>
    <dc:creator>lwaszniowski</dc:creator>
    <dc:date>2021-03-30T14:00:37Z</dc:date>
    <item>
      <title>S32K148 flash partitioning without deleting data flash</title>
      <link>https://community.nxp.com/t5/S32K/S32K148-flash-partitioning-without-deleting-data-flash/m-p/1254300#M10380</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I face a problem that data flash (part of FlexNVM) is deleted during flash partitioning command 0x80 (PGMPART). I would like to flash a code to the code flash and also data to the data flash during production flashing via JTAG interface (e.g. J-link from Segger). But when the code is executed first time, it recognize that flash is not partitioned and executes flash partitioning command 0x80 (PGMPART) which erases complete FlexNVM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Please can somebody suggest an approach to flashing data flash and flash partitioning?&lt;/LI&gt;&lt;LI&gt;Is there a way to do the flash partitioning during flashing via JTAG (without executing code calling partitioning command PGMPART)? For example by direct flashing value to SIM-&amp;gt;FCFG1. I want to keep the production flashing process simple and fast.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried also the opposite approach. I have flashed code doing flash partitioning, started this code and then flashed the data to data flash. It works, but only when I erase only sectors in the range 0x10000000 - 0x1005FFFF. When I erase more, the partitioning is corrupted and must be repeated on the next code execution. It makes sense to me. Sectors from 0x10060000 are probably used for EEE backup (64KB). I would like to ask whether this approach is save.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;What else can corrupt the partitioning?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any hints,&lt;/P&gt;&lt;P&gt;Libor Waszniowski&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 14:00:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K148-flash-partitioning-without-deleting-data-flash/m-p/1254300#M10380</guid>
      <dc:creator>lwaszniowski</dc:creator>
      <dc:date>2021-03-30T14:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: S32K148 flash partitioning without deleting data flash</title>
      <link>https://community.nxp.com/t5/S32K/S32K148-flash-partitioning-without-deleting-data-flash/m-p/1255043#M10403</link>
      <description>&lt;P&gt;Hi, I would share screenshot from AN11983.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="davidtosenovjan_0-1617203882428.png" style="width: 636px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/141076i2547E05EEA029F8C/image-dimensions/636x294?v=v2" width="636" height="294" role="button" title="davidtosenovjan_0-1617203882428.png" alt="davidtosenovjan_0-1617203882428.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Flash partitioning itself needs to be executed from SRAM. Then you may store data to flash.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 15:22:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K148-flash-partitioning-without-deleting-data-flash/m-p/1255043#M10403</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2021-03-31T15:22:00Z</dc:date>
    </item>
  </channel>
</rss>

