BLE Mesh DFU Issue with dfu_no_serial Example

Question

When I use dfu_nrf52832_xxAA_s132_6.1.1.hex, it works all devices updated with blink code as described in dfu_quick_start.md But without any provisioning Process, why? And in 3 out of 5 devices I upload dfu_no_serial_nrf52832_xxAA_s132_6.1.1.hex generated file, and in other 2 uploads dfu_nrf52832_xxAA_s132_6.1.1.hex. And all the other steps are same as explained in dfu_quick_start.md In DFU process 2 devices with dfu_nrf52832_xxAA_s132_6.1.1.hex code is uploaded and blinky started, but not in other 3 devices, which means that they are not updated. I want to implement dfu in my code, but little confused about how, from above two, as it seems that I have to use dfu_nrf52832_xxAA_s132_6.1.1.hex source not dfu_no_serial_nrf52832_xxAA_s132_6.1.1.hex source. for DFU. Please Help me regarding it. 
 Thank You Bivay

Hung Bui · Accepted Answer

Hi Bivay, 
 
 By theory they should all works, both the one with dfu_nrf52832_xxAA_s132_6.1.1.hex and the one with dfu_no_serial_nrf52832_xxAA_s132_6.1.1.hex. 
 I'm not sure what would go wrong here. Could you try to compile the file from the code, instead of using the precompiled hex file ? 
 The reason why you can do DFU without doing provisioning is that our Mesh DFU using broadcast mesh instead of Bluetooth mesh to do DFU. In broadcast mesh there is no encryption and no provisioning needed. If you want to implement DFU in your application, please have a look at the dfu example. It's pretty simple, just include the DFU file and include a mesh event handler as in the dfu example (mesh_evt_handler) .

bivay · Answer

Issue Solved by resetting all module before upload code. Thank You Bivay

BLE Mesh DFU Issue with dfu_no_serial Example

Top Replies