<?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>Booting Mesh-Application from BLE secure Booltoader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41844/booting-mesh-application-from-ble-secure-booltoader</link><description>Dear Support, 
 I am working now on the PCA10040 Development-Board, I use the Booltoader from the nRF5_SDK_15.0.0 and the application from the nrf5_SDK_for_Mesh_v2.2.0. I had programmen a secure bootloader from the nonMesh-SDK and tested it with nonMesh</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 21 Dec 2018 14:56:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41844/booting-mesh-application-from-ble-secure-booltoader" /><item><title>RE: Booting Mesh-Application from BLE secure Booltoader</title><link>https://devzone.nordicsemi.com/thread/162877?ContentTypeID=1</link><pubDate>Fri, 21 Dec 2018 14:56:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c687ffd2-fa0e-4618-8fad-0d11a2c6dc61</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Roland,&lt;/p&gt;
&lt;p&gt;I just did a test with the light_switch\proxy_server example, where I created a DFU image with this, and used the secure_bootloader from SDK15.0.0, and it worked on my computer. I didn&amp;#39;t do any changes to either the bootloader or the Mesh example.&lt;/p&gt;
&lt;p&gt;Can you describe how you created the DFU image, and how you transferred it?&lt;/p&gt;
&lt;p&gt;Are you sure that it is not running? The mesh examples doesn&amp;#39;t necessarily use the LEDs, but I could see the RTT output that the example was running.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Booting Mesh-Application from BLE secure Booltoader</title><link>https://devzone.nordicsemi.com/thread/162875?ContentTypeID=1</link><pubDate>Fri, 21 Dec 2018 14:48:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67d792bc-4c55-416e-b90c-842e771d82a2</guid><dc:creator>Andre</dc:creator><description>&lt;p&gt;I have encountered this problem before. The problem lies in the fact the mesh sdk assumes the mesh bootloader being present, and calls into it during initialisation, which is not supported by the BLE bootloader. The solution is to comment out the lines where this happens. in&amp;nbsp;core/src/nrf_mesh.c there is a call to&amp;nbsp;nrf_mesh_dfu_init(). (in nrf_mesh_init() , line 360) Comment that out, and then it should work fine with the BLE bootloader.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>