<?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 on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7376/dfu-on-nrf-master-control-panel-andriod-version</link><description>Dear all. 
 I have some test result on DFU feature. Please any comment on this issue. 
 test condition 
 
 
 Mater control panel (64-bit version) 
 
 
 nRFgo studio (64-bit version) : 1.19.0.7 
 
 
 Smart Beacon Kit : PCA20006 
 
 
 Pre</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Jun 2015 08:19:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7376/dfu-on-nrf-master-control-panel-andriod-version" /><item><title>RE: DFU on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/thread/26207?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 08:19:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a086c27-f9bf-4fb1-b038-0ef23605802c</guid><dc:creator>Aleksander Nowakowski</dc:creator><description>&lt;p&gt;Hi, the Error 0x85 (error 133) happens occasionally sometimes. Also, I think, it may happen when the device is not reachable. If you are dealing with the DFU bootloader from SDK 8+ you should remember that the DFU advertises with an address incremented by 1 when entered with a button (not the buttonless DFU) or in case the softdevice was updated (as it removes the app). This causes a situation when you may send the SD+BL to a device with normal address (when the buttonless update was used) and then an application to a device with address incremented. This issue has been fixed in the new releases of all the Android apps. But it only applies to a situation when you flash SD+BL+App in a single ZIP file after using buttonless update.&lt;/p&gt;
&lt;p&gt;If you want to verify the CRC the best way is to use the nrf utility tool. I gave a link to some documentation above.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/thread/26205?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 08:10:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f86d500b-642b-432f-bd3d-8fbb81ea9c6c</guid><dc:creator>Aleksander Nowakowski</dc:creator><description>&lt;p&gt;Hi, all Android apps (nRF MCP, Toolbox and Beacon) support all features of DFU. You should be able to update only softdevice or only bootloader using the hex file (with providing .dat file, if required by the bootloader). You should also be able to update softdevice and bootloader by putting them to a ZIP file and naminig the files softdevice.hex, bootloader.hex (and optionally system.dat with the init packet for combined files). However, as Hung said, we now recommend you to use the nrf.exe tool from the PC version on Master Control Panel. I have written some documentation how to do that here: &lt;a href="https://github.com/NordicSemiconductor/nRF-Master-Control-Panel/tree/master/init%20packet%20handling"&gt;github.com/.../init packet handling&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/thread/26206?ContentTypeID=1</link><pubDate>Wed, 10 Jun 2015 15:00:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13d1c32f-7a5c-4212-8210-471dc5d33c99</guid><dc:creator>oceanide</dc:creator><description>&lt;p&gt;@Hung Bui&lt;/p&gt;
&lt;p&gt;When I tried to use your bootloader hex file, it looks like bootloader downloading is done successfully. But, I got a error message as &amp;quot;Error (0x85): GATT ERROR&amp;quot;, so I attached a log file.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/6366.log.txt"&gt;log.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When I pressed a button to enter DFU mode again, I never entered into DFU mode and just stayed in normal beacon mode.&lt;/p&gt;
&lt;p&gt;Could you please .dat file for all pre-compiled binaries (softdevice, bootloader, application) of beacon v1.1?   I would like to compare if my .dat files are correct or not.&lt;/p&gt;
&lt;p&gt;Thanks in advance&lt;/p&gt;
&lt;p&gt;oceanide&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/thread/26204?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2015 14:44:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f779abe-5890-42fe-ba96-43542c7745e1</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Oceanide: Have you make sure you have included the .dat file after you select the .hex file ?&lt;/p&gt;
&lt;p&gt;How did you generate the .dat file ?&lt;/p&gt;
&lt;p&gt;You should use nrf.exe tool to generate the .zip file and then unzip, take out the .dat file inside the zip.&lt;/p&gt;
&lt;p&gt;Init file is required on the bootloader for Beacon v1.1 (equivalent to the DFU on SDK v7.1 for nRF51)
I attached in my answer the bootloader.hex and bootloader.dat that you can try.&lt;/p&gt;
&lt;p&gt;I tested here and got no problem to update the bootloader with nRF Master Control Panel on Android .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/thread/26203?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2015 10:37:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:99fd22fe-7214-43e9-85dc-1fbf7066b917</guid><dc:creator>oceanide</dc:creator><description>&lt;p&gt;Thank you for response.&lt;/p&gt;
&lt;p&gt;I did not used .zip file with Master control panel.
I tried to use each hex file to update softdevice, bootloader and application binary.&lt;/p&gt;
&lt;p&gt;Using nRFToolbox, I also tried to update with  each hex binary, but I got failed.&lt;/p&gt;
&lt;p&gt;I just want to know if softdevice and bootloader files can update with master control panel(android version) using each hex files, not .zip file.&lt;/p&gt;
&lt;p&gt;Thanks in advance&lt;/p&gt;
&lt;p&gt;oceanide&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU on nRF Master Control Panel (andriod version)</title><link>https://devzone.nordicsemi.com/thread/26202?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2015 07:32:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:646fa729-0066-46be-884d-d7dd4c83c81b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Oceanide: I&amp;#39;m sorry indeed for the late response.&lt;/p&gt;
&lt;p&gt;Regarding the issue, which .zip file did you use to update the softdevice and bootloader ? Could you attach them to your question?&lt;/p&gt;
&lt;p&gt;Have you tried to do DFU with nRFToolbox and nRFBeacon app  ?&lt;/p&gt;
&lt;p&gt;The nRFMaster Control Panel may not be compatible with the new .zip file standard (with .json file). We are releasing a new version of the Master Control Panel in the next few days.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3872.bootloader.hex"&gt;bootloader.hex&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/bootloader.dat"&gt;bootloader.dat&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>