DFU example

RE: DFU example

Edvin — Thu, 14 Mar 2019 08:45:19 GMT

That is good news! Glad it worked out.

Yes, one has to be careful when working with files that are not specific for one example. The uart files are one of the files that are common by many parts of the SDK.

Let us follow up on your other ticket regarding implementing the DFU part to other projects, then.

Best regards,

Edvin

RE: DFU example

DeveloperZ — Tue, 12 Mar 2019 18:43:07 GMT

Hi Edvin,

Finally, I got the DFU up and running. I downloaded everything from the website and repeated the process from the scratch and it worked.

My best guess is that DFU wasn't being pushed properly because of some random change in the 15.2.0 SDK (may be UART files) which was made in a different application or somehow!!

Thanks a lot for your patience. 🙂

RE: DFU example

DeveloperZ — Tue, 12 Mar 2019 12:05:39 GMT

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/175529"]You use Segger Embedded Studio, right? And what SDK_for_mesh version do you use?[/quote]

Yes, I am using Segger IDE. I am using 15.2.0 SDK and 3.1.0 Mesh SDK

I have attached the compressed folder of dfu example below. I have removed the build folder and zipped it as it was giving an error to upload a large file

devzone.nordicsemi.com/.../4745.dfu.zip

Thank you.

RE: DFU example

Edvin — Tue, 12 Mar 2019 07:45:49 GMT

Can you zip the DFU example that you are using? I want to test it. Zip the entire folder: SDK_for_Mesh\examples\dfu.

You use Segger Embedded Studio, right? And what SDK_for_mesh version do you use? (and what "normal" SDK version do you use with it?)

I want to see if I can get it up an running on my computer. Basically, if there are some project settings that are causing the issues, or if it is the procedure.

BR,

Edvin

RE: DFU example

DeveloperZ — Mon, 11 Mar 2019 15:27:11 GMT

Hi!

We tried to run this from the scratch: stock 15 SDK, Stock Mesh SDK, everything as it comes from Nordics downloads pages, but still didn't work... So we doubt this is anything related to the UART changes we made on our custom firmware.

We are going to run the example again on a completely stock setup again just to be sure... but we doubt this is going to make any difference... all in all IMHO, the documentation could be more clear and useful?

Following are the files that I generated and flashed after changing the UART pins to initial configurations and also pca10040 file with pin configurations:

devzone.nordicsemi.com/.../3731.device_5F00_page_5F00_nrf52832_5F00_xxAA_5F00_s132_5F00_6.1.0.hex

devzone.nordicsemi.com/.../4405.dfu_5F00_nrf52832_5F00_xxAA_5F00_s132_5F00_6.1.0.hex

devzone.nordicsemi.com/.../1016.dfu_5F00_test.zip

devzone.nordicsemi.com/.../8203.mesh_5F00_bootloader_5F00_serial_5F00_gccarmemb_5F00_nrf52832_5F00_xxAA.hex

devzone.nordicsemi.com/.../pca10040.h

devzone.nordicsemi.com/.../0250.s132_5F00_nrf52_5F00_6.1.0_5F00_softdevice.hex

Thank you.

RE: DFU example

Edvin — Mon, 11 Mar 2019 14:54:25 GMT

Ok. I don't know why it is not working. Can you describe how you changed the Serial interface when you changed the UART pins? Did you turn off flow control?

Can you send the updated hex files with the correct UART settings? The previous version wasn't working, I can confirm that. But there has to be something that you have either changed, or done correctly when following the guide. Was there some part of the guide that you were uncertain of, where you may have done something incorrectly?

I am really trying to understand why it isn't working, but all I can see from the information you describe is that the board isn't responding, so at this point, anything could be the source of the issue.

BR,

Edvin

RE: DFU example

DeveloperZ — Mon, 11 Mar 2019 14:28:45 GMT

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/175380"]What HW are you trying this on? Are you using a DK?[/quote]

Yes, I am using an nRF52 development kit.

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/175380"]Can you show me the log output and the terminal output when you try to push the DFU?[/quote]

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/175380"]Did you also reprogram the DK after changing the UART pins?[/quote]

Yes, I repeated the whole process again with a new Mesh SDK

RE: DFU example

Edvin — Mon, 11 Mar 2019 14:18:47 GMT

What HW are you trying this on? Are you using a DK? Can you show me the log output and the terminal output when you try to push the DFU? Did you also reprogram the DK after changing the UART pins?

RE: DFU example

DeveloperZ — Mon, 11 Mar 2019 13:52:51 GMT

Hi,

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/175285"]Did you change the UART pins in the application?[/quote]

Yes, I noticed that I changed the UART pin configuration. Now, I set them back to the original configuration and tried to push the DFU but the result is the same as what you saw.

RE: DFU example

Edvin — Mon, 11 Mar 2019 10:24:50 GMT

Hello,

I see that your application is running, I can see it from the log. However, if you add --verbose to your DFU command:
nrfutil-mesh --verbose dfu serial -pkg dfu_test.zip -p COM7 -b 115200 --mesh

(obviously with your own COM port), you will see that it says:

Your application log says:

0> <t: 1>, main.c, 206, ----- Bluetooth Mesh DFU Example -----
0> <t: 8818>, serial_handler_prov.c, 267, Generating encryption keypair...
0> <t: 13706>, main.c, 224, Initialization complete!
0> <t: 18474>, main.c, 245, Enabling serial interface...
0> <t: 18477>, mesh_app_utils.c, 65, Device UUID (raw): 464B4596FD473049936CE0FE34C4D5FD
0> <t: 18480>, mesh_app_utils.c, 70, Device UUID : 96454B46-47FD-4930-936C-E0FE34C4D5FD
0> <t: 18488>, nrf_mesh_dfu.c, 528, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFE
0> <t: 18493>, nrf_mesh_dfu.c, 561, SERIAL TX!
0> <t: 18500>, main.c, 253, DFU example started!

(RTT Log read using J-Link RTT Viewer).

The "--verbose output from nrfutil --verbose dfu serial -pkg dfu_test.zip -p COM7 -b 115200 --mesh" suggests that there are some issues with getting a response from the serial connection. Did you change the UART pins in the application?

Best regards,

Edvin

RE: DFU example

DeveloperZ — Fri, 08 Mar 2019 15:16:25 GMT

Hi,

Sorry about that. I added the files below:

devzone.nordicsemi.com/.../device_5F00_page_5F00_nrf52832_5F00_xxAA_5F00_s132_5F00_6.1.0.hex

devzone.nordicsemi.com/.../dfu_5F00_nrf52832_5F00_xxAA_5F00_s132_5F00_6.1.0.hex

devzone.nordicsemi.com/.../mesh_5F00_bootloader_5F00_serial_5F00_gccarmemb_5F00_nrf52832_5F00_xxAA.hex

devzone.nordicsemi.com/.../s132_5F00_nrf52_5F00_6.1.0_5F00_softdevice.hex

devzone.nordicsemi.com/.../5074.dfu_5F00_test.zip

RE: DFU example

Edvin — Fri, 08 Mar 2019 15:10:50 GMT

You can upload it here on devzone. Just click insert -> image/video/file

RE: DFU example

DeveloperZ — Fri, 08 Mar 2019 13:16:22 GMT

Hi, I have put the hex files and the Blinky dfu packet in this folder here. Please let me know if you need any other files.

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/175013"]you may try using the nRF Programmer, which is part of nRF Connect 2 for Desktop[/quote]

Okay, I will try and let you know the update.

Thank you.

RE: DFU example

Edvin — Fri, 08 Mar 2019 13:06:23 GMT

Can you send the hex files here? I would like to try.

Also, you may try using the nRF Programmer, which is part of nRF Connect 2 for Desktop. Maybe it gives some more information on why it isn't working.

BR,

Edvin

RE: DFU example

DeveloperZ — Fri, 08 Mar 2019 12:55:58 GMT

Yes, I was able to program every file(softdevice, boot loader, application, device page) with nrfjprog but boot loader verification hangs!!!

RE: DFU example

Edvin — Fri, 08 Mar 2019 09:42:52 GMT

So can you try to use nrfjprog to program all the files?

RE: DFU example

DeveloperZ — Thu, 07 Mar 2019 19:34:07 GMT

Hey,

No, I have been using nrfjprog only to perform the dfu.

Also, any idea on why the boot loader verification is hung up at Resetting Device..

Reading UICR.. OK.

Reading Device page.. OK.

Resetting device..

RE: DFU example

Edvin — Thu, 07 Mar 2019 17:52:50 GMT

Hello,

Well, yes and no. The issue is the signing of the application that is flashed when you program the device via an IDE. IDEs doesn't use the .hex file, but rather the .out file to be able to debug the application. When using this file, the key that was used in the settings page will change the CRC of the application, and the bootloader will not validate it as a valid application (it believes that someone has messed with/changed the Firmware). If this is what you have done, then that is probably why the application is not responding to the serial messages, because the application is not running. Try to flash your .hex files using nrfjprog, and see whether that works better.

You can download it here:

https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF5-Command-Line-Tools

Best regards,

Edvin.

RE: DFU example

DeveloperZ — Thu, 07 Mar 2019 12:54:53 GMT

Hey,

I have another question. Can't we use Segger IDE to flash the dfu code onto the board, flash the device page, reset the board and then run the DFU command? instead to executing the commands and flashing the board from command line

RE: DFU example

DeveloperZ — Wed, 06 Mar 2019 18:28:48 GMT

Hi,

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/174633"]I usually do a .bat script (windows), but you should be able to write a .sh script doing basically the same things.[/quote]

I will try this out and let you know once done.

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/174633"]python bootloader_verify.py 682994997 usbmodem0006829949971[/quote]

This command hangs up at Resetting device.. as follows:

Reading UICR.. OK.

Reading Device page.. OK.

Resetting device..

RE: DFU example

Edvin — Wed, 06 Mar 2019 16:22:50 GMT

Hello,

The 0502aabbccdd is an echo command to see that the serial device is responding, something it was not.

You can see the list over serial commands and serial events here:

https://www.nordicsemi.com/DocLib/Content/SDK_Doc/Mesh_SDK/v3-0-0/md_doc_libraries_serial_cmd#device-echo

The first byte (05) is the length of the packet (excluding this byte itself), and the second byte is the OPcode. 02 means echo, and the rest of the bytes is the bytes that the device is supposed to echo back.

Have you reset the device after programming it (using nrfjprog)? "nrfjprog --reset" should do the trick. If not, there is something wrong with the application, the bootloader, or possibly the device page that you have flashed. Can you try to run the

python bootloader_verify.py 682994997 usbmodem0006829949971

command with the dev/tty. part in front of the usbmodem########?

The DFU guides are a bit tricky, because everything has to be done exactly correct for it to work. What I really recommend that you do is to write a script that compiles, generates the device page, erases the chip, programs the softdevice + bootloader + application + device page, resets the device, and then you can try to perform the dfu. I usually do a .bat script (windows), but you should be able to write a .sh script doing basically the same things.

One of these scripts that I have made is a file called test.bat, and looks like this:

make

nrfutil-mesh dfu genpkg --application _build\nrf52832_xxaa.hex --company-id 0x00000059 --application-id 1 --application-version 2 --key-file keys\private_key.txt --sd-req 0x00AF --mesh dfu_test2.zip
nrfutil-mesh dfu genpkg --application _build\nrf52832_xxaa.hex --company-id 0x00000059 --application-id 1 --application-version 3 --key-file keys\private_key.txt --sd-req 0x00AF --mesh dfu_test3.zip


cd tools\dfu
python device_page_generator.py -d nrf52832_xxAA -sd "s132_6.1.0"
cd ..\..

nrfjprog -e --snr 682654319
nrfjprog --program ..\..\nRF5_SDK_15.2.0_9412b96\components\softdevice\s132\hex\s132_nrf52_6.1.0_softdevice.hex --verify --snr 682654319
nrfjprog --program ..\bin\bootloader\gccarmemb\mesh_bootloader_gccarmemb_nrf52832_xxAA.hex --snr 682654319
nrfjprog --program _build\nrf52832_xxaa.hex --verify --snr 682654319
nrfjprog --program tools\dfu\bin\device_page_nrf52832_xxAA_s132_6.1.0.hex --verify --snr 682654319
nrfjprog --reset --snr 682654319

TIMEOUT 5

nrfutil-mesh --verbose dfu serial -pkg dfu_test2.zip -p COM7 -b 115200 -fc --mesh

Exactly this script uses an armgcc compiler, so you would of course replace "make" with manually compiling your application project. Another thing this script doesn't do is to insert the private and public key like step number 1 and 2 in the guide tells you. You must do this manually.

What you also can do to check whether your application is running is to have some logging (which the example from the guide has). Check out whether anything is logged using "RTT Viewer" from J-Link to see that your application is actually running before you start the DFU update.

BR,

Edvin

RE: DFU example

DeveloperZ — Wed, 06 Mar 2019 15:20:46 GMT

[quote userid="26071" url="~/f/nordic-q-a/44199/dfu-example/174561"]nrfutil --verbose dfu serial -pkg dfu_test.zip -p /dev/tty.usbmodem0006829949971 -b 115200 -fc --mesh[/quote]

This command worked. It opened the serial port and it took around 10 minutes trying to do dfu and finally it failed. The response is as follows:

Upgrading target on /dev/tty.usbmodem0006829949971 with DFU package /Users/developerbubblynet/Desktop/MeshSDK/dfu_MeshSDK310/dfu_test.zip. Flow control is enabled.

Flushing com-port...

Opened com-port

Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 2468

Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.

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...

The line PC -> target: 0502aabbccdd prints every 2/3 minutes and finally after 10 minutes or more, it failed.

RE: DFU example

Edvin — Wed, 06 Mar 2019 13:10:17 GMT

Hello,

Can you please try to add the following when you call the nrfutil scripts:

Instead of e.g. nrfutil --verbose dfu serial -pkg dfu_test.zip -p usbmodem0006829949971 -b 115200 -fc --mesh

can you try to use the full path to the COM port:

nrfutil --verbose dfu serial -pkg dfu_test.zip -p /dev/tty.usbmodem0006829949971 -b 115200 -fc --mesh

It worked for someone else having some problems with Mac and nrfutil.

BR,

Edvin

RE: DFU example

DeveloperZ — Wed, 06 Mar 2019 12:54:49 GMT

[quote userid="73423" url="~/f/nordic-q-a/44199/dfu-example/174524"]Are you sure that your COM Port is not occupied when you try to do the DFU?[/quote]

I see no other functionality/application being run on the board which uses serial port other than DFU.
So, yes. I don't think there is anything that is not allowing the serial port to open!!

Thank you.

RE: DFU example

AndreasF — Wed, 06 Mar 2019 11:46:11 GMT

Hi.

Are you sure that your COM Port is not occupied when you try to do the DFU?

Best regards,

Andreas