<?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>Request to enter bootloader mode failed asynchronously.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42828/request-to-enter-bootloader-mode-failed-asynchronously</link><description>I was working with the buttonless DFU service that requires bonds and I was able to update my firmware just fine. Then I added Just Works OOB pairing using the nfc_ble_pair_lib. Now whenever the DFU characteristic is written, I receive the &amp;quot; Request to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 Jan 2019 17:26:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42828/request-to-enter-bootloader-mode-failed-asynchronously" /><item><title>RE: Request to enter bootloader mode failed asynchronously.</title><link>https://devzone.nordicsemi.com/thread/167453?ContentTypeID=1</link><pubDate>Wed, 23 Jan 2019 17:26:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:256a7c55-30b0-4d2f-896a-b75f6f27979a</guid><dc:creator>Jonathan</dc:creator><description>&lt;p&gt;&lt;span&gt;Setting #define NRF_SDH_BLE_SERVICE_CHANGED 1 Fixed this issue. The phone needed to be turned off and on again in order to completely erase the cache. forgetting the bluetooth device did not do this on it&amp;#39;s own.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Request to enter bootloader mode failed asynchronously.</title><link>https://devzone.nordicsemi.com/thread/167449?ContentTypeID=1</link><pubDate>Wed, 23 Jan 2019 17:12:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef20a943-b133-4798-8f18-2f9e58297e61</guid><dc:creator>Jonathan</dc:creator><description>&lt;p&gt;Somehow I didn&amp;#39;t have this set:&lt;br /&gt;NRF_SDH_BLE_SERVICE_CHANGED 1&lt;br /&gt;&lt;br /&gt;However now, I am getting&lt;br /&gt;&amp;quot;Enabling indications failed&amp;quot;&lt;br /&gt;When trying to perform a bonded DFU.&lt;br /&gt;&lt;br /&gt;I also can not enable indications on the DFU characteristic manually via the LightBlue GATT client app&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Request to enter bootloader mode failed asynchronously.</title><link>https://devzone.nordicsemi.com/thread/167305?ContentTypeID=1</link><pubDate>Wed, 23 Jan 2019 09:46:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1756418-2d19-4b9c-aa90-4660fc1214af</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi Jonathan,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;which nRF52 IC are you using? Also which SDK version and SoftDevice are you using?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I took a look in SDK v15.0.0 and the buttonless DFU example prints&amp;nbsp;&lt;/p&gt;
&lt;p&gt;NRF_LOG_ERROR(&amp;quot;Request to enter bootloader mode failed asynchroneously.&amp;quot;);&lt;/p&gt;
&lt;p&gt;when the&amp;nbsp;BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED event is passed by the&amp;nbsp;Buttonless Secure DFU service.&amp;nbsp; This event is generated in either ble_dfu.c or ble_dfu_bonded.c.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In&amp;nbsp;&lt;span&gt;ble_dfu.c the&amp;nbsp;BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED&amp;nbsp; is returned at one location&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;If&amp;nbsp;ble_dfu_buttonless_bootloader_start_prepare() at line 194 in&amp;nbsp;on_hvc() ruturns a non-zero error code, i.e. not NRF_SUCESS.&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In&amp;nbsp;ble_dfu_bonded.c.&amp;nbsp;BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED&amp;nbsp;&amp;nbsp;is passed to the event handler at four locations,&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;If&amp;nbsp;ble_dfu_buttonless_bootloader_start_finalize() returns a non-zero error code when the&amp;nbsp;PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event is processed in&amp;nbsp;pm_evt_handler()&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;If&amp;nbsp;ble_dfu_buttonless_bootloader_start_finalize&amp;nbsp;returns a non-zero error code when the PM_EVT_PEER_DATA_UPDATE_FAILED event is processed in&amp;nbsp;pm_evt_handler()&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;If ble_dfu_buttonless_resp_send at line 266 returns a non-zero error code&amp;nbsp;in ble_dfu_buttonless_on_sys_evt()&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;If&lt;span&gt;&amp;nbsp;&lt;/span&gt;ble_dfu_buttonless_resp_send at line 358 returns a non-zero error code&amp;nbsp;in&lt;span&gt; ble_dfu_buttonless_on_ctrl_pt_write&lt;/span&gt;()&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;Can you please place a breakpoint at these 5 locations and see which one is triggered?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards&lt;br /&gt;Bjørn&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>