<?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: EEPROM emulator on MPC57xx in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1645993#M23529</link>
    <description>&lt;P&gt;I've read this document and the problem persists, I am accessing the same record whatever "dataID" value I am passing to the read/write functions. what would be the reason for that doesn't the "dataID" variable represent the record number ?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 07 May 2023 15:45:28 GMT</pubDate>
    <dc:creator>Osabry</dc:creator>
    <dc:date>2023-05-07T15:45:28Z</dc:date>
    <item>
      <title>EEPROM emulator on MPC57xx</title>
      <link>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1642563#M23467</link>
      <description>&lt;P&gt;I am trying to use the EEPROM driver and I couldn't fully understand what does the "dataID" variable represents, I am using it to access different records but it keeps accessing the same record regardless the "dataID" value I pass to the read/write/erase functions !! I would like to ask also if I could select the partition I am accessing ?&lt;/P&gt;</description>
      <pubDate>Sun, 30 Apr 2023 10:31:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1642563#M23467</guid>
      <dc:creator>Osabry</dc:creator>
      <dc:date>2023-04-30T10:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: EEPROM emulator on MPC57xx</title>
      <link>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1643581#M23501</link>
      <description>&lt;P&gt;I could recommend to see following aponote what will help you to understand how EEPROM emulation works:&lt;BR /&gt;&lt;A href="https://www.nxp.com/docs/en/application-note/AN4868.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/application-note/AN4868.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;EEPROM emulation driver basically spreads programmed data content over the whole data flash in order to prevent wearing out of particular flash portions. Otherwise endurance limit (number of program/erase cycles) would be early achieved and data content could be damaged. So you dont choose specific place where data are being stored, but the driver takes care of it.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2023 11:30:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1643581#M23501</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-05-03T11:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: EEPROM emulator on MPC57xx</title>
      <link>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1645993#M23529</link>
      <description>&lt;P&gt;I've read this document and the problem persists, I am accessing the same record whatever "dataID" value I am passing to the read/write functions. what would be the reason for that doesn't the "dataID" variable represent the record number ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 07 May 2023 15:45:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1645993#M23529</guid>
      <dc:creator>Osabry</dc:creator>
      <dc:date>2023-05-07T15:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: EEPROM emulator on MPC57xx</title>
      <link>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1658748#M23714</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52613"&gt;@davidtosenovjan&lt;/a&gt;&amp;nbsp;I have further debugged it and I found that any record access returns a status of invalid (0xFFFF0000) which I couldn't understand is there some sort of initialization for the records I am missing, however I am using an example. the invalid status is returned through the "record" struct variable "dataStatus" highlighted in the attached image.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Osabry_0-1685286316480.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/225105i928FA4AB6B754ED7/image-size/large?v=v2&amp;amp;px=999" role="button" title="Osabry_0-1685286316480.png" alt="Osabry_0-1685286316480.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 28 May 2023 15:05:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/EEPROM-emulator-on-MPC57xx/m-p/1658748#M23714</guid>
      <dc:creator>Osabry</dc:creator>
      <dc:date>2023-05-28T15:05:32Z</dc:date>
    </item>
  </channel>
</rss>

