<?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 EEPROM PROBLEM IN JN5168 in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/EEPROM-PROBLEM-IN-JN5168/m-p/755869#M4427</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/mario_castaneda"&gt;mario_castaneda&lt;/A&gt;‌,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing problem in PDM EEPROM.&lt;/P&gt;&lt;P&gt;when i tried to load data in EEPROM its works correctly.&amp;nbsp;&lt;/P&gt;&lt;P&gt;but after a reboot while reading "PDM_eReadDataFromRecord" this API,&lt;/P&gt;&lt;P&gt;it&amp;nbsp;shows "&amp;nbsp;PDM_E_STATUS_INVLD_PARAM".&lt;/P&gt;&lt;P&gt;how to overcome this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dheeraj Sawant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Jan 2018 10:50:14 GMT</pubDate>
    <dc:creator>dheerajsawant</dc:creator>
    <dc:date>2018-01-02T10:50:14Z</dc:date>
    <item>
      <title>EEPROM PROBLEM IN JN5168</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/EEPROM-PROBLEM-IN-JN5168/m-p/755869#M4427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/mario_castaneda"&gt;mario_castaneda&lt;/A&gt;‌,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing problem in PDM EEPROM.&lt;/P&gt;&lt;P&gt;when i tried to load data in EEPROM its works correctly.&amp;nbsp;&lt;/P&gt;&lt;P&gt;but after a reboot while reading "PDM_eReadDataFromRecord" this API,&lt;/P&gt;&lt;P&gt;it&amp;nbsp;shows "&amp;nbsp;PDM_E_STATUS_INVLD_PARAM".&lt;/P&gt;&lt;P&gt;how to overcome this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dheeraj Sawant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2018 10:50:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/EEPROM-PROBLEM-IN-JN5168/m-p/755869#M4427</guid>
      <dc:creator>dheerajsawant</dc:creator>
      <dc:date>2018-01-02T10:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: EEPROM PROBLEM IN JN5168</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/EEPROM-PROBLEM-IN-JN5168/m-p/755870#M4428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dheeraj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Application data records in EEPROM can be read by the application using the function PDM_eReadDataFromRecord(). The record to be read is specified using its 16-bit identifier and a data buffer in RAM must also be specified in which the read data will be stored.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the call to PDM_eReadDataFromRecord() indicates that the record has not been found, the application should also call PDM_eDeleteAllData() because another application may have been running that does not use the same record ID but has written inconsistent ZigBee PRO records to the PDM module&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jan 2018 02:12:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/EEPROM-PROBLEM-IN-JN5168/m-p/755870#M4428</guid>
      <dc:creator>mario_castaneda</dc:creator>
      <dc:date>2018-01-25T02:12:40Z</dc:date>
    </item>
  </channel>
</rss>

