About Mesh DFU Test

Question

1. I used the nRF5 SDK for Mesh v2.2.0 version to test the Mesh DFU feature and follow the DFU example tutorial. 
 http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v2.2.0%2Fmd_doc_getting_started_getting_started.html -------> DFU quick start guide 
 2. The upgraded application is blinky_nrf52840_xxAA_s140_6.0.0.hex. After the upgrade is complete, I want to upgrade the second time, but it is not successful. 
 mesh-sdk$ nrfutil dfu genpkg --application bin/blinky/blinky_nrf52832_xxAA_s132_6.0.0.hex \ 
 --company-id 0x00000059 \ 
 --application-id 1 \ 
 --application-version 2 \ 
 --key-file private_key.txt \ 
 --sd-req 0x009D \ 
 --mesh dfu_test.zip 
 3. Then I went to check the source code of the DFU upgrade, so I think the application blinky_nrf52840_xxAA_s140_6.0.0.hex is not equipped with DFU function, just for flash led. 
 
 4. Finally, I tried to clear the device program and re-run the first upgrade, but the application selected the hex program compiled by the DFU routine. The file size is about 300K, but the upgrade is very slow, and finally there is no upgrade. 
 nrfutil dfu genpkg --application examples/NOA_dfu/build/dfu_nrf52840_xxAA_s140_6.0.0_Debug/dfu_nrf52840_xxAA_s140_6.0.0.hex --company-id 0x00000059 --application-id 1 --application-version 3 --key-file private_key.txt --sd-req 0x009D --mesh dfu_test.zip 
 I want to know if my understanding is accurate. And whether the application must be modified based on the DFU example, under the premise that the MESH DFU function is required

Bjørn Kvaale · Answer

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!

Fullscreen dfu.bat Download

echo @off

title Start Mesh v2.2.0 DFU process!
echo Start DFU

nrfutil_mesh keys --gen-key private_key.txt
nrfutil_mesh keys --show-vk hex private_key.txt

pause

echo Add public key info to tools/dfu/bootloader_config_default.json file

echo Generating DFU zip file

nrfutil_mesh dfu genpkg --application ../../bin/blinky/blinky_nrf52840_xxAA_s140_6.0.0.hex --company-id 0x00000059 --application-id 1 --application-version 2 --key-file private_key.txt --sd-req 0x00A9 --mesh dfu_test_blinky.zip
	

	
echo generate hex version of device page
rem Device page generator requires Python 2.7

rem python ../../tools/dfu/device_page_generator.py -d nrf52840_xxAA -sd "s140_6.0.0"



echo Erase chip memory on all devices

nrfjprog --eraseall -s <SEGGER ID>
nrfjprog --eraseall -s <SEGGER ID>
nrfjprog --eraseall -s <SEGGER ID>

echo Flash softdevice on all devices

nrfjprog --program ../../bin/softdevice/s140_nrf52_6.0.0_softdevice.hex -s <SEGGER ID> --chiperase
nrfjprog --program ../../bin/softdevice/s140_nrf52_6.0.0_softdevice.hex -s <SEGGER ID> --chiperase
nrfjprog --program ../../bin/softdevice/s140_nrf52_6.0.0_softdevice.hex -s <SEGGER ID> --chiperase

echo Flash serial BL on all dfu

nrfjprog --program ../../bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex -s <SEGGER ID> --verify
nrfjprog --program ../../bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex -s <SEGGER ID> --verify
nrfjprog --program ../../bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex -s <SEGGER ID> --verify

echo Flash DFU app on all devices

nrfjprog --program ../../examples/dfu/build/dfu_nrf52840_xxAA_s140_6.0.0_Debug/dfu_nrf52840_xxAA_s140_6.0.0.hex -s <SEGGER ID>  --verify
nrfjprog --program ../../examples/dfu/build/dfu_nrf52840_xxAA_s140_6.0.0_Debug/dfu_nrf52840_xxAA_s140_6.0.0.hex -s <SEGGER ID>  --verify
nrfjprog --program ../../examples/dfu/build/dfu_nrf52840_xxAA_s140_6.0.0_Debug/dfu_nrf52840_xxAA_s140_6.0.0.hex -s <SEGGER ID>  --verify

echo Flash device page on all devices

nrfjprog --program ../../tools/dfu/bin/device_page_nrf52840_xxAA_s140_6.0.0.hex -s <SEGGER ID>
nrfjprog --program ../../tools/dfu/bin/device_page_nrf52840_xxAA_s140_6.0.0.hex -s <SEGGER ID>
nrfjprog --program ../../tools/dfu/bin/device_page_nrf52840_xxAA_s140_6.0.0.hex -s <SEGGER ID>

echo Soft reset all devices

nrfjprog --reset -s <SEGGER ID>
nrfjprog --reset -s <SEGGER ID>
nrfjprog --reset -s <SEGGER ID>

echo Start DFU
nrfutil_mesh dfu serial -pkg dfu_test_blinky.zip -p COM29 -b 115200 -fc --mesh

pause

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

Kind Regards,

Bjørn

About Mesh DFU Test

Top Replies