<?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>Mesh DFU bootloader replied error 84 78 85</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/76755/mesh-dfu-bootloader-replied-error-84-78-85</link><description>Hi, 
 Device FW information is as follows: SoftDevice: s113_nrf52_7.0.1_softdevice.hex bootloader: mesh_bootloader_serial_gccarmemb_nrf52832_xxAA.hex device page: device_page_nrf52832_xxAA_s113_7.0.1.hex 
 
 We want to test the single bank Mesh DFU (bootloader</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 01 Jul 2021 08:57:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/76755/mesh-dfu-bootloader-replied-error-84-78-85" /><item><title>RE: Mesh DFU bootloader replied error 84 78 85</title><link>https://devzone.nordicsemi.com/thread/318124?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 08:57:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:504db118-4d6f-4d0c-9d00-a3948d0805ce</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Frank,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Mesh DFU is not designed to have multiple DFU source at the same time. They will both relay the packets over air and will cause conflict.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Could you let me know why you want to do DFU update for both of them ? Why don&amp;#39;t you just update one of them and let the other node just passively receive the new firmware ? (that&amp;#39;s what the mesh DFU designed for, all nodes will receive the new firmware)&lt;/p&gt;
&lt;p&gt;If you do need to update them at the same time and via serial, you may want to think of having a new DFU mode that it will not relay the message. It&amp;#39;s not something designed with the mesh bootloader. Usually there is only 2 modes: only relay (when the DFU image is not for the node, it will only relay) and store and relay (when the image is for the node and it will also relay).&amp;nbsp;&lt;br /&gt;You can find this in the dfu example, inside&amp;nbsp;mesh_evt_handler() there are 2 options, one is to call&amp;nbsp;nrf_mesh_dfu_request() for store and relay, and the other is&amp;nbsp;nrf_mesh_dfu_relay()&lt;/p&gt;
&lt;p&gt;You would need to create a 3rd option that it only does store. You then need to modify the bootloader to allow this 3rd option. I don&amp;#39;t have the exact instruction on how you would do this, but you may want to have a look into&amp;nbsp;handle_data_packet() inside dfu_mesh.c file and look at how the do_relay variable is controlled. Your third option should be that you turn off the do_relay.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>