DFU in multiprotocol BLE/Thread application

RE: DFU in multiprotocol BLE/Thread application

Edvin — Fri, 07 Sep 2018 07:57:48 GMT

Hello,

So you want to use the Thread Bootloader and DFU, right, You only want the application that is running and updated to to include the softdevice?

Try to use the flash_placement and thumb files for the DFU projects, and adjust the FLASH_START and FLASH_SIZE parameters in your project settings to match the multiprotocol example's settings.

I believe you should use the same CoAP UDP port. Have you tested?

It might be easier to try to get the DFU up and running first, using the example, to ensure that everything is right there before mixing in the multiprotocol example.

Best regards,

Edvin

RE: DFU in multiprotocol BLE/Thread application

Edvin — Thu, 06 Sep 2018 14:34:16 GMT

Hello,

Sorry for the late reply. I have been out traveling. I am back now, and will look into this as soon as possible.

Best regards,

Edvin

RE: DFU in multiprotocol BLE/Thread application

marmio — Mon, 03 Sep 2018 11:46:46 GMT

Few more questions, because I still didn't make this work and I didn't see any more questions and tutorials on this topic.

1. How should the linker script and flash_placement.xml look like? Especially memory sections adresses and sizes. There are different linker scripts and files for multiprotocol and DFU for Thread examples

2. How should the app look like if I'm already using CoAP? Should I bind to the same or different UDP port?

3. thumb_crt0.s, there are also differences between DFU example and multiprotocol examples

Regards,

Marek

RE: DFU in multiprotocol BLE/Thread application

Edvin — Mon, 13 Aug 2018 10:20:07 GMT

I have not tested the Thread DFU yet, but I see that it uses the same bootloader library as the BLE bootloader, so I assume that it is only the transport layer that is changed.

So if your application requires a softdevice, which it does if you use BLE, you must use --sd-req 0xNN, which matches the softdevice that you are using.

You need to use coap_dfu_init(), yes. Just remember to also flash the bootloader before you run the project. At least in the regular BLE bootloader projects, it will return an error if it can't find any bootloader.

I can't see that it uses the same function to look for the bootloader, but I assume it has the same check. Either way, you would need the bootloader in order to perform the DFU.

I suggest that you try the guide for the Thread DFU example first, just to see that you get the bootloader is up and running before you try to implement it in a BLE + Thread project.

Best regards,

Edvin

RE: DFU in multiprotocol BLE/Thread application

marmio — Fri, 10 Aug 2018 14:08:04 GMT

And what do I have to add to my app, only coap dfu init, process and trigger functions, and all their dependencies?

RE: DFU in multiprotocol BLE/Thread application

Edvin — Fri, 10 Aug 2018 13:47:11 GMT

Hello Marek,

This field used in nrfutil, --sd-req 0xNN is used only for the bootloader to not accept a DFU pack that does not fulfill the requirements.

So if your application is using multiprotocol; BLE and Thread, and the BLE part requires the softdevice (which it probably does), then you should use the --sd-req that fits to that softdevice.

You may know this, but you can see the list of softdevice IDs by typing:

nrfutil pkg generate --help

Best regards,

Edvin