<?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>NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44946/nrf52-mesh-dfu-on-sdk-coexistence</link><description>Hi everyone, 
 I&amp;#39;m currently trying to develop an application with the mesh, the uart and the DFU. 
 I&amp;#39;ve started the project with the sdk_coexistence for use the uart and the mesh, i decided to add even the BLE capabilities to make the application compatible</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 28 Mar 2019 13:31:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44946/nrf52-mesh-dfu-on-sdk-coexistence" /><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/178949?ContentTypeID=1</link><pubDate>Thu, 28 Mar 2019 13:31:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ade8afe0-c220-4842-a58c-0db45b21fb5d</guid><dc:creator>Allen96</dc:creator><description>&lt;p&gt;Hello Edvin,&lt;/p&gt;
&lt;p&gt;Thanks for your support. I fixed the problem and now i got my DFU working.&lt;/p&gt;
&lt;p&gt;I guess the problem was on the bootloader_serial that goes in conflict with the usart. At the same time i fixed some function to make them look more similar to the example and is finnaly working.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you so much for the help&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/178373?ContentTypeID=1</link><pubDate>Tue, 26 Mar 2019 13:16:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b19bb129-ba97-480a-ba80-b639f87cd96a</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Ok. So now you are getting 0 on the nrf_mesh_dfu_init() return value. That is good. I was not aware of these flash placement settings for the bootloader.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you tried to update via mesh (from another node using serial) using the dfu example? Just to see how it is supposed to work with the DFU packet and the keys and all that?&lt;/p&gt;
&lt;p&gt;Have you checked your log? Do you get any events while performing the DFU from the other node?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/178304?ContentTypeID=1</link><pubDate>Tue, 26 Mar 2019 11:21:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d101b94-c826-4c9e-9ff2-bf46b32d2358</guid><dc:creator>Allen96</dc:creator><description>&lt;p&gt;Hi Edvin,&lt;/p&gt;
&lt;p&gt;the nrf_mesh_dfu_init() is called, the result&amp;nbsp;was 0x06.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The error was due this part&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;static uint32_t dfu_cmd_handler_set(bl_if_cmd_handler_t handler)
{
    if (handler == NULL)
    {
        return NRF_ERROR_NULL;
    }
    if (BOOTLOADERADDR() == 0xFFFFFFFF)
    {
        /* No bootloader present. */
        return NRF_ERROR_NOT_SUPPORTED;
    }
    //FIXME
    NRF_LOG_INFO(&amp;quot;handler dfu %X\n&amp;quot;, handler);
    NRF_LOG_INFO(&amp;quot;flash dfu %X\n&amp;quot;, DEVICE_FLASH_END_GET());
    NRF_LOG_INFO(&amp;quot;boot dfu %X\n&amp;quot;, BOOTLOADERADDR());
    if (((uint32_t) handler &amp;gt;= DEVICE_FLASH_END_GET()) ||
        ((uint32_t) handler &amp;lt; BOOTLOADERADDR()))
    {
        /* out of bounds. */
        return NRF_ERROR_INVALID_ADDR;
    }
    m_cmd_handler = handler;
    return NRF_SUCCESS;
}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;The result of the&amp;nbsp;third if was the cause. I fixed it by changing&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In flash_placement.xml&amp;nbsp;the line 32 from&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;lt;MemorySegment&amp;nbsp;name=&amp;quot;RAM&amp;quot;&amp;nbsp;start=&amp;quot;$(RAM_PH_START)&amp;quot;&amp;nbsp;size=&amp;quot;$(RAM_PH_SIZE)&amp;quot;&amp;gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;to&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;lt;MemorySegment&amp;nbsp;name=&amp;quot;RAM&amp;quot;&amp;nbsp;start=&amp;quot;$(RAM_PH_START)&amp;quot;&amp;nbsp;size=&amp;quot;$(RAM_SIZE)&amp;quot;&amp;gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;as suggested&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/34448/mesh-dfu-dfu_cmd_handler_set-always-failing"&gt;here&lt;/a&gt;. Now the status is 0 but i still don&amp;#39;t recive the DFU.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I hope that this can help to understand what&amp;#39;s not working.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks for the help and the support&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/178096?ContentTypeID=1</link><pubDate>Mon, 25 Mar 2019 12:34:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ed3997b2-b1a5-4686-8b96-afb67618a785</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;It sounds like you are missing some parts from the dfu example. Something in initialize() or start() isn&amp;#39;t included, like it is in the dfu example. It is a bit hard to say what it is without seeing the project.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is nrf_mesh_dfu_init() called inside your nrf_mesh_init()? (And if it is, what is the return value of nrf_mesh_dfu_init()?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/178012?ContentTypeID=1</link><pubDate>Mon, 25 Mar 2019 08:36:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85703adf-568c-45f9-8382-3c2672db98b9</guid><dc:creator>Allen96</dc:creator><description>&lt;p&gt;Hi Edvin,&lt;/p&gt;
&lt;p&gt;I tried to activate the serial port as you asked me and in that case I can receive the DFU update through the serial port and this is correctly sent to the other devices.&lt;/p&gt;
&lt;p&gt;For this reason I really believe that the bootloader that the device page is correct, always loaded as the example describe.&lt;br /&gt;When I try to receive the DFU instead through another device I get nothing.&lt;/p&gt;
&lt;p&gt;None of the events you asked for are received.&lt;/p&gt;
&lt;p&gt;Thanks for the help&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/177621?ContentTypeID=1</link><pubDate>Thu, 21 Mar 2019 14:24:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f979ee7-64ae-41c6-943b-6c9f79acc25b</guid><dc:creator>Allen96</dc:creator><description>&lt;p&gt;Dear Edvin,&lt;/p&gt;
&lt;p&gt;Thank you very much for what you did. At the moment I am in London so I cannot control the code right now but I will keep you fully informed as soon as possible. So far I can only tell you that I don&amp;#39;t receive any event linked to the DFU, whereas I receive all of those linked to the MESH.&lt;/p&gt;
&lt;p&gt;Thank you and have a good day,&lt;/p&gt;
&lt;p&gt;Alessandro Mattioli&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 Mesh DFU on sdk coexistence</title><link>https://devzone.nordicsemi.com/thread/176725?ContentTypeID=1</link><pubDate>Mon, 18 Mar 2019 13:18:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d29548b-17bb-40e1-8bba-4ae549c1e926</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Is &amp;quot;LOG_SRC_DFU&amp;quot; part of your __LOG_INIT() arguments?&lt;/p&gt;
&lt;p&gt;Do you get any of the other Mesh DFU events in the mesh_evt_handler()?&lt;/p&gt;
&lt;p&gt;NRF_MESH_EVT_DFU_FIRMWARE_OUTDATED, &lt;br /&gt;NRF_MESH_EVT_DFU_FIMRWARE_OUTDATED_NO_AUTH,&lt;br /&gt;NRF_MESH_EVT_DFU_END (probably not this one, if you don&amp;#39;t get &amp;quot;start&amp;quot;.&lt;br /&gt;NRF_MESH_EVT_DFU_BANK_AVAILABLE&lt;/p&gt;
&lt;p&gt;Any of them?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Have you programmed the bootloader and device page as in the dfu example?&lt;/p&gt;
&lt;p&gt;I understand that you don&amp;#39;t want the serial part in the end, but can you try to enable the serial part, and see if you then receive the DFU image over Mesh when you start the transmission via serial on another board?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>