<?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>Bluetooth Mesh Light Switch Example Provisioner DFU implementation fail.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/35880/bluetooth-mesh-light-switch-example-provisioner-dfu-implementation-fail</link><description>Hello 
 I am working on a project based on the Mesh SDK 2.0.1 light_switch example. The system is using SD 6.0.0 and PCA10040 boards. DFU is successfully implemented on the servers(which are running as dual client/servers) with no serial support. 
 The</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 28 Jun 2018 13:40:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/35880/bluetooth-mesh-light-switch-example-provisioner-dfu-implementation-fail" /><item><title>RE: Bluetooth Mesh Light Switch Example Provisioner DFU implementation fail.</title><link>https://devzone.nordicsemi.com/thread/138149?ContentTypeID=1</link><pubDate>Thu, 28 Jun 2018 13:40:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:45e46447-3c8f-4903-9e03-d294a01c4a3f</guid><dc:creator>Martin</dc:creator><description>&lt;p&gt;This solved it. By moving the flash area used by dsm by defining&amp;nbsp;DSM_FLASH_AREA_LOCATION in device_state_manager.c and setting it outside of the area of the bootloader the assert problem dissappeared. The serial problem was solved by removing the call to&amp;nbsp;&lt;span&gt;nrf_mesh_evt_handler_add. It&amp;#39;s currently in test but it looks promising.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth Mesh Light Switch Example Provisioner DFU implementation fail.</title><link>https://devzone.nordicsemi.com/thread/138088?ContentTypeID=1</link><pubDate>Thu, 28 Jun 2018 11:28:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:62270fd6-6683-4327-99f3-5040c8b638e5</guid><dc:creator>Trond Einar Snekvik</dc:creator><description>&lt;p&gt;Hi Martin,&lt;/p&gt;
&lt;p&gt;The first issue is caused by a limitation in the serial driver in the mesh, that makes it lock up when the host doesn&amp;#39;t pop its outgoing packets. See the note in step 8 of &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v2.0.1/md_doc_getting_started_dfu_quick_start.html?cp=4_1_0_3_2"&gt;the DFU quickstart guide&lt;/a&gt;. Only enable the serial module for devices that are actively communicating with the host.&amp;nbsp;You can also remove the call to nrf_mesh_evt_handler_add in serial_handler_mesh_init() in serial_handler_mesh.c, if you only want the DFU module to push events to serial.&lt;/p&gt;
&lt;p&gt;I believe the second problem happens because you&amp;#39;ve got other stuff in your flash&amp;nbsp;manager regions. If you&amp;#39;re adding your own flash manager before this mesh_stack_init call, that might be it, otherwise, check your flash configuration, and see if your app, bootloader or softdevice is using the same flash page for something else.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>