<?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>Looking To Advertise but Keep DFU Service Disabled</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/59506/looking-to-advertise-but-keep-dfu-service-disabled</link><description>Hello, 
 I&amp;#39;m working on an nRF52832 with SoftDevice v6.1.0 and SDK 15.3.0. We have made a custom application that was created from the ble_app_uart example project. We&amp;#39;ve also added the buttonless DFU (with bonding) capability to the project. I&amp;#39;m hoping</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Mar 2020 10:18:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/59506/looking-to-advertise-but-keep-dfu-service-disabled" /><item><title>RE: Looking To Advertise but Keep DFU Service Disabled</title><link>https://devzone.nordicsemi.com/thread/242058?ContentTypeID=1</link><pubDate>Fri, 27 Mar 2020 10:18:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90309e5b-2443-4ad0-8ab3-073834cf442d</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="aculverD5"]From what I&amp;#39;ve read that event gets generated when a mobile client writes 0x01 to the DFU service, correct?[/quote]
&lt;p&gt;Yes.&lt;/p&gt;
[quote user="aculverD5"]I&amp;#39;m also curious if it would be better to send an RSP code back to the connected client when we ignore the control point write? We were considering sending back&amp;nbsp;&lt;span&gt;DFU_RSP_OPERATION_FAILED. Our accompanying mobile app has also made use of the DFU library. Does it matter if we send back an RSP code or not?&lt;/span&gt;[/quote]
&lt;p&gt;It would probably be cleaner to make a new RSP code for this, something like&amp;nbsp;DFU_RSP_OPERATION_NOT_ALLOWED, and add support for that in the DFU library on the mobile&amp;nbsp;phone side as well. In any case, it is not implemented by us, so the details are up to you an how you prefer to do it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Looking To Advertise but Keep DFU Service Disabled</title><link>https://devzone.nordicsemi.com/thread/241951?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2020 17:39:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5072920-1941-4574-b0cb-89826ee99f55</guid><dc:creator>Anders</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;Thank you for the response, that makes sense. I&amp;#39;d been looking around ble_dfu_bonded.c already and saw that event.&amp;nbsp;From what I&amp;#39;ve read that event gets generated when a mobile client writes 0x01 to the DFU service, correct?&lt;/p&gt;
&lt;p&gt;I&amp;#39;m also curious if it would be better to send an RSP code back to the connected client when we ignore the control point write? We were considering sending back&amp;nbsp;&lt;span&gt;DFU_RSP_OPERATION_FAILED. Our accompanying mobile app has also made use of the DFU library. Does it matter if we send back an RSP code or not?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Looking To Advertise but Keep DFU Service Disabled</title><link>https://devzone.nordicsemi.com/thread/241927?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2020 15:40:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7181516-14c1-4be4-8155-098079c5e956</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is no support for this in the buttonless DFU service, but it should not be difficult to add. I suggest you check your flag in the handling of the&amp;nbsp;DFU_OP_ENTER_BOOTLOADER event in&amp;nbsp;ble_dfu_buttonless_on_ctrl_pt_write() in \ble_dfu_bonded.c or ble_dfu_unbonded (depending on which you use). There you could ignore commands to enter DFU mode if the peer is not&amp;nbsp;authenticated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>