<?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>RAM state after reset by WatchDog</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/59558/ram-state-after-reset-by-watchdog</link><description>Hello Nordic team, 
 
 I&amp;#39;m looking into solution to pass data to my application after a Reset using the RAM of my nrf52840. 
 Looking at the documentation, this picture troubles me: 
 
 I&amp;#39;m interested into the RAM state after a WatchDog reset, and it</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 17 Apr 2020 12:15:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/59558/ram-state-after-reset-by-watchdog" /><item><title>RE: RAM state after reset by WatchDog</title><link>https://devzone.nordicsemi.com/thread/245231?ContentTypeID=1</link><pubDate>Fri, 17 Apr 2020 12:15:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c4ee6972-75ab-4a69-8ebb-1e237e185dd6</guid><dc:creator>Heidi</dc:creator><description>&lt;p&gt;Hi, you could write to FLASH instead.&lt;/p&gt;
&lt;p&gt;I would recommend using the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_fds.html"&gt;Flash Data Storage library&lt;/a&gt; in the SDK (instead of the Flash Storage library) if you&amp;#39;re updating after every boot. Flash has an endurance of 10000 write/erase cycles. With FDS you can fill up a whole page before having to erase, so you&amp;nbsp;get basic wear leveling.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There is also an&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/fds_example.html"&gt;FDS example&lt;/a&gt;&amp;nbsp;available in the SDK.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Heidi&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RAM state after reset by WatchDog</title><link>https://devzone.nordicsemi.com/thread/244615?ContentTypeID=1</link><pubDate>Wed, 15 Apr 2020 08:23:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0b768697-3fd4-477e-95d1-b06ef403d358</guid><dc:creator>AKYR</dc:creator><description>&lt;p&gt;Hey Heidi,&lt;/p&gt;
&lt;p&gt;Thanks for this, I didn&amp;#39;t saw you answered !&lt;/p&gt;
&lt;p&gt;So for the product we are designing the most probable cause of a reboot is the Watchdog, but we would like to save a few data for the next boot...&lt;/p&gt;
&lt;p&gt;This is the only solution I see, RAM struct in .non_init section with a CRC calculation to ensure data is not corrupted, can you think of any other way to pass data to next boot after Watchdog reboot ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks in advance !&lt;/p&gt;
&lt;p&gt;Alo&amp;iuml;s KYROU.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RAM state after reset by WatchDog</title><link>https://devzone.nordicsemi.com/thread/242547?ContentTypeID=1</link><pubDate>Mon, 30 Mar 2020 19:13:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:514caafb-72d3-4b8a-bb61-1561ac65aa60</guid><dc:creator>Heidi</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;It looks like you got lucky. The documentation states that the RAM&amp;nbsp;&lt;em&gt;may be&lt;/em&gt; corrupted, but that doesn&amp;#39;t mean it will happen every time. So the data is not reliable after a WD reset.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Heidi&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>