BLE mesh DFU and nRF Device Manager

[Matej]

Hello,

I'm having an issue with performing fw update with ble mesh DFU examples.

My setup is pca10056 used as distributor and pca10059 - dongle as target.

I'm using nrf v2.6.2 (same with 2.6.0) and other dependecies are updated with west.

I added both of them to mesh and binded keys for blob transfer server and firmware update server on the target (dongle). While on the distributor I have bind keys to blob and firmware update client,  but not to server.

Once I upload target image, it's start uploading and at the end confirming fails to connection timeout.

Would you be please so kind and describe a bit more in details procedure what needs key binding and flashing procedure... Since there are quite some options when uploading file; e.g. test, confirm, test and confirm, no revert etc... When I select advanced mode, there is combo for application core, network core etc... For what purpose are those options?

In one of retries I have also noticed that there were two images stored at distributor, but images were not swapped neither on distributor or target node.

Thank you for your inputs.

Best regards,

Matej

  

[Amanda Hsieh]

Hi, 

Once I upload target image, it's start uploading and at the end confirming fails to connection timeout.

You can send a message to the device from the nRF Device Manager to initiate the connection. Then, upload the image after the device is connected 

Are you using the unmodified  Device Firmware Update (DFU) distributor sample? Since the device name in the nRF Device Manager app is not as the distributor sample. 

Please follow the instructions in the Testing section to Provision the device and Upload a firmware image via the nRF Device Manager app to slot-1.

Regards,
Amanda H.

[Matej]

Hi Amanda, thank you for your inputs.

I'm using sample as it is - without changes, interesting that there is no name.

I have followed mentioned description; send hello and upload image.

Now, I'm wondering how to trigger that this image will be distributed over the mesh to other nodes, since current state is pending.

After clicking confirm, distributor stops responding at all. 

Thank you.

Best regards,

Matej

[Amanda Hsieh]

Matej said:

Now, I'm wondering how to trigger that this image will be distributed over the mesh to other nodes, since current state is pending.

Please refer to DFU over Bluetooth Mesh doc.

Matej said:

After clicking confirm, distributor stops responding at all. 

Do not request to test/confirm the image. Otherwise, the bootloader will try swapping the distributor image with the uploaded one at the next reboot.

[upupsky]

use rtt, then shell cmd.