SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

[iotlight]

We used nRF5_SDK_15.0.0_a53641a and nrf5_SDK_for_Mesh_v2.0.0_src.

We are following DFU quick start guide http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v0.10.0%2Findex.html

For nRF52:

mesh-sdk$ nrfutil dfu genpkg --application bin/blinky/blinky_nrf52832_xxAA_s132_5.0.0.hex \

--company-id 0x00000089 \

--application-id 1 \

--application-version 2 \

--key-file private_key.txt \

--sd-req 0x009D \

--mesh dfu_test.zip

We used "--company-id 0x00000089 \" to match Step 2 public key:

{

"bootloader_config": {

"bootloader_id": 1,

"bootloader_version": 1,

"company_id": 89,

"application_id": 1,

"application_version": 1,

"public_key": "ed09a58df6db5cd15b8637304f31d31f4042492ed7c7e4839fbe903f260a2ba1a855e92b72885825481ad56282bcf549ad7455ec46f000f0f62d97eeec883ba6"

}

}

The hex we used is C:\Nordic\nRF5_SDK_15.0.0_a53641a\mesh_sdk\bin\blinky\blinky_nrf52832_xxAA_s132_5.0.0.hexblinky_nrf52832_xxAA_s132_5.0.0.hex

We got ValueError, please see attached screen shot. 

Please advise.  Thanks

[Bjørn Kvaale]

You were fine to skip step 8, as the mesh stack has already been built before being uploaded as a zip file to the nordic semi homepage. Did you use the dfu_nrf52832_xxAA_s132_6_0_0 segger project to build the dfu example? If so, then you will need to make sure all of the steps before 8 also use the s132 softdevice version 6. I believe you have used version 5 up until this point. Did you flash the program via nrfjprog or via segger embedded studio (SES) directly? If you used SES, then you will have flashed the softdevice to the device again, which is not a good idea. I would build the example with SES & then program the hex file located in the build folder via nrfjprog (like shown in step 8).

I believe the reason you are getting the serial port error is that you are not running the cmd prompt as an administrator. You can start command prompt as an administrator by searching for "cmd", right click on the command prompt icon & run as administrator.