<?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>Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91664/nrfutil-dfu-over-ble-causes-ble-device-to-disconnect</link><description>I am using bleak and python to connect to a ble device and then using subprocess to run the dfu. The ble device disconnects when the dfu starts and then I get &amp;quot;Connection Failure - Device not found&amp;quot; error. I am using the nrf52833 board as a connectivity</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 08 Sep 2022 08:16:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91664/nrfutil-dfu-over-ble-causes-ble-device-to-disconnect" /><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/385187?ContentTypeID=1</link><pubDate>Thu, 08 Sep 2022 08:16:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60cf992b-a34c-4ca0-a232-e9c5081d1f06</guid><dc:creator>Einar Thorsrud</dc:creator><description>[quote user="cheeetoo"]The endianness definitely isn&amp;#39;t the problem because I am using the same address to connect to the device.[/quote]
&lt;p&gt;Using nrfutil? If not, it would make sense to spend extra 10 seconds to swap the address manually just to double-check.&lt;/p&gt;
&lt;p&gt;The error &amp;quot;Connection Failure - Device not found&amp;quot; is printed&amp;nbsp;only when a connection failed to be established (see how &lt;a href="https://github.com/NordicSemiconductor/pc-nrfutil/blob/f4a51acc196ae779785bb96b92229cebae0f03ce/nordicsemi/dfu/dfu_transport_ble.py#L232"&gt;verify_stable_connection()&lt;/a&gt;&amp;nbsp;is implemented and used), so there is some reason the connection is never established. The typical reasons for that are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The specified address (if any) is wrong&lt;/li&gt;
&lt;li&gt;The&amp;nbsp;specified name (if any) is wrong&lt;/li&gt;
&lt;li&gt;The device is not advertising / not connectable&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I cannot say much more at this point, but as mentioned, I would think it would be useful to see the device advertising in for instance nRF Connect Bluetooth, as that would give us some key information (first of all that it really is advertising and the address).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/385131?ContentTypeID=1</link><pubDate>Thu, 08 Sep 2022 00:49:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81e5e69c-f294-4b37-99a9-4ea9805c3bb3</guid><dc:creator>cheeetoo</dc:creator><description>&lt;p&gt;The endianness definitely isn&amp;#39;t the problem because I am using the same address to connect to the device. Also I should probably mention that I am not getting an error, it shows a status bar at 0% and then the device disconnects and my program hangs for a second and then crashes.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/384916?ContentTypeID=1</link><pubDate>Wed, 07 Sep 2022 06:46:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d32fdd6e-58ff-4d6b-91df-0014c4d65d5b</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;I don&amp;#39;t have experience with bleak, but&amp;nbsp;different tools can show the address with different endianness. Can you try to swap the endianness and see if that helps?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/384888?ContentTypeID=1</link><pubDate>Wed, 07 Sep 2022 01:37:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93a6df0f-1f3f-444d-af36-a86c2c1533e3</guid><dc:creator>cheeetoo</dc:creator><description>&lt;p&gt;The command I am using is &amp;quot;nrfutil dfu ble -ic NRF52 -pkg /home/finn/Downloads/firmware.zip -p /dev/ttyACM0 -a {d.address} -f&amp;#39;. {d.address} is the address of the device provided by bleak.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/384838?ContentTypeID=1</link><pubDate>Tue, 06 Sep 2022 15:15:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca67b1ee-8e13-44c9-828d-3d10023a7584</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Can you show the full command you are using, and perhaps also a screenshot of the device seen from nRF Connect for&amp;nbsp;Desktop Bluetooth, so that I can see both the name and BT address of the device you are trying to update?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/384823?ContentTypeID=1</link><pubDate>Tue, 06 Sep 2022 13:49:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93f8a2ea-fd4d-429c-94f9-70194a664f81</guid><dc:creator>cheeetoo</dc:creator><description>&lt;p&gt;Yes, I have tried specifying both and I get the same result.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrfutil dfu over ble causes ble device to disconnect</title><link>https://devzone.nordicsemi.com/thread/384809?ContentTypeID=1</link><pubDate>Tue, 06 Sep 2022 13:24:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0de659f2-0f7f-4e85-a106-c8a175272feb</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;That error indicates that the device (which is in bootloader mode) is not found. Have you specified a name (using the -n option) or an address (using the -a option), and double checked that it is correct?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>