<?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>Flash crash</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/16372/flash-crash</link><description>I used nRF51822 IC and SDK11 with softdevice S130. I found a problem that our product cannot work. I dumped the hex code of 2sets from 0x00000000 to 0x0003ffff. One can work, the other cannot. The differences are between address of 0x0003b808 and 0x0003b937</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Oct 2016 14:04:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/16372/flash-crash" /><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62677?ContentTypeID=1</link><pubDate>Wed, 19 Oct 2016 14:04:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15189950-e865-4477-8afe-da2287de1901</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@lerrywu: I cant ses that you are calling &lt;code&gt;ble_stack_init()&lt;/code&gt; before calling  &lt;code&gt;gap_params_init()&lt;/code&gt;, this will lead to the device hardfaulting because us calling &lt;code&gt;sd_ble_gap_ppcp_set&lt;/code&gt; which is a SoftDevice function. You need to initialize the BLE Stack before calling functions with sd_-prefix.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62676?ContentTypeID=1</link><pubDate>Mon, 03 Oct 2016 07:02:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d68aa82-2cf3-48c1-8a86-f86a2614bc98</guid><dc:creator>Ted</dc:creator><description>&lt;p&gt;@Bjorn, The project is too big. Attach the main 3 files. The Pstorage was broken, so it make pack.device_name_length and pack.device_name error. The program will cause system reset at function of gap_params_init.&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/flash_5F00_crash.zip"&gt;flash_crash.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62675?ContentTypeID=1</link><pubDate>Wed, 28 Sep 2016 09:28:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7eb8f5c2-5189-4d5e-baf7-8b0e48464ddb</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@lerrywu (Ted): I apologize for my late response. The b_pstorge.c attachment is identical to b_pstorge.h, so I am missing the .c file. However, It would be more helpful if you could tell me which specific function the device runs which results in the device entering a &amp;quot;dead loop&amp;quot;.  The best thing would be if you could share you application project so that I can try to reproduce the issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62674?ContentTypeID=1</link><pubDate>Mon, 19 Sep 2016 01:33:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4de44bad-2d96-4da0-9835-d125cb048a16</guid><dc:creator>Ted</dc:creator><description>&lt;p&gt;Yes, I using persitant storage manager to store some datas.I created a block for 40-byte data. I&amp;#39;ll call the function of pstorage_creat and pstorage_init_and_load at main function. (system initialization)&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/b_5F00_pstorge.h"&gt;b_pstorge.c&lt;/a&gt;(/attachment/7b920c630eb4bd54e5f5f2f3bd199829)&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4760.b_5F00_pstorge.h"&gt;b_pstorge.h&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hi Bjorn, Do you have any update? Is there any wrong in my code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62669?ContentTypeID=1</link><pubDate>Wed, 14 Sep 2016 08:35:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f989872d-0a06-4cfc-a927-f26a49c6643b</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Which function specifically? Are you using the persistant storage manager to store any application data?
Would it be possible for you to share your firmware? If it is confidential then we can move the case to Mypage which is our closed support portal.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62673?ContentTypeID=1</link><pubDate>Wed, 14 Sep 2016 02:20:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aee6f78e-8e51-4903-a644-983c8cdc4492</guid><dc:creator>Ted</dc:creator><description>&lt;p&gt;Yes, the bootloader passes execution to the application. Application runs to some function and causes it run into a dead loop. I want to know why and when the flash is modified and how to protect flash? The address at 0x0003b800 is similar pstorage area.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62671?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2016 10:26:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c09454a9-cf7b-4ff3-96f3-edc85b2a4306</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Have you tried debugging the non-working product? You should be able to check if the bootloader is  running and if it passes execution to the application. If it passes execution to the application then you know that the problem lies in the application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62670?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2016 09:34:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4d9fbc9-7893-4690-8497-53234866fb08</guid><dc:creator>Ted</dc:creator><description>&lt;p&gt;Hi Bjorn, The set will flash LED during power on if it is working, but it didn&amp;#39;t flash LED. Yes, I am using a bootloader. I used nrfjprog to dump the codes both sets for entire flash (256Kbytes). then I found that the differences are at the address of 0x0003b808 to 0x0003b937. The working set&amp;#39;s datas are 0xffffffff between the address of 0x0003b808 and 0x0003b937. But the broken set&amp;#39;s datas aren&amp;#39;t 0xffffffff between the address of 0x0003b808 and 0x0003b937. Does it make the set broken? How to solve it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flash crash</title><link>https://devzone.nordicsemi.com/thread/62672?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2016 08:56:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a9693a5-e97a-4cc1-a92c-dd30b6bd08fd</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi Ted, could you explain a bit more in detail what you mean by not working? Are you using a bootloader?The flash section below 0x3C000 is usually used by the Persistant Storage Manager to store application data and bonding information.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>