About Mesh DFU Test

RE: About Mesh DFU Test

Bjørn Kvaale — Mon, 12 Nov 2018 11:04:16 GMT

Would you mind upvoting any comment(s) you thought were helpful & pressing More -> Suggest as Answer if applicable?

RE: About Mesh DFU Test

NOA-BEN — Mon, 12 Nov 2018 02:25:33 GMT

Thank you very much for your reply, you mean after all the devices have completed the first upgrade. In the second upgrade, I need to erase and re-burn the firmware to successfully burn it.
I tried communication between Mesh clients but it didn't work.

RE: About Mesh DFU Test

Bjørn Kvaale — Fri, 02 Nov 2018 16:09:10 GMT

Another quick remark: I put the batch script at this location: nrf5_SDK_for_Mesh_v2.2.0_src\scripts\DFU\

RE: About Mesh DFU Test

Bjørn Kvaale — Fri, 02 Nov 2018 16:02:41 GMT

Sorry for the delayed response. I have finished testing the DFU bootloader example. I essentially just followed the Getting Started with DFU documentation that you looked at.

As you can see from the picture below, the bootloader is still there after you perform the DFU.

However, as you pointed out, the blinky application does not support DFU. When I tried to do the DFU the second time around, I got the same error you did.

What I did next was to first erase one of the boards, then run the following commands on that board:

nrfjprog --eraseall
nrfjprog --program ../../bin/softdevice/s140_nrf52_6.0.0_softdevice.hex --chiperase
nrfjprog --program ../../bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex --verify
nrfjprog --program ../../examples/dfu/build/dfu_nrf52840_xxAA_s140_6.0.0_Debug/dfu_nrf52840_xxAA_s140_6.0.0.hex  --verify
nrfjprog --program ../../tools/dfu/bin/device_page_nrf52840_xxAA_s140_6.0.0.hex
nrfjprog --reset
nrfutil_mesh dfu serial -pkg dfu_test_blinky.zip -p COM29 -b 115200 -fc --mesh

You can naturally just use nrfutil instead of nrfutil_mesh. Since I use both quite often, I decided to rename the mesh version nrfutil_mesh. Once I made those changes, everything worked fine like it should.

Also, in case you have not created a bat script, I have uploaded one below to make this whole process a lot easier & more enjoyable. Just replace the SEGGER_ID with the IDs on the top of the interface MCU on your 52 DKs.

I used three DKs during this test, but you can easily use 2 or even more if you really want to test it out more!

devzone.nordicsemi.com/.../dfu.bat

Regarding the communication protocol, I believe we just use the serial interface. Hope that helps!

Kind Regards,

Bjørn

RE: About Mesh DFU Test

Bjørn Kvaale — Fri, 02 Nov 2018 16:02:41 GMT

Sorry for the delayed response. I have finished testing the DFU bootloader example. I essentially just followed the Getting Started with DFU documentation that you looked at.

As you can see from the picture below, the bootloader is still there after you perform the DFU.

However, as you pointed out, the blinky application does not support DFU. When I tried to do the DFU the second time around, I got the same error you did.

What I did next was to first erase one of the boards, then run the following commands on that board:

nrfjprog --eraseall
nrfjprog --program ../../bin/softdevice/s140_nrf52_6.0.0_softdevice.hex --chiperase
nrfjprog --program ../../bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex --verify
nrfjprog --program ../../examples/dfu/build/dfu_nrf52840_xxAA_s140_6.0.0_Debug/dfu_nrf52840_xxAA_s140_6.0.0.hex  --verify
nrfjprog --program ../../tools/dfu/bin/device_page_nrf52840_xxAA_s140_6.0.0.hex
nrfjprog --reset
nrfutil_mesh dfu serial -pkg dfu_test_blinky.zip -p COM29 -b 115200 -fc --mesh

I used three DKs during this test, but you can easily use 2 or even more if you really want to test it out more!

devzone.nordicsemi.com/.../dfu.bat

Regarding the communication protocol, I believe we just use the serial interface. Hope that helps!

Kind Regards,

Bjørn

RE: About Mesh DFU Test

NOA-BEN — Mon, 29 Oct 2018 09:53:52 GMT

I also want to know the communication protocol between nrfutil and the device in the Mesh DFU function. We want to implement DFU function through other serial ports, such as WiFi module and NRF52840.

Can you provide this communication protocol to us?

RE: About Mesh DFU Test

NOA-BEN — Mon, 29 Oct 2018 06:55:06 GMT

Thank you very much for your reply and look forward to your testing of the NRF52840 Mesh.

I will try to modify the code to implement server to server communication, or client and client communication

RE: About Mesh DFU Test

Bjørn Kvaale — Fri, 26 Oct 2018 13:55:44 GMT

I will test the dfu functionality with two 52840 dks & get back to you on that. Why should the server not be able to send an acknowledged message to another server? That way, a server sends a set message to another server for example & the receiving server will respond to the sender with a status message.

Right now, the light switch server example is setup to send a status message back to the client, but you should be able to update that to send a reliable unicast message to another server. What you could do is add the generic on off client model in the light switch server example. A similar example is shown here, where I have updated the light switch example to be both a server & a client (by adding the generic on off client model in the server example). By provisioning via the nRF Mesh app (available for Android & iOS), you are able to use the device as both a light switch & a light (i.e. client or server). Just beware that the example uses a slightly simplified version of the "generic on off model". Therefore, I would use the github example as a good starting point, but maybe rather update the mesh sdk v2.2.0 light switch example to achieve the same thing.

If you want a quick way to send messages from one client to another client, I would test out the github code. There are two pdfs that show the testing guidelines.

I agree that Bluetooth Mesh is not the simplest of things to learn. I have spent quite a lot of time supporting Bluetooth Mesh & there are definitely easier examples to understand. ;)

RE: About Mesh DFU Test

NOA-BEN — Fri, 26 Oct 2018 09:30:10 GMT

I am very sorry, because I can see your reply next week.

I want to ask a question here, I run the Mesh light_switch routine.

Data can only be bidirectional from server to client. It can't be from the server to the server, or the client. I tried to read the client and server code and found it difficult and took a lot of time.

I would like to ask if there is a corresponding example, sent directly from the client to the client.

RE: About Mesh DFU Test

NOA-BEN — Fri, 26 Oct 2018 05:55:36 GMT

And I used Two NRF52840 dev kits To Test DFU

RE: About Mesh DFU Test

NOA-BEN — Fri, 26 Oct 2018 02:42:46 GMT

Yes. I have deleted all of the zip files and re-run step3 and 10. --application-version 4.

The first DFU was successful, but the second DFU prompted the following error.

/**********************************************************************************************

Upgrading target on COM29 with DFU package D:\Github_Project\NOA_IoT_BACKBONE\nrf5_SDK_for_Mesh_v2.2.0_src\dfu_test.zip. Flow control is enabled.
[------------------------------------] 0%Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 1656
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
PC -> target: 0502aabbccdd
PC -> target: 0502aabbccdd
PC -> target: 0502aabbccdd
PC -> target: 0502aabbccdd
PC -> target: 0502aabbccdd

Failed to upgrade target. Error is: Failed to establish connection

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
Closing serial port...

************************************************************************************************/

And I don't understand what you said created a script

RE: About Mesh DFU Test

Bjørn Kvaale — Thu, 25 Oct 2018 12:41:35 GMT

Hi,

It should work to do the DFU multiple times. Like the documentation states, you will need to do this:

"To try another DFU, re-run steps 3 and 10 with an increased version number, for example --application-version 3, and use the new zip file to do the DFU again."

If you have not already created a script, I would start there. Then, I would erase the boards completely & start from scratch one more time.

How many dev kits are you testing with atm?

Regarding your 4th point, I would delete all of the zip files generated & start from scratch. Then, it should work to do the DFU multiple times.

Kind Regards,

Bjørn