<?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>After DFU update Device does not reset</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54974/after-dfu-update-device-does-not-reset</link><description>Hello, 
 I have issue that after firmware update in DFU mode through BLE device does not reset. If i test updating firmware for 10 to 20 times then 4 to 5 times it does not get reset in rest cases get reset. Could not find any such reason for such observation</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Jan 2020 12:11:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54974/after-dfu-update-device-does-not-reset" /><item><title>RE: After DFU update Device does not reset</title><link>https://devzone.nordicsemi.com/thread/231115?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2020 12:11:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f812f698-38aa-4017-a4bf-140b157dbdd0</guid><dc:creator>ssc</dc:creator><description>&lt;p&gt;I have solved this issue by changing the bootloader mode entering method. Previously I was using DFU service in my main application. Now I am using the GPREGRET register method to enter bootloader mode and resetting the device. This is making my OTA process faster as well as the issue of disconnection after entering bootloader mode is also covered.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: After DFU update Device does not reset</title><link>https://devzone.nordicsemi.com/thread/222797?ContentTypeID=1</link><pubDate>Fri, 29 Nov 2019 12:31:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:523f2197-6442-4dd7-b73a-bd16e8ed7caa</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
[quote user=""]I am using SDK 15.2.0 version. IDE used is Segger embedded studio which shows&amp;nbsp;Toolchain version 7-2018-q2-update source distribution.&amp;nbsp;[/quote]
&lt;p&gt;Could you use GCC ARM Embedded 6.3 2017-q2-update as our suggestion in&amp;nbsp;&lt;a title="nRF5 SDK v15.2.0" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/index.html?cp=6_5_1"&gt;nRF5 SDK v15.2.0&lt;/a&gt;?&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Link Time Optimization(LTO) issue occurred when using a GCC version that was not production tested with the nRF5 SDK, e.g. using&amp;nbsp;&lt;/span&gt;&lt;span&gt;GCC ARM Embedded 7 instead of&amp;nbsp;&lt;/span&gt;&lt;span&gt;GCC ARM Embedded 6.3. We also do not see any issues with LTO when using the correct GCC version.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;-Amanda H.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>