<?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>NRF52 dk won&amp;#39;t flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/15760/nrf52-dk-won-t-flash-anymore-any-hope</link><description>My &amp;#181;vision crashed during programming and will no longer respond to trying to program it. It boots into the bootloader mode. My computer sees it but the precompiled binaries don&amp;#39;t seem to have any affect. NRFGo also sees it. Trying to program the board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 01 Sep 2016 06:08:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/15760/nrf52-dk-won-t-flash-anymore-any-hope" /><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60155?ContentTypeID=1</link><pubDate>Thu, 01 Sep 2016 06:08:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a8056fa9-9fe9-4dcf-a527-d6780a5699b5</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Then you need to send your chip to us so that we can examine. Please open a support case and get more instructions on how to proceed further.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60154?ContentTypeID=1</link><pubDate>Thu, 01 Sep 2016 03:36:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d550e510-1b10-4ccc-af13-7f3d5de6f00d</guid><dc:creator>Cleadonta</dc:creator><description>&lt;p&gt;Sadly no. All applications including the sdk examples exhibit the same behavior.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60150?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 07:17:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4600715f-e592-45f7-ac2a-dafa2a2800cc</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Is it possible that your program is writing to wrong address in flash? can you program a simple blinky program (some some other simple sdk example) and see if it is the same behavior. If not then your application is the culprit.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60152?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 01:43:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6149f919-d839-4d32-a958-a14f95901e7e</guid><dc:creator>Cleadonta</dc:creator><description>&lt;p&gt;In short, yes. That is exactly what happens.&lt;/p&gt;
&lt;p&gt;What it seems like is that it cannot hold a program. It lets you program it, then promptly forgets the program you sent it. I&amp;#39;m not sure what might be causing that. I &amp;quot;confirmed&amp;quot; this with the nRFgo Studio program. Anything programmed to the chip will disappear within moments of the upload finishing. Something odd is going on. I&amp;#39;m at a loss for what to do next.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60151?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2016 06:41:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f921b580-0155-482b-8539-6dee20f99f30</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;That is strange, the reset handler in arm_startup_nrf52.s clearly tells it to run main function after SystemInit&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Reset_Handler   PROC
                EXPORT  Reset_Handler             [WEAK]
                IMPORT  SystemInit
                IMPORT  __main
                
                LDR     R0, =SystemInit
                BLX     R0
                LDR     R0, =__main
                BX      R0
                ENDP
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Are you saying that it is able to run SystemInit function full and then hardfaults when it returns from this function?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60153?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2016 01:44:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4a328343-1a65-49e8-a5bb-f8aa2af5d8c7</guid><dc:creator>Cleadonta</dc:creator><description>&lt;p&gt;It looks like as soon as it starts, it goes until it hits:
&lt;code&gt;0x00000522 E7FE B 0x00000522&lt;/code&gt;
in disassembly mode and then stops. Any ideas? It stops at the same place for two different programs, one I made and a sample one. With 0 optimization this is in the &lt;code&gt;HardFault_Handler/&lt;/code&gt; exception handler in arm_startup_nrf52.s. It seems like it gets sent there right after finishing the  &lt;code&gt;void SystemInit(void)&lt;/code&gt; function in system_nrf52.c. Is it just not knowing what to do after the startup code is executed?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 dk won't flash anymore? Any hope?</title><link>https://devzone.nordicsemi.com/thread/60149?ContentTypeID=1</link><pubDate>Tue, 16 Aug 2016 06:29:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:955fda03-6783-492c-9916-1c9ee0d46682</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;if Keil and nRFgo sees your device then it is not bricked. Bricked means there is no way that any debugger could connect your device and halt the CPU in time.&lt;/p&gt;
&lt;p&gt;You said that you are even able to reprogram but it does not have any affect, In that case i would suggest you to compile your program with no optimizations and start in debug mode to see if anything is running at all in the CPU.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>