Queries on DFU

RE: Queries on DFU

beemavishnu — Mon, 02 Dec 2019 08:23:50 GMT

Thank you Sigurd for your inputs.

RE: Queries on DFU

Sigurd — Mon, 02 Dec 2019 08:15:25 GMT

Hi,

1) No, we don’t provide a SW solution for this. If this is for production, then I would download pc-nrfutil, found here, and use it to perform the DFU of all your devices, one by one. You could write a small script that uses pc-nrfutil, that automatically call nrfutil with the DFU option for each device (MAC address). (You could also connect multiple DK’s("DFU-master") to the computer.)

2) Yes, DFU of multiple devices at the same time is supported in BLE Mesh. But this requires you to have Mesh bootloader and supporting mesh in your application (if you want background DFU) and DFU for mesh would take much longer time than normal BLE.

RE: Queries on DFU

beemavishnu — Thu, 28 Nov 2019 05:55:46 GMT

Thank you for your input.

1) Regarding DFU for multiple devices at a time, are there any other ways where we can do DFU for more than 1 connected device at a time.

2) How about DFU in mesh network. Even in mesh network, whether only one device at a time can be in DFU mode ?

Thanks & Regards

Vishnu Beema

RE: Queries on DFU

Sigurd — Wed, 27 Nov 2019 15:35:58 GMT

Hi,

1) The SoftDevice.hex already includes the MBR. So you don't need to flash the stand-alone MBR hex, if you have flashed the SoftDevice.

2) If you have a bootloader, and the nRF52 resets(e.g. by waking up from SystemOFF sleep), then the CPU will start in the MBR, then jump to the bootloader(if present), if the bootloader finds a valid application, then the CPU will jump from bootloader to the application.

3) If you are using e.g. a PC with nRF Connect for desktop, then it only supports 1 DFU at the time.

4) For s140_nrf52_7.0.1, the SoftDevice+MBR takes 156 kB. The application space then starts at 0x27000

BR,

Sigurd