Problems when flashing Thingy 52 using NRF52 DK: pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 13

[tobiass]

Hello again, I accidently verified one of my own answer so I will retry.

I am currently trying to update the firmware for Thingy 52, using the NRF52 development kit.

I am following the instructions in this section:

https://nordicsemiconductor.github.io/Nordic-Thingy52-FW/documentation/dfu_generating.html

Right now I'm very stuck. I have generated the private and public keys, and generated the DFU package for the application. I then need to compile the bootloader. What files (entire build or just the hex, out or bin files?) from the bootloader do I need to include in the package, and when I flash the Thingy? 

Do I need to compile the softdevice, or just use the hex-file in "sdk_components\softdevice\s132\hex"?

The link to generating the bootloader settings seems to be broken:

http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/nrfutil/nrfutil_settings_generate_display.html

Having then compiled all the needed elements,  how do I combine these into a single package for the DFU?

Using the NRF52 DK and following the instructions, I tried updating by only uploading the DFU package for the application, and got the following errors:

"

C:\Users\Owner\Downloads>nrfutil_.exe dfu ble -ic NRF52 -pkg dfu-app.zip
No target selected. Default device name: DfuTarg is used.
Please select connectivity serial port:
0 : COM3 - 682293664
Enter your choice: : 0

Traceback (most recent call last):
File "nordicsemi\__main__.py", line 1464, in <module>
File "click\core.py", line 764, in __call__
File "click\core.py", line 717, in main
File "click\core.py", line 1137, in invoke
File "click\core.py", line 1137, in invoke
File "click\core.py", line 956, in invoke
File "click\core.py", line 555, in invoke
File "nordicsemi\__main__.py", line 1151, in ble
File "nordicsemi\dfu\dfu.py", line 129, in dfu_send_images
File "nordicsemi\dfu\dfu.py", line 90, in _dfu_send_image
File "nordicsemi\dfu\dfu_transport_ble.py", line 453, in open
File "nordicsemi\dfu\dfu_transport_ble.py", line 106, in open
File "site-packages\pc_ble_driver_py\ble_driver.py", line 127, in wrapper
pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 13
[25572] Failed to execute script __main__

I am using Windows 10 and the nrfutil executable.

Best regards,

Tobias Samuelsson

[Edvin]

Hello Tobias,

The link seems to be broken, yes. I believe this is the link you are looking for:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrfutil%2FUG%2Fnrfutil%2Fnrfutil_settings_generate_display.html

Where did you find the broken link? I can report it and have it fixed.

First, I would like to ask you a couple of things:

Have you programmed a new bootloader to the Thingy52? Or is it the bootloader that was preprogrammed on the Thingy when you received it?

C:\Users\Owner\Downloads>nrfutil_.exe dfu ble -ic NRF52 -pkg dfu-app.zip

 The command that you use here seems to be incomplete.

It should look like this:

nrfutil dfu ble -pkg packet.zip -ic NRF52 -p COMn -n "DfuTarg" -snr 123456789 -f

Where packet.zip is the path to your generated DFU image (let me know if you are unsure on how to generate this). NRF52 refers to the Development Kit that you use to update the Thingy FW (you need a separate nRF Device. Do you have this?) COMn should be changed to the COM port which your DK has, e.g. COM3. "DfuTarg" should be the name of the device that you want to update (the advertising name). 123456789 should be changed to the serial number of the on board debugger on your DK (the number on the white sticker). You can type in "nrfutil.exe dfu ble --help" to see all possible input parameters and an explanation of what they are.

But have you reprogrammed the bootloader on your thingy to your own bootloader with your own set of keys? To so so you would need a 10-pin segger cable.

Best regards,

Edvin

[tobiass]

Many thanks Edvin! The broken link was found on this page (in the bootloader section):

https://nordicsemiconductor.github.io/Nordic-Thingy52-FW/documentation/dfu_generating.html

NRF52 is the device I use. I also use the preprogrammed bootloader in Thingy52.

I tried using your command:

"C:\Users\Owner\Downloads>nrfutil_.exe dfu ble -pkg dfu-app.zip -ic NRF52 -p COM3 -n "ThingyDfu" -snr 682293664 -f
Flashing connectivity firmware...
Connectivity firmware flashed.

Traceback (most recent call last):
File "nordicsemi\__main__.py", line 1464, in <module>
File "click\core.py", line 764, in __call__
File "click\core.py", line 717, in main
File "click\core.py", line 1137, in invoke
File "click\core.py", line 1137, in invoke
File "click\core.py", line 956, in invoke
File "click\core.py", line 555, in invoke
File "nordicsemi\__main__.py", line 1151, in ble
File "nordicsemi\dfu\dfu.py", line 129, in dfu_send_images
File "nordicsemi\dfu\dfu.py", line 90, in _dfu_send_image
File "nordicsemi\dfu\dfu_transport_ble.py", line 453, in open
File "nordicsemi\dfu\dfu_transport_ble.py", line 106, in open
File "site-packages\pc_ble_driver_py\ble_driver.py", line 127, in wrapper
pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 3
[7980] Failed to execute script __main__

C:\Users\Owner\Downloads>nrfutil_.exe dfu ble -pkg dfu-app.zip -ic NRF52 -p COM3 -n "DfuTarg" -snr 682293664 -f
Board already flashed with connectivity firmware."

So it successfully flashes the connectivity firmware, but then exits with an error code 3.

I'm not sure which DFU packets I need to update. My plan is to use the Thingys as nodes in an acoustic locator network (using built-in RTC, in combination with the mic) so I'll be having them constantly in sleep/standby mode until the microphone registers a sound event, and then periodically send data (time stamps from the RTC) to an external data collector (Android phone). I will only be using the built-in functions of the Thingys. How much code do I need to add to the firmware? 

Many thanks for your help!

Best regards, Tobias

[Edvin]

Hello Tobias,

 

tobiass said:

I also use the preprogrammed bootloader in Thingy52.

 You need to replace this bootloader. It is locked with a private key that we don't have access to. You need to physically connect a programmer to the thingy using a DK and a segger 10 pin cable, like this one. You will not be able to update the FW to your own firmware unless you replace the bootloader. If you are not familiar with the bootloader, I suggest you start by experimenting with the bootloader on a DK using this guide.

I have two more questions:

1: How did you install nrfutil? Can you try to update to the latest version? Use the .exe file from the 5.2.0 release here.

2: What device is 682293664? Is it a Development Kit?

BR,

Edvin