https://devzone.nordicsemi.com/f/nordic-q-a/43229/mesh-sdk-v3-1-0-with-buttonless-dfu-exampleHi guys, hope all is well. I was hoping someone could help me out with this particular issue. Maybe someone on here has tried to do the same thing. Just some background about my test setup: Using 2x nRF52840&#39;s, custom hardware. One is the clienten-USTelligent Community 13Thu, 07 Feb 2019 21:13:14 GMThttps://devzone.nordicsemi.com/thread/170022?ContentTypeID=1Thu, 07 Feb 2019 21:13:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7d5bb86e-5482-47c8-a530-49755acd64e8gordie<p>Hi thanks for the reply. I tried the bootloader DFU that is integrated into some of the mesh examples. Seems to work the same, minus the problem I described. So I will just use that. Thanks again for the help.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/169954?ContentTypeID=1Thu, 07 Feb 2019 14:21:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f7ab96ca-286e-4d61-ad21-946a40237849Mttrinh<p>Hi,</p> <p>I think it is fine using the workaround you come up it.</p> <p>The bootloader DFU, supported in the Mesh DFU,&nbsp;<span>the application is not running, and the bootloader takes care of the transfer. This mode is primarily meant as a fallback mechanism, in case the application malfunctions. The Mesh DFU also supports side-by-side DFU which&nbsp;transfers the new firmware in the background while the application is running and reports to the application when the transfer is done.</span></p><div style="clear:both;"></div>