<?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: Get temp values from NHS3100 in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675397#M27079</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Shailav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aside: this looks like code from SDK v9.1. On nxp.com you can now download SDK v10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can increase the number of the storage samples by switching to a release build - if you are able to store about&amp;nbsp;4000 samples it looks like your firmware image is very big, which indicates you are using a debug build.&lt;/P&gt;&lt;P&gt;As &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/IvanRuiz"&gt;IvanRuiz&lt;/A&gt; already pointed out: using the storage module will make use of both EEPROM and FLASH. A call to&amp;nbsp;&lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold;"&gt;Storage_Write&lt;/STRONG&gt; will write too EEPROM, but when that is full (and only then), all data is dumped to FLASH, making room for more samples. A smaller firmware image will thus allow you to write more samples in&amp;nbsp;non-volatile memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that you can control which&amp;nbsp;amount of EEPROM the storage module is allowed to use for storing data by adjusting or defining&amp;nbsp;&lt;STRONG&gt;STORAGE_EEPROM_FIRST_ROW&lt;/STRONG&gt; and/or&amp;nbsp;&lt;STRONG&gt;STORAGE_EEPROM_LAST_ROW&lt;/STRONG&gt;. See &lt;EM&gt;storage_dft.h&lt;/EM&gt; or the documentation at &lt;EM&gt;docs/FirmwareDevelopmentDocumentation/index.html.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to delete old samples - while still using the storage module - you can do so by defining &lt;STRONG&gt;STORAGE_COMPRESS_CB&lt;/STRONG&gt; and implementing&amp;nbsp;a lossy compression algorithm. This callback is called each time EEPROM is full, just before moving data to FLASH. The current &lt;EM&gt;tlogger demo&lt;/EM&gt; is using a lossless compression algorithm to demonstrate the technique, but you can differentiate by&amp;nbsp;making your own 'compression' - deletion can be viewed as a heavy kind of lossy compression :-)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of course, you cam also just stop using the storage module and implement your own logic on top of the EEPROM driver that does precisely what you want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;BR /&gt;Dries.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Jun 2017 19:23:09 GMT</pubDate>
    <dc:creator>driesmoors</dc:creator>
    <dc:date>2017-06-01T19:23:09Z</dc:date>
    <item>
      <title>Get temp values from NHS3100</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675395#M27077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am using NHS3100 and loading the code app_demo_dp_tlogger. I am using lpc xpresso ide for that. Now the maximum capacity is 4000 samples which are stored in flash of NHS3100. So I dont get the data once the flash gets full. How can I delete the old samples so that I can get some memory for new samples?&lt;/P&gt;&lt;P&gt;I am attaching my code with this.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Shailav&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337842"&gt;app_demo_dp_tlogger.rar&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 May 2017 11:34:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675395#M27077</guid>
      <dc:creator>shailavsurve</dc:creator>
      <dc:date>2017-05-10T11:34:11Z</dc:date>
    </item>
    <item>
      <title>Re: Get temp values from NHS3100</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675396#M27078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Shailav Surve,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can clear EEPROM by moving the data into FLASH by making use of &lt;STRONG&gt;int Storage_Write(STORAGE_TYPE * samples, int n)&lt;/STRONG&gt; function in storage.c file. When that is done, the EEPROM is fully empty again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Ivan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 May 2017 23:37:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675396#M27078</guid>
      <dc:creator>IvanRuiz</dc:creator>
      <dc:date>2017-05-18T23:37:50Z</dc:date>
    </item>
    <item>
      <title>Re: Get temp values from NHS3100</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675397#M27079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Shailav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aside: this looks like code from SDK v9.1. On nxp.com you can now download SDK v10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can increase the number of the storage samples by switching to a release build - if you are able to store about&amp;nbsp;4000 samples it looks like your firmware image is very big, which indicates you are using a debug build.&lt;/P&gt;&lt;P&gt;As &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/IvanRuiz"&gt;IvanRuiz&lt;/A&gt; already pointed out: using the storage module will make use of both EEPROM and FLASH. A call to&amp;nbsp;&lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold;"&gt;Storage_Write&lt;/STRONG&gt; will write too EEPROM, but when that is full (and only then), all data is dumped to FLASH, making room for more samples. A smaller firmware image will thus allow you to write more samples in&amp;nbsp;non-volatile memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that you can control which&amp;nbsp;amount of EEPROM the storage module is allowed to use for storing data by adjusting or defining&amp;nbsp;&lt;STRONG&gt;STORAGE_EEPROM_FIRST_ROW&lt;/STRONG&gt; and/or&amp;nbsp;&lt;STRONG&gt;STORAGE_EEPROM_LAST_ROW&lt;/STRONG&gt;. See &lt;EM&gt;storage_dft.h&lt;/EM&gt; or the documentation at &lt;EM&gt;docs/FirmwareDevelopmentDocumentation/index.html.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to delete old samples - while still using the storage module - you can do so by defining &lt;STRONG&gt;STORAGE_COMPRESS_CB&lt;/STRONG&gt; and implementing&amp;nbsp;a lossy compression algorithm. This callback is called each time EEPROM is full, just before moving data to FLASH. The current &lt;EM&gt;tlogger demo&lt;/EM&gt; is using a lossless compression algorithm to demonstrate the technique, but you can differentiate by&amp;nbsp;making your own 'compression' - deletion can be viewed as a heavy kind of lossy compression :-)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of course, you cam also just stop using the storage module and implement your own logic on top of the EEPROM driver that does precisely what you want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;BR /&gt;Dries.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Jun 2017 19:23:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Get-temp-values-from-NHS3100/m-p/675397#M27079</guid>
      <dc:creator>driesmoors</dc:creator>
      <dc:date>2017-06-01T19:23:09Z</dc:date>
    </item>
  </channel>
</rss>

