<?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 Bootloader Data Request Handling Issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/53003/mesh-bootloader-data-request-handling-issue</link><description>I&amp;#39;ve been doing some testing with Mesh DFU and I&amp;#39;ve noticed some unexpected behavior around handling missing data segments. 
 As I understand the Mesh DFU protocol, if a data segment is found to be missing, then the nRF chip is supposed to continuously</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 01 Nov 2019 06:19:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/53003/mesh-bootloader-data-request-handling-issue" /><item><title>RE: Mesh Bootloader Data Request Handling Issue</title><link>https://devzone.nordicsemi.com/thread/217876?ContentTypeID=1</link><pubDate>Fri, 01 Nov 2019 06:19:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4d16ea9-6123-4f3f-966a-f35f9f1afd98</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Some information from our developers:&amp;nbsp;&lt;br /&gt;You can find the changes for the behavior here:&amp;nbsp;&lt;br /&gt;&lt;a href="https://github.com/NordicPlayground/nRF51-ble-bcast-mesh/commit/ed93bfb2619d1e272fc3866dbe15fda03d8fbe67"&gt;https://github.com/NordicPlayground/nRF51-ble-bcast-mesh/commit/ed93bfb2619d1e272fc3866dbe15fda03d8fbe67&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This was made a long time ago, but one of the reasons could be to reduce the flooding in the network. One suggestion could be to play with REQ_RX_COUNT_RETRY and see if it still causes the DFU to stall.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Another possible issue here might be that DFU stalls at the end of the DFU process, so that the target will never receive segments higher than the last requested missing segment, because it has already received the last segment. We will do some additional investigation to check if this actually happens so that we can provide a patch for it.&amp;nbsp;&lt;br /&gt;You could also try to check if this actually happens, for example by checking if the target has received the last segment (which is equal to m_transaction.segment_count) and if so, unconditionally request all the rest missing packets.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim Jakobsen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Bootloader Data Request Handling Issue</title><link>https://devzone.nordicsemi.com/thread/217086?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2019 13:12:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a254d63e-b5d0-46c5-9369-a2cbe43186f2</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;When looking at the progress on the internal report I couldn&amp;#39;t track down my report.&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know what happened, but I&amp;#39;ve created a new bug-report for the Mesh team.&lt;/p&gt;
&lt;p&gt;Will update you as soon as I have any more information.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Sorry about the inconvenience. &lt;br /&gt;Best regards, &lt;br /&gt;Joakim &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Bootloader Data Request Handling Issue</title><link>https://devzone.nordicsemi.com/thread/216708?ContentTypeID=1</link><pubDate>Thu, 24 Oct 2019 23:33:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85f27bdd-77d2-42f2-a7e5-31127d3c57b6</guid><dc:creator>Thomas-Brilliant</dc:creator><description>&lt;p&gt;Hi Joakim,&lt;/p&gt;
&lt;p&gt;Any updates on this bug?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Bootloader Data Request Handling Issue</title><link>https://devzone.nordicsemi.com/thread/214867?ContentTypeID=1</link><pubDate>Mon, 14 Oct 2019 13:29:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c761e7e-eb29-4f0f-8378-710a513b51fc</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi again!&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks for your feedback. One of our developers looked at this, and it seems to be a bug.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve created an internal bug-report for this and I&amp;#39;ll update you with&amp;nbsp; any updates from our developers.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Bootloader Data Request Handling Issue</title><link>https://devzone.nordicsemi.com/thread/213880?ContentTypeID=1</link><pubDate>Tue, 08 Oct 2019 11:22:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:20e5666c-b680-4ffc-8ef4-8261793c0495</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll need to send a request internally to have someone with more knowledge about the bootloader take a look at this.&lt;/p&gt;
&lt;p&gt;Let me get back to you when I have any more information.&lt;/p&gt;
&lt;p&gt;Best regards, &lt;br /&gt;Joakim Jakobsen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>