<?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>unintended flash erase</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25783/unintended-flash-erase</link><description>Hi, 
 we have a nrf51 mounted inside an AC motor housing which we assume is causing an unintended flash erase from time to time (checked with nrfjprog --readcode). 
 Is this a valid assumption?
Are there any solutions for this problem? E.g. shielding</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Aug 2018 13:23:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25783/unintended-flash-erase" /><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/145941?ContentTypeID=1</link><pubDate>Mon, 27 Aug 2018 13:23:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af4e6f85-7bd8-479a-a46c-69777cce1aee</guid><dc:creator>gorazd</dc:creator><description>&lt;p&gt;We discarded the module that was causing the problem. Other modules did not exhibit the problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/145878?ContentTypeID=1</link><pubDate>Mon, 27 Aug 2018 09:31:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb08b949-7fc7-41b4-acd4-51f6f14cb390</guid><dc:creator>kamisen</dc:creator><description>&lt;p&gt;Had your question been resolved?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/145876?ContentTypeID=1</link><pubDate>Mon, 27 Aug 2018 09:30:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5cca0d89-9a2c-4834-a650-7ac5f8512845</guid><dc:creator>kamisen</dc:creator><description>&lt;p&gt;Had your question been resolved?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101563?ContentTypeID=1</link><pubDate>Fri, 20 Oct 2017 05:50:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7fb33ab1-cf0e-46be-bbd7-4a805ff273bf</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Ok, let me know how it goes then.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101562?ContentTypeID=1</link><pubDate>Thu, 19 Oct 2017 05:30:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92eae98e-bee5-4cea-9235-62cbcefda62f</guid><dc:creator>gorazd</dc:creator><description>&lt;p&gt;Tnx
I will attach the resistor.
We also found out not all of the modules exhibit the problem or the problem is meybe harder to reproduce. But we had one module which we could reproduce the problem many times in a row on.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101561?ContentTypeID=1</link><pubDate>Tue, 17 Oct 2017 13:48:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1eaa53f2-9c60-46b8-9c95-efadfc202f02</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m unable to open your files. They seem to lack file extensions. You can edit your question and attach them directly in your post.&lt;/p&gt;
&lt;p&gt;The nRF51 has a design flaw related to the SWD and reset pins and is known to unexpectedly reset itself and maybe enter unknown states. This may be caused by noise on the SWD lines generated by for example magnetic fields. The workaround is to attach a 1k pull-down restistor on the SDWCLK pin as shown in the latest &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf51/dita/nrf51/pdflinks/ref_layout.html?cp=3_6"&gt;reference schematic&lt;/a&gt;. Have you done this? Anyway, I&amp;#39;m unsure how this would result in an erased flash, but the cases I have seen related to magnetic fields have also been related to noise on the SWD lines.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101559?ContentTypeID=1</link><pubDate>Mon, 09 Oct 2017 11:52:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4759fc81-4e2b-4635-9e1f-157ec498d640</guid><dc:creator>gorazd</dc:creator><description>&lt;p&gt;Additional information: we have a level shifter TCA9406 to communicate with motor over uart which is on 5V.
Also, we suspect the flash erase happens after the motor (we dont even start the motor spinning and advertising works just fine up until then) is plugged out which results in capacitors  slowly discharging and eventually putting our module into reset. After that the module is dead (flash empty) and the module needs to be reprogrammed to work again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101560?ContentTypeID=1</link><pubDate>Mon, 09 Oct 2017 08:56:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc8a0165-0b2a-4ae4-a2be-ea06085a129d</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Really looks nicely erased... to do such mass erase it would probably need to write into UICR and then reset the chip. Not sure how probable this is in case you have the chip in strong magnetic field. But it would be more probable that some corruptions happen already before so it would be interesting to dump the chip while it is still working and compare against the original HEX image.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101558?ContentTypeID=1</link><pubDate>Mon, 09 Oct 2017 08:43:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41be8a68-79ec-4c8b-8934-74ccdd881fa8</guid><dc:creator>gorazd</dc:creator><description>&lt;p&gt;I leave it by default (unprotected)&lt;/p&gt;
&lt;p&gt;Outside the housing everything works fine (&lt;a href="https://www.dropbox.com/s/bv8rgsroop2f8g6/koda2?dl=0"&gt;This is inside the flash&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;Once in housing it stops working (&lt;a href="https://www.dropbox.com/s/2u3y7lgtm3nmqb5/koda3?dl=0"&gt;This is in flash&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;EDIT: broken links fixed&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unintended flash erase</title><link>https://devzone.nordicsemi.com/thread/101557?ContentTypeID=1</link><pubDate>Mon, 09 Oct 2017 08:27:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4240b097-93b5-4d10-ab01-f35022d797a3</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;This is quite strange. How exactly you check the flash state? You leave it unprotected (RBPALL register not set) and then once it stops working you dump it and whole flash is erased meaning set to 0xFF..FF? Isn&amp;#39;t there other kind of corruption before?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>