<?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>DFU works via Master Control Panel but not via nRF Toolbox</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9968/dfu-works-via-master-control-panel-but-not-via-nrf-toolbox</link><description>Hello all, 
 I am working on the implementation of DFU OTA in our application, running on a custom board using the nRF51822-QFAC. 
 The tools that I am using are: 
 
 SDK 7.2.0 
 Keil uVision V5.15 
 Softdevice S110 7.1.0 
 nRFgo Studio 1.21.0</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 Oct 2015 14:20:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9968/dfu-works-via-master-control-panel-but-not-via-nrf-toolbox" /><item><title>RE: DFU works via Master Control Panel but not via nRF Toolbox</title><link>https://devzone.nordicsemi.com/thread/36986?ContentTypeID=1</link><pubDate>Fri, 30 Oct 2015 14:20:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30259591-b145-45d3-9df0-785f495e3bb2</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Thank you for a very good and detailed description of your problem&lt;/p&gt;
&lt;p&gt;I generated the bootloader zip file with the same nrf dfu genpkg ... string as you and it works fine.&lt;/p&gt;
&lt;p&gt;Perhaps what is going on is that there is old bonding information residing on the phone. nRF51 SDK 7.2 bootloader does not handle that properly, as it advertises on the same GAP address as the application, making it use the same GATT table. It should work in nRF51 SDK 8.0.0+, where the bootloader advertises on a different GAP address, which results in the IOS to do a new service discovery for the bootloader and to refresh the GATT table.&lt;/p&gt;
&lt;p&gt;Check if this makes it work:
go to Settings -&amp;gt; Bloetooth on your IOS device, erase all pairing/bonding information and then turn off bluetooth and turn it on again. That should erase the old GATT table and force IOS to do a new service discovery when connecting.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>