<?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 fails with &amp;quot;Verification failed (Code = 12)&amp;quot; (vs. NRF_SDH_BLE_... parameters?)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97755/dfu-fails-with-verification-failed-code-12-vs-nrf_sdh_ble_-parameters</link><description>Hello, 
 I am developing a peripheral device, DFU is added long time ago and it worked well and stable (I use the slightly modified buttonless bootloader example). Suddenly I am facing to the issue that DFU fails with &amp;quot;Verification failed (Code = 12)</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 17 Mar 2023 07:02:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97755/dfu-fails-with-verification-failed-code-12-vs-nrf_sdh_ble_-parameters" /><item><title>RE: DFU fails with "Verification failed (Code = 12)" (vs. NRF_SDH_BLE_... parameters?)</title><link>https://devzone.nordicsemi.com/thread/415878?ContentTypeID=1</link><pubDate>Fri, 17 Mar 2023 07:02:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6337af1d-9e6a-4115-8699-1769fef2429d</guid><dc:creator>a14523</dc:creator><description>&lt;p&gt;Hello Vidar,&lt;br /&gt;&lt;br /&gt;thank you for your answer. So, this is a bit embarrassing... I recognised it just now that in my nRF connect app the automatically request of maximum MTU (517bytes) is set. If I remove this option, the issue is gone. DFU is successful at the first try from the application.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU fails with "Verification failed (Code = 12)" (vs. NRF_SDH_BLE_... parameters?)</title><link>https://devzone.nordicsemi.com/thread/415632?ContentTypeID=1</link><pubDate>Thu, 16 Mar 2023 09:05:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad073fea-6cb6-4b89-ad7f-7efacbfc557b</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I strongly recommend you use the default connection settings. DFU throughput is not only about the BLE transfer speed, but&amp;nbsp;also scheduling of the flash operations&amp;nbsp;(&lt;a title="Flash memory API" href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/flash_mem_api/flash_mem_api.html?cp=5_7_4_0_7"&gt;Flash memory API&lt;/a&gt;). If you increase the BLE throughput too much, it will have a negative impact on the overall DFU speed, or worst case, cause DFU to always fail.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The default paramaters have been optimized for throughput, and you should be able to reach up to 10 kB/s with the right phone.&amp;nbsp;&lt;/p&gt;
[quote user=""] (27, 23, 6) [/quote]
&lt;p&gt;The default MTU should be 247, not 23. And the data length is always limited to 27 when using s112 (data length has little to no impact on dfu speed anyway).&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>