<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NVS Terminology</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/83996/nvs-terminology</link><description>What does ATE mean ? 
 
 As in &amp;quot;...NVS in-flash image will stay compatible unless the physical ATE size changes&amp;quot;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Jan 2022 10:37:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/83996/nvs-terminology" /><item><title>RE: NVS Terminology</title><link>https://devzone.nordicsemi.com/thread/349489?ContentTypeID=1</link><pubDate>Tue, 25 Jan 2022 10:37:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c669f57-d482-44e3-b16c-1c6323fb7763</guid><dc:creator>Soupdragon</dc:creator><description>&lt;p&gt;Yes, another perfect answer. Many thanks,&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;John&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NVS Terminology</title><link>https://devzone.nordicsemi.com/thread/349473?ContentTypeID=1</link><pubDate>Tue, 25 Jan 2022 09:46:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26f06e25-4293-4162-92b1-1e298b1441c3</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi John,&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Correct me if I am wrong, but from the text excerpt&amp;nbsp;&lt;span&gt;&amp;quot;...&lt;em&gt;NVS in-flash image will stay compatible unless the physical ATE size changes&lt;/em&gt;&amp;quot;, my guess is that you&amp;#39;re reading Zephyr documentation about&amp;nbsp;&lt;a href="https://docs.zephyrproject.org/latest/reference/storage/nvs/nvs.html"&gt;Non-Volatile Storage&lt;/a&gt;. In this documentation the ATE is an abriviation for &amp;quot;&lt;em&gt;Allocation Table Entry&lt;/em&gt;&amp;quot;. In NVS, the flash area is divided into sectors, where some of the sectors are currently in use as storage, while others are ready to be used (empty). &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;From what I can understand, the ATE holds the information about what areas of the NVS that are ready for use or not.&amp;nbsp;&lt;/span&gt;&lt;span&gt;In the&amp;nbsp;&lt;em&gt;API Reference&lt;/em&gt; section in the linked document, the parameter &amp;quot;Allocation table entry write address&amp;quot; is explained as &amp;quot;Addresses are stored as uint32_t: high 2 bytes correspond to the sector, low 2 bytes are the offset in the sector&amp;quot;.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I hope this answers your question!&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Andreas&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>