<?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>Workflow for DFU via BLE on Windows</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97501/workflow-for-dfu-via-ble-on-windows</link><description>Hi 
 I&amp;#39;m using an nRF52840 with Zephyr and nRF Connect SDK v2.1.0. 
 I can update my device with the nRF Connect App on my smartphone. On Windows however, I had no luck so far. Has someone a workflow for that? What I tried: 
 
 nrfutil.exe (in combination</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 Mar 2023 12:08:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97501/workflow-for-dfu-via-ble-on-windows" /><item><title>RE: Workflow for DFU via BLE on Windows</title><link>https://devzone.nordicsemi.com/thread/414360?ContentTypeID=1</link><pubDate>Thu, 09 Mar 2023 12:08:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2c2943f-6a78-408e-b884-ce7488a1bf78</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi again. I missed your question a bit and I apologize for the confusion.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;1. The nRF Util for nRF5 SDK only supported dfu created by nRF5 SDK and not a project created by nRF Connect SDK&lt;/p&gt;
&lt;p&gt;2 &amp;amp; 3. Currently FOTA is not supported in windows and you will have to use either linux, osx, or android/iOS&amp;nbsp;&lt;/p&gt;
&lt;p&gt;One alternativ for linux would be to look into MCUmgr-cli&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/device_mgmt/mcumgr.html"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/device_mgmt/mcumgr.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Workflow for DFU via BLE on Windows</title><link>https://devzone.nordicsemi.com/thread/414313?ContentTypeID=1</link><pubDate>Thu, 09 Mar 2023 09:16:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d1aa3a1-e796-4389-a494-cc529a2031c6</guid><dc:creator>giz</dc:creator><description>&lt;p&gt;Hi Runar,&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;VSCode generates dfu_application.zip in the build folder. Are you saying this is the file that&amp;#39;s actually supposed to be used with nrfutil? What do I need to change in my setup for it to work? nrfutil complains with the following error when trying to update with this file:&lt;/p&gt;
&lt;p&gt;KeyError: &amp;#39;manifest&amp;#39;&lt;/p&gt;
&lt;p&gt;When generating the package file &amp;#39;manually&amp;#39;, the manifest in the zip file is different. By manual, I mean I created the package file using nrfutil. I&amp;#39;m confused with what this package file actually needs to contain, so I wouldn&amp;#39;t be surprised if what I tried for testing is wrong:&lt;/p&gt;
&lt;p&gt;nrfutil pkg generate --hw-version 52 --sd-req 0x123 --application-version 4 --application app_signed.hex dfu.zip&lt;/p&gt;
&lt;p&gt;I would really appreciate if VSCode would just output the correct file without me having to dig into this.&lt;/p&gt;
&lt;p&gt;Regarding the dongle, yes, I&amp;#39;ve put it into bootloader mode before programming. My device connects, it lists all my services and I evencan read/write my characteristics. So I&amp;nbsp;assume the dongle is correctly programmed?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Workflow for DFU via BLE on Windows</title><link>https://devzone.nordicsemi.com/thread/414296?ContentTypeID=1</link><pubDate>Thu, 09 Mar 2023 08:34:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:802a485e-5850-4244-8c9b-1ad3c97a8f0e</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;1. I will need to look into this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you managed to create the dfu_application.zip from Vscode? Here is an overview over different output files and their use&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/app_dev/build_and_config_system/index.html#mcuboot-output-build-files"&gt;developer.nordicsemi.com/.../index.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;2. I will need to look into this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;3. Did you follow the procedure as written her:&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf52840_dongle%2FUG%2Fnrf52840_Dongle%2Fprogramming.html"&gt;https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf52840_dongle%2FUG%2Fnrf52840_Dongle%2Fprogramming.html&lt;/a&gt;&amp;nbsp;to set the dongle in bootloader mode before trying to program it using the nRF Connect for Desktop Programmer?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>