This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

OTA DFU Thread: merge with NCP.hex

Hi all,

in my current platform I have:

  1. a DK (we are working to implement HW modifications to use a nrf52 dongle for this purpose) that is performing as a Thread DFU server (following this example https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v3.2.0%2Fthread_example_dfu.html)
  2. a nrf52 dongle that is running the NCP example under <SDK folder>/examples/thread/ncp/ftd/usb/hex

We would like to merge the two functionalities to use one single board to handle both.

Do you have any suggestions? 

I think the easiest way is to have:

  • the source code of the NCP example (SDK/examples/thread/ncp/ftd/usb/hex) 
  • the source code of the connectivity fw for Thread DFU purpose that is automatically flash by nrfutil ('-f') when you run the line:
    nrfutil dfu thread -f -pkg app_dfu_package.zip -p COMx --channel 11 --panid 43981 -r 4 -rs 5000 -a FF03::1

 so that we can merge them manually.

Is it possible? Am I missing something? Are there any issues that I'm not considering?

Thanks in advace,

Alessio

(nrfutil version: 6.1

SDK version: nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8)

  • Hello,

    Actually, the NCP example is the one being used when running the command "nrfutil dfu thread -f -pkg app_dfu_package.zip -p COMx --channel 11 --panid 43981 -r 4 -rs 5000 -a FF03::1". However, it is the uart version, and not the USB version. 

    Try manually compiling the dongle using nRF Connect for Desktop -> Programmer, and then call your nrfutil call "nrfutil dfu thread -pkg app_dfu_package.zip -p COMx --channel 11 --panid 43981 -r 4 -rs 5000 -a FF03::1" without the "-f" flag. Does that work?

    Please note that the COM port may change after you program it with the NCP example.

    Best regards,

    Edvin

Related