nrfutil dfu ble failed to open Win 10

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Mon, 20 Aug 2018 08:41:46 GMT

Which version of nrfutil are you using? Did you use the .exe file or did you build it from the source?

RE: nrfutil dfu ble failed to open Win 10

Yosi.stx — Sat, 18 Aug 2018 19:29:56 GMT

Hi guys, I encountered the same issue both in Win 10 and in Win 7.

I run the the command prompt as an administrator (in Win7), It didn't resolved my "Error code 13" issue.

See attached figure:

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Wed, 11 Apr 2018 10:53:25 GMT

xavier: Thanks for posting the solution here. I will report it internally.

RE: nrfutil dfu ble failed to open Win 10

xavier — Tue, 10 Apr 2018 09:46:20 GMT

Hi guys, I encountered the same issue and solved it.

*******************************************************

File "C:\Python27\lib\site-packages\pc_ble_driver_py-0.8.0-py2.7.egg\pc_ble_driver_py\config.py", line 48, in sd_api_ver_get raise RuntimeError('Connectivity IC identifier conn_ic_id is not set') RuntimeError: Connectivity IC identifier conn_ic_id is not set

*************************************

the error informations tell us that the conn_ic_id is not set .so, open the file :config.py, and change the code __conn_ic_id__ = None to __conn_ic_id__ = "NRF52" .

RE: nrfutil dfu ble failed to open Win 10

Harshil — Wed, 21 Mar 2018 19:55:43 GMT

Same issue here, Thanks for that info man! But r u kidding me? My workplace gives standard access to users....this means that I have to walk to the IT admin everytime I need to do the DFU...LOL.

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Wed, 01 Feb 2017 07:18:16 GMT

Hi Rocky, thanks for letting us know. I will report this internally.

RE: nrfutil dfu ble failed to open Win 10

Rocky Liang — Wed, 01 Feb 2017 06:46:06 GMT

Hi guys, I encountered the same issue today while doing dfu update via nrfutil. I was just sending the zip file provided in the SDK12.2 examples\dfu\ble_dfu_send_hex\test_images_update_nrf52 The bootloader and the SoftDevice on the targeted device are programed with the provided Hex files. I was able to do a dfu via the nRF Connector app on a PC and smartphones. However, when using nrfutil, I encountered this error:

File "c:\python27\lib\site-packages\pc_ble_driver_py\ble_driver.py", line 126, in wrapper
    raise NordicSemiException('Failed to {}. Error code: {}'.format(wrapped.__name__, err_code))
pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 13

At the end of the day, I resolved my issue - I need to run the command prompt as an administrator. This step should be mentioned or even highlighted in the chapter 5 of the nrfutil v2.0.0 User Guide.

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Mon, 19 Dec 2016 10:03:27 GMT

Yes, you need a nRF51 dongle or another nRF51/52 DK connected to the production station. You can configure nrfutil to connect to a device with a specific name or address, see the screenshot below.

RE: nrfutil dfu ble failed to open Win 10

Kent — Sat, 17 Dec 2016 08:39:20 GMT

Aha I see. Yes I already tried "nRF Toolbox apps for Android/iOS to perform DFU" and it works fine. Im trying to do the same from a production station "linux/pc" with DFU. So I need one "BLE dongle flashed with the connectivity firmware" connected to the production station, and then use nrfutil to do dfu to the manufactured nrf5 unit. In this case the dongle may be adverticed with "DfuTest" and the other with company name. So I need to create a custum bootloader with another advertice name to test this I guess?.

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Mon, 12 Dec 2016 09:46:48 GMT

Hi Kent, you edited the comment before I managed to answer. You wrote

"... in order to use it to perform DFU over BLE on another nRF5x device." Do I need two separate units? I only have one nRF52DK that I laborate with.

Yes, you need two separate units if you want to use the pc-ble-driver to perform DFU. One that is used as a BLE dongle flashed with the connectivity firmware that communicates with the pc-ble-driver on your computer. The second unit is the nRF52 device that runs your application, bootloader and SoftDevice. Since you only have one unit, then I recommend that you use our nRF Connect or nRF Toolbox apps for Android/iOS to perform DFU instead.

RE: nrfutil dfu ble failed to open Win 10

Kent — Sat, 10 Dec 2016 09:16:25 GMT

Hello

As you said, pc-nrfutil-1.5.0 have the correct pc-ble-drive for dfu example using SDK v12.1.0 ? So my problem is I cant install it correctly and therefore I cant even run "nrfutil --help" or anything. Should I avoid SDK v12.1.0 and use nrfutil2.0.0?

The reason I left out the -f option was otherwise the softdevice and bootloader already in place will be erased and then in next step nrfutil2.0.0 will timeout probably due to there is no bootloader anymore.

For the moment I dont have any success so I will try to use pc-nrfutil-1.5.0 in linux environment...

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Tue, 06 Dec 2016 10:05:09 GMT

Hi Kent, nrfutil uses the pc-ble-driver,a serialization API for our SoftDevices that needs Nordic Hardware( either a nRF51 Dongle or nRF51/52 DK) flashed with the connectivity firmware connected to your computer in order to use it to perform DFU over BLE on another nRF5x device. Thus when you use the following command

nrfutil dfu ble -ic NRF52 -n "DfuTest" -p COM5 -pkg dfu_test_app_hrm_s132.zip

nrfutil will look for a nRF5x device connected to COM5, that is flashed with the connectivity firmware, and then use it to send the DFU packets to a second nRF5x device that is advertising as "DfuTarg" (by default) since you have not specified which device it should update. You can upload the connectivity firmware by adding the -f option to the command above, i.e.

 nrfutil dfu ble -ic NRF52 -n "DfuTest" -p COM5 -f -pkg dfu_test_app_hrm_s132.zip

RE: nrfutil dfu ble failed to open Win 10

Kent — Sat, 03 Dec 2016 09:43:04 GMT

Sorry Im not sure what you mean. Im new on this. I think "NO" on that question.

"connectivity firmware supplied with the pc-ble-driver" ?

Is that a step I missed before I flash: ...\nRF5_SDK_12.1.0_0d23e2a\examples\dfu\ble_dfu_send_hex\test_images_update_nrf52\dfu_test_softdevice_bootloader_s132.hex that I program with: "nrfjprog -f NRF52 –-chiperase --program dfu_test_softdevice_bootloader_s132.hex --verify"

And then trying to flash: ...\nRF5_SDK_12.1.0_0d23e2a\examples\dfu\ble_dfu_send_hex\test_images_update_nrf52\dfu_test_app_hrm_s132.hex that I program with: "nrfutil dfu ble -ic NRF52 -n "DfuTest" -p COM5 -pkg dfu_test_app_hrm_s132.zip"

I was thinking everything are prepared after installing i.e nRF5x-Command-Line-Tools Installer.

When I was running nRFgo Studio I remember something is uppdated to the connected nRF52 DK device first time.

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Fri, 02 Dec 2016 12:29:57 GMT

Yes, but do you have one nRF device that is connected to you computer running the connectivity firmware supplied with the pc-ble-driver in addition to the nRF52 DK that is flashed with the bootloader and the s132 SoftDevice?

RE: nrfutil dfu ble failed to open Win 10

Kent — Thu, 01 Dec 2016 17:33:58 GMT

I did use nRF51DK(s130) before and now using nRF52DK(s132+bootloader). With nRF51DK I only use nRFgo Studio. With nRF52DK I also start using nfrjprog and nrfutil.

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Thu, 01 Dec 2016 12:19:57 GMT

Hi Kent, do you have a nRF51 Dongle or another nRF52 DK that runs the connectivity firmware in addition to the nRF52 DK with the S132 and the bootloader right?

RE: nrfutil dfu ble failed to open Win 10

Kent — Tue, 29 Nov 2016 19:07:22 GMT

Seems pc_ble_driver_py-0.8.0 still be installed even if I force it away :(

I now did the following:

delete entry in %USERPROFILE%\AppData\Local\pip\cache
delete existing pc-nrfutil-1.5.0 folder
unzip pc-nrfutil-1.5.0 and cd to it
uninstall existing Python and delete the folder
install Python 2.7.12
open cmd.exe as administrator
python -m pip install --no-cache-dir -r requirements.txt
python nordicsemi/main.py

but still get the:

Traceback (most recent call last): File "nordicsemi/main.py", line 50, in from nordicsemi.dfu.dfu_transport_ble import DfuTransportBle File "C:\Users\4light\Downloads\pc-nrfutil-1.5.0\pc-nrfutil-1.5.0\nordicsemi\dfu\dfu_transport_ble.py", line 48, in from pc_ble_driver_py.ble_driver import BLEDriver, BLEDriverObserver, BLEUUIDBase, BLEUUID, BLEAdvData, BLEGapConnParams, NordicSemiException File "C:\Python27\lib\site-packages\pc_ble_driver_py\ble_driver.py", line 63, in nrf_sd_ble_api_ver = config.sd_api_ver_get() File "C:\Python27\lib\site-packages\pc_ble_driver_py\config.py", line 48, in sd_api_ver_get raise RuntimeError('Connectivity IC identifier conn_ic_id is not set') RuntimeError: Connectivity IC identifier conn_ic_id is not set

The log from the "python -m pip install --no-cache-dir -r requirements.txt"

Collecting six>=1.9 (from -r requirements.txt (line 1)) Downloading six-1.10.0-py2.py3-none-any.whl

Collecting pyserial>=2.7 (from -r requirements.txt (line 2)) Downloading pyserial-3.2.1-py2.py3-none-any.whl (189kB) 100% |################################| 194kB 4.9MB/s

Collecting enum34>=1.0.4 (from -r requirements.txt (line 3)) Downloading enum34-1.1.6-py2-none-any.whl

Collecting click>=6.0 (from -r requirements.txt (line 4)) Downloading click-6.6-py2.py3-none-any.whl (71kB) 100% |################################| 71kB 663kB/s

Collecting ecdsa>=0.13 (from -r requirements.txt (line 5)) Downloading ecdsa-0.13-py2.py3-none-any.whl (86kB) 100% |################################| 92kB 980kB/s

Collecting behave (from -r requirements.txt (line 6)) Downloading behave-1.2.5-py2.py3-none-any.whl (109kB) 100% |################################| 112kB 5.7MB/s

Collecting protobuf (from -r requirements.txt (line 7)) Downloading protobuf-3.1.0.post1-py2.py3-none-any.whl (347kB) 100% |################################| 348kB 5.4MB/s

Collecting pc-ble-driver-py>=0.6.1 (from -r requirements.txt (line 8)) Downloading pc_ble_driver_py-0.8.0.tar.gz (13.1MB) 100% |################################| 13.1MB 5.7MB/s

Collecting parse>=1.6.3 (from behave->-r requirements.txt (line 6)) Downloading parse-1.6.6-py2-none-any.whl

Collecting parse-type>=0.3.4 (from behave->-r requirements.txt (line 6)) Downloading parse_type-0.3.4.tar.gz (62kB) 100% |################################| 71kB 6.0MB/s

Requirement already satisfied (use --upgrade to upgrade): setuptools in c:\python27\lib\site-packages (from protobuf->-r requirements.txt (line 7))

Collecting wrapt (from pc-ble-driver-py>=0.6.1->-r requirements.txt (line 8)) Downloading wrapt-1.10.8.tar.gz

Collecting future (from pc-ble-driver-py>=0.6.1->-r requirements.txt (line 8)) Downloading future-0.16.0.tar.gz (824kB) 100% |################################| 829kB 6.0MB/s

Installing collected packages: six, pyserial, enum34, click, ecdsa, parse, parse-type, behave, protobuf, wrapt, future, pc-ble-driver-py

Running setup.py install for parse-type ... done Running setup.py install for wrapt ... done Running setup.py install for future ... done Running setup.py install for pc-ble-driver-py ... done

Successfully installed behave-1.2.5 click-6.6 ecdsa-0.13 enum34-1.1.6 future-0.16.0 parse-1.6.6 parse-type-0.3.4 pc-ble-driver-py-0.8.0 protobuf-3.1.0.post1 pyserial-3.2.1 six-1.10.0 wrapt-1.10.8

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Tue, 29 Nov 2016 07:19:46 GMT

You have to uninstall nrfutil v0.8.0 as it will casue a conflict with the newer version. Also check that your path variable is pointing to the correct version.

RE: nrfutil dfu ble failed to open Win 10

Kent — Mon, 28 Nov 2016 19:45:17 GMT

Thanks! yes Im running cmd.exe as administrator.

I installed nrfutil v1.5.0 by the following as admin:

install Python 2.7.12
python -m pip install --upgrade pip
python -m pip install -U setuptools
python -m pip install pyinstaller
unzip pc-nrfutil-1.5.0 and cd to it
python setup.py install
pyinstaller nrfutil.spec

running as admin "nrfutil --help" but gets:

I have already run:

nrfjprog -f NRF52 –-chiperase --program dfu_test_softdevice_bootloader_s132.hex --verify

RE: nrfutil dfu ble failed to open Win 10

bjorn-spockeli — Mon, 28 Nov 2016 09:16:07 GMT

You're running cmd.exe as administrator right? However, you have to use nrfutil v1.5.0 if you're using the Secure Bootloader from SDK v12.1.0, please see our Github page, here is the link.