<?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>How to choose ACCESS_FLASH_PAGE_COUNT and DSM_FLASH_PAGE_COUNT?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50556/how-to-choose-access_flash_page_count-and-dsm_flash_page_count</link><description>These two options in nrf_mesh_config_app are arbitrary for me if I don&amp;#39;t understand how they should be sized. 
 From the documentation of the MESH SDK 3.2.0: 
 ACCESS_FLASH_PAGE_COUNT: The number of pages of flash storage reserved for the access layer</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Aug 2019 08:01:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50556/how-to-choose-access_flash_page_count-and-dsm_flash_page_count" /><item><title>RE: How to choose ACCESS_FLASH_PAGE_COUNT and DSM_FLASH_PAGE_COUNT?</title><link>https://devzone.nordicsemi.com/thread/202325?ContentTypeID=1</link><pubDate>Mon, 05 Aug 2019 08:01:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:39f49736-e5ae-4fb9-a9f7-99397cefe38c</guid><dc:creator>rmarques</dc:creator><description>&lt;p&gt;Then we just set the number of pages to the minimum, let&amp;#39;s say 1 each, and keep erasing and reprogramming the chip with a higher number if needed? I was expecting this to be predictable, given the setup of the resources we are requiring, for example number of non virtual addresses and the number of models/elements of the mesh.&lt;/p&gt;
&lt;p&gt;If I erase the chip before reprogramming I can choose any number of pages and it boots fine, the issue only happens if I reprogram with a different number of pages and don&amp;#39;t erase the chip previously.&lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;
&lt;p&gt;R&amp;uacute;ben&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to choose ACCESS_FLASH_PAGE_COUNT and DSM_FLASH_PAGE_COUNT?</title><link>https://devzone.nordicsemi.com/thread/202196?ContentTypeID=1</link><pubDate>Fri, 02 Aug 2019 14:24:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d410f76-6757-4895-8660-8165404993bb</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
[quote user=""]But is there a formula or rule of thumb to how much memory or how many pages the Access Layer and the Device State Manager needs?[/quote]
&lt;p&gt;&lt;span&gt;There is no single correct answer to this question.&amp;nbsp;It is entirely application dependent and this will be different for all customers.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Not sure about the Mesh assert. Did you erase the chip before reprogramming?&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>