• State Not Answered
  • Replies 38 replies
  • Subscribers 63 subscribers
  • Views 5560 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 267355
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

OTA Thread DFU: Merge SDK example with custom application

AS_Kalpa

Hi all!

I'm able to fully test the SDK example https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v3.2.0%2Fthread_example_dfu.html and it works pretty well.

Now, the next step is the integration of this OTA DFU over Thread example in my custom application (that already exploits Thread and MQTT-SN protocol).

I haven't found a tutorial that explains step-by-step this kind of operation. 

Basically I need some help to integrate the DFU client with the user application. I think the key point is the IoT SDK CoAP library that implement a DFU algorithm that should run concurrently to the user application, but I'm a bit confused about merging process.

Thanks in advance,

Alessio

Parents
  • 0

    Hi,

    I'm not aware of any tutorials describing this exact process, but it should basically be a matter of merging the code, add relevant source files/header paths, and required sdk_config.h configurations from one project to the other.

    If you are using MQTT-SN and not CoAP in your main application, it should not cause major issues when merging with the OTA Client. If you had been using CoAP, you would face a bigger task, as the OTA Client usese the IoT CoAP library, while the Thread applications uses the built-in CoAP library in OpenThread. This would require you to port the CoAP applications to the IoT CoAP library, but this is not required with MQTT-SN.

    I would recommend you to start out with merging your applications. If you are facing any issues or problems, please post the issues here and we will help you resolve it.

    Best regards,
    Jørgen

  • 0 in reply to Jørgen Holmefjord
    AS_Kalpa said:
    In my custom application I use the SoftDevice s140, does I need to insert the parts related to MBR? If i get well, those parts are there cause DFU example doesn't use SD but only MBR. Am I missing something?

    You need to include all sections, both in the flash_placements.xml file, and in the Memory Segments parameter in the project options.

    The softdevice includes the MBR, so it is present in both applications. MBR settings page is used to allow secure updates of the bootloader, and is required by all DFU examples.

Reply
  • 0 in reply to Jørgen Holmefjord
    AS_Kalpa said:
    In my custom application I use the SoftDevice s140, does I need to insert the parts related to MBR? If i get well, those parts are there cause DFU example doesn't use SD but only MBR. Am I missing something?

    You need to include all sections, both in the flash_placements.xml file, and in the Memory Segments parameter in the project options.

    The softdevice includes the MBR, so it is present in both applications. MBR settings page is used to allow secure updates of the bootloader, and is required by all DFU examples.

Children
Related