<?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のトピックRe: S32k3xx : Query on Embedded Flash Memory Blocks</title>
    <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858328#M34888</link>
    <description>&lt;P&gt;According configuration lower data granularity is 4 bytes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;EEPROM emulation drivers that are part of RTD driver package (FEE driver):&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD" target="_blank"&gt;https://www.nxp.com/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;An example for this is called Fee_Example_S32K3..&lt;/P&gt;</description>
    <pubDate>Thu, 02 May 2024 08:51:14 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2024-05-02T08:51:14Z</dc:date>
    <item>
      <title>S32k3xx : Query on Embedded Flash Memory Blocks</title>
      <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1854466#M34638</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I wanted to inquire about the inclusion of separate &lt;STRONG&gt;Data Flash Memory&lt;/STRONG&gt; alongside &lt;STRONG&gt;Code Flash Memory&lt;/STRONG&gt; in the S32K3xx microcontrollers.&lt;/P&gt;&lt;P&gt;Could you kindly provide some insights into why separate Data Flash memory is required in the design choice?&lt;/P&gt;&lt;P&gt;Thank you for your time and assistance.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2024 07:30:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1854466#M34638</guid>
      <dc:creator>varunbharti</dc:creator>
      <dc:date>2024-04-25T07:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: S32k3xx : Query on Embedded Flash Memory Blocks</title>
      <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1855654#M34707</link>
      <description>&lt;P&gt;The most typical way for using of DFLASH is EEPROM emulation. DFlash use always smallest block with highest endurance, sometimes reaction to ECC failure is handled differently than with code flash. That’s why it is well suited for running EEPROM emulation driver above this memory space. Otherwise it just may be used for storing non-volatile data (in comparison to code flash, it has higher endurance, but lower data retention).&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 11:26:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1855654#M34707</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2024-04-26T11:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: S32k3xx : Query on Embedded Flash Memory Blocks</title>
      <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1855880#M34717</link>
      <description>Thankyou for your quick response</description>
      <pubDate>Fri, 26 Apr 2024 17:48:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1855880#M34717</guid>
      <dc:creator>varunbharti</dc:creator>
      <dc:date>2024-04-26T17:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: S32k3xx : Query on Embedded Flash Memory Blocks</title>
      <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858178#M34872</link>
      <description>&lt;P&gt;Hi&amp;nbsp; &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52613"&gt;@davidtosenovjan&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thank you again for your response,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please share a sample code on how to use DFLASH to emulate EEPROM?&lt;/P&gt;&lt;P&gt;Can we do byte-wise write and erase in DFLASH?&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 05:30:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858178#M34872</guid>
      <dc:creator>varunbharti</dc:creator>
      <dc:date>2024-05-02T05:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: S32k3xx : Query on Embedded Flash Memory Blocks</title>
      <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858328#M34888</link>
      <description>&lt;P&gt;According configuration lower data granularity is 4 bytes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;EEPROM emulation drivers that are part of RTD driver package (FEE driver):&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD" target="_blank"&gt;https://www.nxp.com/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;An example for this is called Fee_Example_S32K3..&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 08:51:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858328#M34888</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2024-05-02T08:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: S32k3xx : Query on Embedded Flash Memory Blocks</title>
      <link>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858558#M34911</link>
      <description>Thankyou!!!</description>
      <pubDate>Thu, 02 May 2024 18:33:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k3xx-Query-on-Embedded-Flash-Memory-Blocks/m-p/1858558#M34911</guid>
      <dc:creator>varunbharti</dc:creator>
      <dc:date>2024-05-02T18:33:39Z</dc:date>
    </item>
  </channel>
</rss>

