<?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>Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51829/bootloader-dfu-stop-advertising-after-updating-new-firmware</link><description>Hello, 
 I&amp;#39;m using this example of code (nRF5_SDK_11.0.0_89a8197\examples\dfu\bootloader\pca10040\dual_bank_ble_s132\arm5_no_packs) with my custom board to perform a dfu. So in this it&amp;quot;s seems to support use of button but in my case there is no button</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 22 Oct 2019 16:06:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51829/bootloader-dfu-stop-advertising-after-updating-new-firmware" /><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/216223?ContentTypeID=1</link><pubDate>Tue, 22 Oct 2019 16:06:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24399dfb-ae7f-4a74-a47b-7d18343d24a4</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t think we have done any qualification of nRF52 with S132v2.0. If you want to use NRF52840 I would suggest to use S140. You would need to port the application in SDK v11 to use S140 instead.&amp;nbsp;&lt;br /&gt;However we strongly suggest you to use our latest SDK for new development.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214445?ContentTypeID=1</link><pubDate>Thu, 10 Oct 2019 15:10:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d9acfa7-89ce-4141-b2f5-a13adaaa6169</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Thanks a lot,&lt;/p&gt;
&lt;p&gt;i will try and share with you result :).&lt;/p&gt;
&lt;p&gt;Can i use the SDK11 and this bootloader&amp;nbsp; with nrf52840, because i plane to move all my developement to this plateform.&lt;/p&gt;
&lt;p&gt;Is the SoftDevice s132_v2.0.0 still compatible with nrf52840?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214295?ContentTypeID=1</link><pubDate>Thu, 10 Oct 2019 08:51:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:152c0700-d23d-4da8-acd1-3abc49684a15</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;If you set it to 100 it will advertise at 100-110ms (+10ms randomized to avoid interference) interval. You are free to set it from 20 (ms)to 10000 (ms)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214205?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 14:28:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:21e605f5-6bc2-4002-8a52-a2dde5464805</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;#define APP_ADV_INTERVAL                     MSEC_TO_UNITS(100, UNIT_0_625_MS) &lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I set this variable to 100, is a correct value or i should make it bigger than 100 ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214203?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 14:20:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf8d2a08-7861-4e06-982c-8b9b4b140995</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;You can modify&amp;nbsp;APP_ADV_INTERVAL inside dfu_transport_ble.c&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214200?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 14:11:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:57dbf126-df04-4721-93b4-63273de111d3</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;How can i increase advertising connexion value ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214178?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 13:15:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25e9c6f9-05b1-4aa2-9962-d0d38452ff4c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;It&amp;#39;s normal to have these 7.8mA peak, it&amp;#39;s when the bootloader advertising. Without periodically advertising, you can&amp;#39;t establish a connection. You can increase the advertising interval to make it draw less current.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214154?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 12:06:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4a7f26f3-fcbe-4296-bbed-c164698039c6</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;sorry , i missed to tell that i m using small resistor(100 ohm) in line with power supply (3,6 V). So the average current is&amp;nbsp; 7,8 mA .&lt;/p&gt;
&lt;p&gt;&amp;quot;Is waiting for image packet&amp;quot; means that&amp;nbsp; the connection is not established yet . That&amp;#39;s why im totally surprised that bootloader still consuming current even though there is no connection .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214131?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 11:10:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3fee66fd-e3b0-42d4-9e1c-4224fdf45141</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The image doesn&amp;#39;t show the current (it shows the voltage drop ? ) so I don&amp;#39;t know what&amp;#39;s the current is.&lt;/p&gt;
&lt;p&gt;When you mentioned &amp;quot;&lt;span&gt;&amp;nbsp;is waiting for image packet&amp;quot;, is the connection established or not ? In both case, the bootloader will either advertise , or have to wake up to handle the connection (even though there is no data transfer) so it&amp;#39;s normal to periodically have some peak current.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The long period after the image transfer finish could be the period where the image is swapped the CPU has to be active to do flash operation.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214090?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 09:37:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf9c03b1-820f-4853-84e9-a5db1e697c1d</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;thank you for replay. I have attached some screenshot to show current drawing in different phase bootloader runing.&lt;/p&gt;
&lt;p&gt;In this picture, bootloader continue to consume current even if is waiting for image packets (Here Peer device doesn&amp;#39;t start sending image file).&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/SDS00005.png" /&gt;&lt;/p&gt;
&lt;p&gt;Here, peer device start sending packet&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/SDS00006.png" /&gt;&lt;/p&gt;
&lt;p&gt;and after finshed image downloding there is a current peak&amp;nbsp; consumption due to the transition from bootloader to the application&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/SDS00007.png" /&gt;&lt;/p&gt;
&lt;p&gt;i hope it a bit clear now.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;quot;Are you using our unmodified bootloader ? &amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;yes, i m using unmodified bootloader.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/214062?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2019 08:19:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a51de2d3-89a9-46b6-a196-d3c081d2f6dc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Usually we use a retention register instead of a shared RAM area but I think it would be fine.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;200 byte per second is very low. I would assume that it&amp;#39;s the limitation on the peer device, not because of the nRF52 ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure I understand what you meant by 5mA every 1s. Do you mean 5mAh&amp;nbsp; ? Current can&amp;#39;t be measured over time.&lt;/p&gt;
&lt;p&gt;Or it&amp;#39;s the constant 5mA current you are seeing ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Are you using our unmodified bootloader ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/213998?ContentTypeID=1</link><pubDate>Tue, 08 Oct 2019 18:02:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7dc26407-c147-49be-be55-000c30c3a337</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Hi Hung Bui,&lt;/p&gt;
&lt;p&gt;I have added&amp;nbsp; share memory&amp;nbsp; flash adrress between bootloader and application.So its a simple way to force bootloader to&amp;nbsp; enter bootloader mode by&amp;nbsp; writing&amp;nbsp; &amp;quot;true&amp;quot; value in to this memory&amp;nbsp;adress from the application and make a prompt test to the above &amp;quot;flag&amp;quot; variable.&lt;/p&gt;
&lt;p&gt;Now Im facing another issue, it&amp;#39;s about power consumption. The software that&amp;#39;s im use to send app image ,transmitt about 200 Byte every 1s and my app image is about 33KByte, So i spend more 3 min to download all the image.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;During the download, Bootloader DFU draw 5mA every 1s, so for 3min I consume 900 mA.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My question is, there is any way to reduce power consumption ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/211890?ContentTypeID=1</link><pubDate>Wed, 25 Sep 2019 15:27:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a3222e5-ce18-4e00-b67e-280ff2c83f1d</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Please tell exactly how you share the flag variable ?&amp;nbsp;How do you switch from application to bootloader ?&lt;/p&gt;
&lt;p&gt;Note that RAM get reset when you trigger a soft reset .&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You would need to either use retention register (GPREGRET) or use flash to store the data of the flag.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/211586?ContentTypeID=1</link><pubDate>Tue, 24 Sep 2019 14:46:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8e0b1be5-3883-4869-b9a2-5c8aef247cc1</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Hi Hung Bui,&lt;/p&gt;
&lt;p&gt;I Have not test the Buttonless example, I have creat&amp;nbsp; a&amp;nbsp;Custom Service in My Application that trigger Bootloader to enter in DFU Mode . So I have added somme line in Bootloader main code to creat shared area where i place flag that&amp;nbsp; my app change when i wont to enter DFU Boot mode.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;		if (flag == 1) 
		{			
			dfu_start= true;
			flag = 0;
		}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;So, the problem is i can&amp;#39;t get the flag change after soft rest . Can you please tell me the correct way to set the flag after boot to valid application.&lt;/p&gt;
&lt;p&gt;Kindly regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/209349?ContentTypeID=1</link><pubDate>Thu, 12 Sep 2019 09:01:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f6ea84b2-70e0-4c9b-84a1-815f82edc105</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please first make sure you have tested the buttonless example and you can do a DFU update without a button.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Then you can start integrate it into your application. Please make sure you have configured the memory properly. Increase the&amp;nbsp;vs_uuid_count in the softdevice enable configuration, before calling&amp;nbsp;softdevice_enable()&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/209244?ContentTypeID=1</link><pubDate>Wed, 11 Sep 2019 15:45:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a336f6b0-0ebf-4e45-af1d-77ddc3059ea5</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Yes I Know that SDK15.3 is the latest version, but for my project needs i use SDK11 version.&lt;/p&gt;
&lt;p&gt;So, I have devlopped a Python application that integrate a dfu process and fit the dfu exmple project that you have provide in sdk11.&lt;/p&gt;
&lt;p&gt;The problem with this example is that they use Button to enter in DFU mode and for my project needs , the dfu should bye placed in Bootloader not in the Application that&amp;#39;s why i look for an example of bootloader thats not need tu use button to enter in dfu mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/209105?ContentTypeID=1</link><pubDate>Wed, 11 Sep 2019 08:43:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7086a760-b618-4ec6-9341-b22f2f9db3ab</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;I&amp;#39;m not familiar with DAP debugger, but as far as I know you should be able to set a breakpoint and step using GDB. As in this &lt;a href="https://ravikiranb.com/projects/cmsis-dap-debug/"&gt;link &lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;What you need to do is to add a breakpoint inside app_error_handler() and check what error and which line cause the issue.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure how you build your application without debugging ability ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s strongly recommended to get hold of a nRF52 DK. You can use the DK as a Jlink debugger.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;One question, why do you use SDK v11&amp;nbsp; ? The latest SDK is v15.3&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/209009?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2019 15:08:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2e4ed745-613d-42f0-8b03-79948b4f53c2</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;I can&amp;#39;t have more debug information because i use DAP Link Debugger . How can I print debug information with this debugger (Nordic use Jlink debugger to have more information)&amp;nbsp; and in my project i don&amp;#39;t have sdk_config.h inside project&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208986?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2019 14:00:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c720e68e-3f97-4529-87b6-8001d6fb8a4f</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Before we can look into the code, we need to have your debug information. If you don&amp;#39;t have any problem with debugging it, you should tell us where exactly the problem happens, where the assertion is. Then we can give you advices or run the test here.&lt;/p&gt;
&lt;p&gt;We can&amp;#39;t do the homework for you.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208965?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2019 13:19:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d8bbd41d-6a71-4588-856d-bd2f8afac429</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;I would like to know if the code that&amp;#39;s i have added is coorect, if not could you please correct me if i&amp;#39;m looking wrong. I dont have any probleme with debugging application&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208891?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2019 11:25:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f9aae0b4-d30a-4d79-8806-f110a4584804</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Please try debugging. Here is the &lt;a href="https://devzone.nordicsemi.com/question/60125/my-device-is-freezing-and-restarting/#60126"&gt;debug guide.&amp;nbsp;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208858?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2019 10:12:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5967de57-34e4-4945-a6e5-9618456b1149</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;yes i have already follow this link and i have add all files which required tu support dfu in app. So, when programme the new app with this modification my app stop advertising &amp;quot;HRM_Blinky&amp;quot;. I have runned it in debug mode (Im using keil ) the software do not jump on &amp;quot;advertising_start()&amp;quot; .&lt;/p&gt;
&lt;p&gt;Here the modification that&amp;#39;s i made on main.c (experimental_ble_app_blinky project) :&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;/* Copyright (c) 2015 Nordic Semiconductor. All Rights Reserved.
 *
 * The information contained herein is property of Nordic Semiconductor ASA.
 * Terms and conditions of usage are described in detail in NORDIC
 * SEMICONDUCTOR STANDARD SOFTWARE LICENSE AGREEMENT.
 *
 * Licensees are granted free, non-transferable use of the information. NO
 * WARRANTY of ANY KIND is provided. This heading must NOT be removed from
 * the file.
 *
 */

/** 
 * @brief Blinky Sample Application main file.
 *
 * This file contains the source code for a sample server application using the LED Button service.
 */

#include &amp;lt;stdint.h&amp;gt;
#include &amp;lt;string.h&amp;gt;
#include &amp;quot;nordic_common.h&amp;quot;
#include &amp;quot;nrf.h&amp;quot;
#include &amp;quot;app_error.h&amp;quot;
#include &amp;quot;ble.h&amp;quot;
#include &amp;quot;ble_hci.h&amp;quot;
#include &amp;quot;ble_srv_common.h&amp;quot;
#include &amp;quot;ble_advdata.h&amp;quot;
#include &amp;quot;ble_conn_params.h&amp;quot;
#include &amp;quot;softdevice_handler.h&amp;quot;
#include &amp;quot;app_timer.h&amp;quot;
#include &amp;quot;app_button.h&amp;quot;
#include &amp;quot;ble_lbs.h&amp;quot;
#include &amp;quot;bsp.h&amp;quot;
#include &amp;quot;ble_gap.h&amp;quot;
#ifdef BLE_DFU_APP_SUPPORT
#include &amp;quot;ble_dfu.h&amp;quot;
#include &amp;quot;dfu_app_handler.h&amp;quot;
#endif // BLE_DFU_APP_SUPPORT
#include &amp;quot;ble_advertising.h&amp;quot;
#include &amp;quot;ble_bas.h&amp;quot;
#include &amp;quot;ble_dis.h&amp;quot;
#include &amp;quot;device_manager.h&amp;quot;
#include &amp;quot;pstorage.h&amp;quot;
#include &amp;quot;nrf_delay.h&amp;quot;

#define IS_SRVC_CHANGED_CHARACT_PRESENT  1                                          /**&amp;lt; Include or not the service_changed characteristic. if not enabled, the server&amp;#39;s database cannot be changed for the lifetime of the device*/

#define CENTRAL_LINK_COUNT              0                                           /**&amp;lt; Number of central links used by the application. When changing this number remember to adjust the RAM settings*/
#define PERIPHERAL_LINK_COUNT           1                                           /**&amp;lt; Number of peripheral links used by the application. When changing this number remember to adjust the RAM settings*/

#define ADVERTISING_LED_PIN             BSP_LED_0_MASK                              /**&amp;lt; Is on when device is advertising. */
#define CONNECTED_LED_PIN               BSP_LED_0_MASK                              /**&amp;lt; Is on when device has connected. */

#define LEDBUTTON_LED_PIN               BSP_LED_0_MASK                              /**&amp;lt; LED to be toggled with the help of the LED Button Service. */
//#define LEDBUTTON_BUTTON_PIN            BSP_BUTTON_0                                /**&amp;lt; Button that will trigger the notification event with the LED Button Service */

#define DEVICE_NAME                     &amp;quot;Nordic_Blinky&amp;quot;                             /**&amp;lt; Name of device. Will be included in the advertising data. */

#define APP_ADV_INTERVAL                64                                          /**&amp;lt; The advertising interval (in units of 0.625 ms; this value corresponds to 40 ms). */
#define APP_ADV_TIMEOUT_IN_SECONDS      BLE_GAP_ADV_TIMEOUT_GENERAL_UNLIMITED       /**&amp;lt; The advertising time-out (in units of seconds). When set to 0, we will never time out. */

#define APP_TIMER_PRESCALER             0                                           /**&amp;lt; Value of the RTC1 PRESCALER register. */
#define APP_TIMER_MAX_TIMERS            6                                           /**&amp;lt; Maximum number of simultaneously created timers. */
#define APP_TIMER_OP_QUEUE_SIZE         4                                           /**&amp;lt; Size of timer operation queues. */

#define MIN_CONN_INTERVAL               MSEC_TO_UNITS(100, UNIT_1_25_MS)            /**&amp;lt; Minimum acceptable connection interval (0.5 seconds). */
#define MAX_CONN_INTERVAL               MSEC_TO_UNITS(200, UNIT_1_25_MS)            /**&amp;lt; Maximum acceptable connection interval (1 second). */
#define SLAVE_LATENCY                   0                                           /**&amp;lt; Slave latency. */
#define CONN_SUP_TIMEOUT                MSEC_TO_UNITS(4000, UNIT_10_MS)             /**&amp;lt; Connection supervisory time-out (4 seconds). */
#define FIRST_CONN_PARAMS_UPDATE_DELAY  APP_TIMER_TICKS(20000, APP_TIMER_PRESCALER) /**&amp;lt; Time from initiating event (connect or start of notification) to first time sd_ble_gap_conn_param_update is called (15 seconds). */
#define NEXT_CONN_PARAMS_UPDATE_DELAY   APP_TIMER_TICKS(5000, APP_TIMER_PRESCALER)  /**&amp;lt; Time between each call to sd_ble_gap_conn_param_update after the first call (5 seconds). */
#define MAX_CONN_PARAMS_UPDATE_COUNT    3                                           /**&amp;lt; Number of attempts before giving up the connection parameter negotiation. */

#define SEC_PARAM_BOND                   1                                          /**&amp;lt; Perform bonding. */
#define SEC_PARAM_MITM                   0                                          /**&amp;lt; Man In The Middle protection not required. */
#define SEC_PARAM_LESC                   0                                          /**&amp;lt; LE Secure Connections not enabled. */
#define SEC_PARAM_KEYPRESS               0                                          /**&amp;lt; Keypress notifications not enabled. */
#define SEC_PARAM_IO_CAPABILITIES        BLE_GAP_IO_CAPS_NONE                       /**&amp;lt; No I/O capabilities. */
#define SEC_PARAM_OOB                    0                                          /**&amp;lt; Out Of Band data not available. */
#define SEC_PARAM_MIN_KEY_SIZE           7                                          /**&amp;lt; Minimum encryption key size. */
#define SEC_PARAM_MAX_KEY_SIZE           16                                         /**&amp;lt; Maximum encryption key size. */

#define APP_GPIOTE_MAX_USERS            1                                           /**&amp;lt; Maximum number of users of the GPIOTE handler. */
#define BUTTON_DETECTION_DELAY          APP_TIMER_TICKS(50, APP_TIMER_PRESCALER)    /**&amp;lt; Delay from a GPIOTE event until a button is reported as pushed (in number of timer ticks). */

#define DEAD_BEEF                       0xDEADBEEF                                  /**&amp;lt; Value used as error code on stack dump, can be used to identify stack location on stack unwind. */

#ifdef BLE_DFU_APP_SUPPORT
#define DFU_REV_MAJOR                    0x00                                       /** DFU Major revision number to be exposed. */
#define DFU_REV_MINOR                    0x01                                       /** DFU Minor revision number to be exposed. */
#define DFU_REVISION                     ((DFU_REV_MAJOR &amp;lt;&amp;lt; 8) | DFU_REV_MINOR)     /** DFU Revision number to be exposed. Combined of major and minor versions. */
#define APP_SERVICE_HANDLE_START         0x000C                                     /**&amp;lt; Handle of first application specific service when when service changed characteristic is present. */
#define BLE_HANDLE_MAX                   0xFFFF                                     /**&amp;lt; Max handle value in BLE. */

STATIC_ASSERT(IS_SRVC_CHANGED_CHARACT_PRESENT);                                     /** When having DFU Service support in application the Service Changed Characteristic should always be present. */
#endif // BLE_DFU_APP_SUPPORT

#ifdef BLE_DFU_APP_SUPPORT
static ble_dfu_t                         m_dfus;                                    /**&amp;lt; Structure used to identify the DFU service. */
#endif // BLE_DFU_APP_SUPPORT

static uint16_t                         m_conn_handle = BLE_CONN_HANDLE_INVALID;    /**&amp;lt; Handle of the current connection. */
static ble_lbs_t                        m_lbs;                                      /**&amp;lt; LED Button Service instance. */

static dm_application_instance_t         m_app_handle;                              /**&amp;lt; Application identifier allocated by device manager */
/**@brief Function for assert macro callback.
 *
 * @details This function will be called in case of an assert in the SoftDevice.
 *
 * @warning This handler is an example only and does not fit a final product. You need to analyze 
 *          how your product is supposed to react in case of Assert.
 * @warning On assert from the SoftDevice, the system can only recover on reset.
 *
 * @param[in] line_num    Line number of the failing ASSERT call.
 * @param[in] p_file_name File name of the failing ASSERT call.
 */
void assert_nrf_callback(uint16_t line_num, const uint8_t * p_file_name)
{
    app_error_handler(DEAD_BEEF, line_num, p_file_name);
}


/**@brief Function for the LEDs initialization.
 *
 * @details Initializes all LEDs used by the application.
 */
static void leds_init(void)
{
	  //LEDS_CONFIGURE(ADVERTISING_LED_PIN | CONNECTED_LED_PIN | LEDBUTTON_LED_PIN);
    //LEDS_OFF(ADVERTISING_LED_PIN | CONNECTED_LED_PIN | LEDBUTTON_LED_PIN);
	
    LEDS_CONFIGURE(ADVERTISING_LED_PIN | CONNECTED_LED_PIN );
    LEDS_OFF(ADVERTISING_LED_PIN | CONNECTED_LED_PIN );	
}


/**@brief Function for the Timer initialization.
 *
 * @details Initializes the timer module.
 */
static void timers_init(void)
{
    // Initialize timer module, making it use the scheduler
    APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_OP_QUEUE_SIZE, false);
}


/**@brief Function for the GAP initialization.
 *
 * @details This function sets up all the necessary GAP (Generic Access Profile) parameters of the
 *          device including the device name, appearance, and the preferred connection parameters.
 */
static void gap_params_init(void)
{
    uint32_t                err_code;
    ble_gap_conn_params_t   gap_conn_params;
    ble_gap_conn_sec_mode_t sec_mode;

    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&amp;amp;sec_mode);

    err_code = sd_ble_gap_device_name_set(&amp;amp;sec_mode,
                                          (const uint8_t *)DEVICE_NAME,
                                          strlen(DEVICE_NAME));
    APP_ERROR_CHECK(err_code);

    memset(&amp;amp;gap_conn_params, 0, sizeof(gap_conn_params));

    gap_conn_params.min_conn_interval = MIN_CONN_INTERVAL;
    gap_conn_params.max_conn_interval = MAX_CONN_INTERVAL;
    gap_conn_params.slave_latency     = SLAVE_LATENCY;
    gap_conn_params.conn_sup_timeout  = CONN_SUP_TIMEOUT;

    err_code = sd_ble_gap_ppcp_set(&amp;amp;gap_conn_params);
    APP_ERROR_CHECK(err_code);
}


#ifdef BLE_DFU_APP_SUPPORT
/**@brief Function for stopping advertising.
 */
static void advertising_stop(void)
{
    uint32_t err_code;

    err_code = sd_ble_gap_adv_stop();
    APP_ERROR_CHECK(err_code);

    err_code = bsp_indication_set(BSP_INDICATE_IDLE);
    APP_ERROR_CHECK(err_code);
}


/**@brief Function for loading application-specific context after establishing a secure connection.
 *
 * @details This function will load the application context and check if the ATT table is marked as
 *          changed. If the ATT table is marked as changed, a Service Changed Indication
 *          is sent to the peer if the Service Changed CCCD is set to indicate.
 *
 * @param[in] p_handle The Device Manager handle that identifies the connection for which the context
 *                     should be loaded.
 */
static void app_context_load(dm_handle_t const * p_handle)
{
    uint32_t                 err_code;
    static uint32_t          context_data;
    dm_application_context_t context;

    context.len    = sizeof(context_data);
    context.p_data = (uint8_t *)&amp;amp;context_data;

    err_code = dm_application_context_get(p_handle, &amp;amp;context);
    if (err_code == NRF_SUCCESS)
    {
        // Send Service Changed Indication if ATT table has changed.
        if ((context_data &amp;amp; (DFU_APP_ATT_TABLE_CHANGED &amp;lt;&amp;lt; DFU_APP_ATT_TABLE_POS)) != 0)
        {
            err_code = sd_ble_gatts_service_changed(m_conn_handle, APP_SERVICE_HANDLE_START, BLE_HANDLE_MAX);
            if ((err_code != NRF_SUCCESS) &amp;amp;&amp;amp;
                (err_code != BLE_ERROR_INVALID_CONN_HANDLE) &amp;amp;&amp;amp;
                (err_code != NRF_ERROR_INVALID_STATE) &amp;amp;&amp;amp;
                (err_code != BLE_ERROR_NO_TX_PACKETS) &amp;amp;&amp;amp;
                (err_code != NRF_ERROR_BUSY) &amp;amp;&amp;amp;
                (err_code != BLE_ERROR_GATTS_SYS_ATTR_MISSING))
            {
                APP_ERROR_HANDLER(err_code);
            }
        }

        err_code = dm_application_context_delete(p_handle);
        APP_ERROR_CHECK(err_code);
    }
    else if (err_code == DM_NO_APP_CONTEXT)
    {
        // No context available. Ignore.
    }
    else
    {
        APP_ERROR_HANDLER(err_code);
    }
}


/** @snippet [DFU BLE Reset prepare] */
/**@brief Function for preparing for system reset.
 *
 * @details This function implements @ref dfu_app_reset_prepare_t. It will be called by
 *          @ref dfu_app_handler.c before entering the bootloader/DFU.
 *          This allows the current running application to shut down gracefully.
 */
static void reset_prepare(void)
{
    uint32_t err_code;

    if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
    {
        // Disconnect from peer.
        err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
        APP_ERROR_CHECK(err_code);
        err_code = bsp_indication_set(BSP_INDICATE_IDLE);
        APP_ERROR_CHECK(err_code);
    }
    else
    {
        // If not connected, the device will be advertising. Hence stop the advertising.
        advertising_stop();
    }

    err_code = ble_conn_params_stop();
    APP_ERROR_CHECK(err_code);

    nrf_delay_ms(500);
}
/** @snippet [DFU BLE Reset prepare] */
#endif // BLE_DFU_APP_SUPPORT



/**@brief Function for handling the Device Manager events.
 *
 * @param[in] p_evt  Data associated to the device manager event.
 */
static uint32_t device_manager_evt_handler(dm_handle_t const * p_handle,
                                           dm_event_t const  * p_event,
                                           ret_code_t        event_result)
{
    APP_ERROR_CHECK(event_result);

#ifdef BLE_DFU_APP_SUPPORT
    if (p_event-&amp;gt;event_id == DM_EVT_LINK_SECURED)
    {
        app_context_load(p_handle);
    }
#endif // BLE_DFU_APP_SUPPORT

    return NRF_SUCCESS;
}


/**@brief Function for the Device Manager initialization.
 *
 * @param[in] erase_bonds  Indicates whether bonding information should be cleared from
 *                         persistent storage during initialization of the Device Manager.
 */
static void device_manager_init(bool erase_bonds)
{
    uint32_t               err_code;
    dm_init_param_t        init_param = {.clear_persistent_data = erase_bonds};
    dm_application_param_t register_param;

    // Initialize persistent storage module.
    err_code = pstorage_init();
    APP_ERROR_CHECK(err_code);

    err_code = dm_init(&amp;amp;init_param);
    APP_ERROR_CHECK(err_code);

    memset(&amp;amp;register_param.sec_param, 0, sizeof(ble_gap_sec_params_t));

    register_param.sec_param.bond         = SEC_PARAM_BOND;
    register_param.sec_param.mitm         = SEC_PARAM_MITM;
    register_param.sec_param.lesc         = SEC_PARAM_LESC;
    register_param.sec_param.keypress     = SEC_PARAM_KEYPRESS;
    register_param.sec_param.io_caps      = SEC_PARAM_IO_CAPABILITIES;
    register_param.sec_param.oob          = SEC_PARAM_OOB;
    register_param.sec_param.min_key_size = SEC_PARAM_MIN_KEY_SIZE;
    register_param.sec_param.max_key_size = SEC_PARAM_MAX_KEY_SIZE;
    register_param.evt_handler            = device_manager_evt_handler;
    register_param.service_type           = DM_PROTOCOL_CNTXT_GATT_SRVR_ID;

    err_code = dm_register(&amp;amp;m_app_handle, &amp;amp;register_param);
    APP_ERROR_CHECK(err_code);
}


/**@brief Function for initializing the Advertising functionality.
 *
 * @details Encodes the required advertising data and passes it to the stack.
 *          Also builds a structure to be passed to the stack when starting advertising.
 */
static void advertising_init(void)
{
    uint32_t      err_code;
    ble_advdata_t advdata;
    ble_advdata_t scanrsp;

    ble_uuid_t adv_uuids[] = {{LBS_UUID_SERVICE, m_lbs.uuid_type}};

    // Build and set advertising data
    memset(&amp;amp;advdata, 0, sizeof(advdata));

    advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    advdata.include_appearance = true;
    advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;


    memset(&amp;amp;scanrsp, 0, sizeof(scanrsp));
    scanrsp.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);
    scanrsp.uuids_complete.p_uuids  = adv_uuids;

    err_code = ble_advdata_set(&amp;amp;advdata, &amp;amp;scanrsp);
    APP_ERROR_CHECK(err_code);
}


/**@brief Function for handling write events to the LED characteristic.
 *
 * @param[in] p_lbs     Instance of LED Button Service to which the write applies.
 * @param[in] led_state Written/desired state of the LED.
 */
static void led_write_handler(ble_lbs_t * p_lbs, uint8_t led_state)
{
    if (led_state)
    {
        LEDS_ON(LEDBUTTON_LED_PIN);
    }
    else
    {
        LEDS_OFF(LEDBUTTON_LED_PIN);
    }
}


/**@brief Function for initializing services that will be used by the application.
 */
static void services_init(void)
{
    uint32_t       err_code;
    ble_lbs_init_t init;

    init.led_write_handler = led_write_handler;

    err_code = ble_lbs_init(&amp;amp;m_lbs, &amp;amp;init);
    APP_ERROR_CHECK(err_code);
	
	
#ifdef BLE_DFU_APP_SUPPORT
    /** @snippet [DFU BLE Service initialization] */
    ble_dfu_init_t   dfus_init;

    // Initialize the Device Firmware Update Service.
    memset(&amp;amp;dfus_init, 0, sizeof(dfus_init));

    dfus_init.evt_handler   = dfu_app_on_dfu_evt;
    dfus_init.error_handler = NULL;
    dfus_init.evt_handler   = dfu_app_on_dfu_evt;
    dfus_init.revision      = DFU_REVISION;

    err_code = ble_dfu_init(&amp;amp;m_dfus, &amp;amp;dfus_init);
    APP_ERROR_CHECK(err_code);

    dfu_app_reset_prepare_set(reset_prepare);
    dfu_app_dm_appl_instance_set(m_app_handle);
    /** @snippet [DFU BLE Service initialization] */
#endif // BLE_DFU_APP_SUPPORT
}


/**@brief Function for handling the Connection Parameters Module.
 *
 * @details This function will be called for all events in the Connection Parameters Module that
 *          are passed to the application.
 *
 * @note All this function does is to disconnect. This could have been done by simply
 *       setting the disconnect_on_fail config parameter, but instead we use the event
 *       handler mechanism to demonstrate its use.
 *
 * @param[in] p_evt  Event received from the Connection Parameters Module.
 */
static void on_conn_params_evt(ble_conn_params_evt_t * p_evt)
{
    uint32_t err_code;

    if (p_evt-&amp;gt;evt_type == BLE_CONN_PARAMS_EVT_FAILED)
    {
        err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_CONN_INTERVAL_UNACCEPTABLE);
        APP_ERROR_CHECK(err_code);
    }
}


/**@brief Function for handling a Connection Parameters error.
 *
 * @param[in] nrf_error  Error code containing information about what went wrong.
 */
static void conn_params_error_handler(uint32_t nrf_error)
{
    APP_ERROR_HANDLER(nrf_error);
}


/**@brief Function for initializing the Connection Parameters module.
 */
static void conn_params_init(void)
{
    uint32_t               err_code;
    ble_conn_params_init_t cp_init;

    memset(&amp;amp;cp_init, 0, sizeof(cp_init));

    cp_init.p_conn_params                  = NULL;
    cp_init.first_conn_params_update_delay = FIRST_CONN_PARAMS_UPDATE_DELAY;
    cp_init.next_conn_params_update_delay  = NEXT_CONN_PARAMS_UPDATE_DELAY;
    cp_init.max_conn_params_update_count   = MAX_CONN_PARAMS_UPDATE_COUNT;
    cp_init.start_on_notify_cccd_handle    = BLE_GATT_HANDLE_INVALID;
    cp_init.disconnect_on_fail             = false;
    cp_init.evt_handler                    = on_conn_params_evt;
    cp_init.error_handler                  = conn_params_error_handler;

    err_code = ble_conn_params_init(&amp;amp;cp_init);
    APP_ERROR_CHECK(err_code);
}


/**@brief Function for starting advertising.
 */
static void advertising_start(void)
{
    uint32_t             err_code;
    ble_gap_adv_params_t adv_params;

    // Start advertising
    memset(&amp;amp;adv_params, 0, sizeof(adv_params));

    adv_params.type        = BLE_GAP_ADV_TYPE_ADV_IND;
    adv_params.p_peer_addr = NULL;
    adv_params.fp          = BLE_GAP_ADV_FP_ANY;
    adv_params.interval    = APP_ADV_INTERVAL;
    adv_params.timeout     = APP_ADV_TIMEOUT_IN_SECONDS;

    err_code = sd_ble_gap_adv_start(&amp;amp;adv_params);
    APP_ERROR_CHECK(err_code);
    LEDS_ON(ADVERTISING_LED_PIN);
}


/**@brief Function for handling the Application&amp;#39;s BLE stack events.
 *
 * @param[in] p_ble_evt  Bluetooth stack event.
 */
static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    uint32_t err_code;

    switch (p_ble_evt-&amp;gt;header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            LEDS_ON(CONNECTED_LED_PIN);
            LEDS_OFF(ADVERTISING_LED_PIN);
            m_conn_handle = p_ble_evt-&amp;gt;evt.gap_evt.conn_handle;

            err_code = app_button_enable();
            APP_ERROR_CHECK(err_code);
            break;

        case BLE_GAP_EVT_DISCONNECTED:
            LEDS_OFF(CONNECTED_LED_PIN);
            m_conn_handle = BLE_CONN_HANDLE_INVALID;

            err_code = app_button_disable();
            APP_ERROR_CHECK(err_code);

            advertising_start();
            break;

        case BLE_GAP_EVT_SEC_PARAMS_REQUEST:
            // Pairing not supported
            err_code = sd_ble_gap_sec_params_reply(m_conn_handle,
                                                   BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP,
                                                   NULL,
                                                   NULL);
            APP_ERROR_CHECK(err_code);
            break;

        case BLE_GATTS_EVT_SYS_ATTR_MISSING:
            // No system attributes have been stored.
            err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
            APP_ERROR_CHECK(err_code);
            break;

        default:
            // No implementation needed.
            break;
    }
}


/**@brief Function for dispatching a BLE stack event to all modules with a BLE stack event handler.
 *
 * @details This function is called from the scheduler in the main loop after a BLE stack
 *          event has been received.
 *
 * @param[in] p_ble_evt  Bluetooth stack event.
 */
static void ble_evt_dispatch(ble_evt_t * p_ble_evt)
{
    on_ble_evt(p_ble_evt);
    ble_conn_params_on_ble_evt(p_ble_evt);
    ble_lbs_on_ble_evt(&amp;amp;m_lbs, p_ble_evt);
#ifdef BLE_DFU_APP_SUPPORT
    /** @snippet [Propagating BLE Stack events to DFU Service] */
    ble_dfu_on_ble_evt(&amp;amp;m_dfus, p_ble_evt);
    /** @snippet [Propagating BLE Stack events to DFU Service] */
#endif // BLE_DFU_APP_SUPPORT
}


/**@brief Function for initializing the BLE stack.
 *
 * @details Initializes the SoftDevice and the BLE event interrupt.
 */
static void ble_stack_init(void)
{
    uint32_t err_code;
    
    nrf_clock_lf_cfg_t clock_lf_cfg = NRF_CLOCK_LFCLKSRC;
    
    // Initialize the SoftDevice handler module.
    SOFTDEVICE_HANDLER_INIT(&amp;amp;clock_lf_cfg, NULL);
    
    ble_enable_params_t ble_enable_params;
    err_code = softdevice_enable_get_default_config(CENTRAL_LINK_COUNT,
                                                    PERIPHERAL_LINK_COUNT,
                                                    &amp;amp;ble_enable_params);
    APP_ERROR_CHECK(err_code);
#ifdef BLE_DFU_APP_SUPPORT
    ble_enable_params.gatts_enable_params.service_changed = 1;
#endif // BLE_DFU_APP_SUPPORT
    //Check the ram settings against the used number of links
    CHECK_RAM_START_ADDR(CENTRAL_LINK_COUNT,PERIPHERAL_LINK_COUNT);
    
    // Enable BLE stack.
    err_code = softdevice_enable(&amp;amp;ble_enable_params);
    APP_ERROR_CHECK(err_code);

    ble_gap_addr_t addr;

    err_code = sd_ble_gap_address_get(&amp;amp;addr);
    APP_ERROR_CHECK(err_code);
    err_code = sd_ble_gap_address_set(BLE_GAP_ADDR_CYCLE_MODE_NONE, &amp;amp;addr);
    APP_ERROR_CHECK(err_code);

    // Subscribe for BLE events.
    err_code = softdevice_ble_evt_handler_set(ble_evt_dispatch);
    APP_ERROR_CHECK(err_code);
}


/**@brief Function for handling events from the button handler module.
 *
 * @param[in] pin_no        The pin that the event applies to.
 * @param[in] button_action The button action (press/release).
 */
//static void button_event_handler(uint8_t pin_no, uint8_t button_action)
//{
//    uint32_t err_code;

//    switch (pin_no)
//    {
//        case LEDBUTTON_BUTTON_PIN:
//            err_code = ble_lbs_on_button_change(&amp;amp;m_lbs, button_action);
//            if (err_code != NRF_SUCCESS &amp;amp;&amp;amp;
//                err_code != BLE_ERROR_INVALID_CONN_HANDLE &amp;amp;&amp;amp;
//                err_code != NRF_ERROR_INVALID_STATE)
//            {
//                APP_ERROR_CHECK(err_code);
//            }
//            break;

//        default:
//            APP_ERROR_HANDLER(pin_no);
//            break;
//    }
//}


/**@brief Function for initializing the button handler module.
 */
//static void buttons_init(void)
//{
//    uint32_t err_code;

//    //The array must be static because a pointer to it will be saved in the button handler module.
//    static app_button_cfg_t buttons[] =
//    {
//        {LEDBUTTON_BUTTON_PIN, false, BUTTON_PULL, button_event_handler}
//    };

//    err_code = app_button_init(buttons, sizeof(buttons) / sizeof(buttons[0]),
//                               BUTTON_DETECTION_DELAY);
//    APP_ERROR_CHECK(err_code);
//}


/**@brief Function for the Power Manager.
 */
static void power_manage(void)
{
    uint32_t err_code = sd_app_evt_wait();

    APP_ERROR_CHECK(err_code);
}


/**@brief Function for application main entry.
 */
int main(void)
{
    bool erase_bonds;
	
		// Initialize.
    leds_init();
    timers_init();
    //buttons_init();
    ble_stack_init();
    gap_params_init();
    services_init();
    advertising_init();
    conn_params_init();
		device_manager_init(erase_bonds);
    // Start execution.
    advertising_start();

    // Enter main loop.
    for (;;)
    {
        power_manage();
    }
}


/**
 * @}
 */
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208750?ContentTypeID=1</link><pubDate>Mon, 09 Sep 2019 15:36:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5c64b5b9-6d4d-4696-9217-cbbf1899c007</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Have you try to follow this ?&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v11.0.0/bledfu_appextending.html?cp=5_5_10_4_2_3_2_1"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v11.0.0/bledfu_appextending.html?cp=5_5_10_4_2_3_2_1&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208747?ContentTypeID=1</link><pubDate>Mon, 09 Sep 2019 15:22:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c1ba49f9-2fe4-44d5-b927-594f6313bee4</guid><dc:creator>Geek</dc:creator><description>&lt;p&gt;Thanks for replay,&lt;/p&gt;
&lt;p&gt;Now i would like to extend my application to support DFU, So i would like to know how/where should i modifiy source files to add DFU to my application. It&amp;#39;s not clear on infocenter documentation.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU stop advertising after updating new firmware</title><link>https://devzone.nordicsemi.com/thread/208616?ContentTypeID=1</link><pubDate>Mon, 09 Sep 2019 09:13:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c981037-99fa-4989-8fbb-4c151a9671a9</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When your application is running, your bootloader can&amp;#39;t run. You can&amp;#39;t run 2 application at the same time. What you need is to implement a service in the application to switch to bootloader, that what we called buttonless DFU.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you are using SDK v11, please have a look here:&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v11.0.0/bledfu_application.html?cp=5_5_10_4_2_3_2"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v11.0.0/bledfu_application.html?cp=5_5_10_4_2_3_2&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The example is inside the _with_dfu projects inside&amp;nbsp;\examples\ble_peripheral\ble_app_hrs&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>