nrfutil.exe, cannot generate keys

[Stef]

Hello, I'm trying to generate DFU keys with the nrfutil.exe tool from Master Control Panel 3.10.0. I always get errors....

C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.10.0.14\nrf>n rfutil keys generate private.pem Usage: nrfutil keys [OPTIONS] KEY_FILE

Error: Got unexpected extra argument (private.pem)

C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.10.0.14\nrf>nrfutil keys generate private.pem Usage: nrfutil keys [OPTIONS] KEY_FILE

Error: Got unexpected extra argument (private.pem)

C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.10.0.14\nrf>nrfutil keys generate Traceback (most recent call last): File "main.py", line 303, in File "click\core.pyc", line 664, in call File "click\core.pyc", line 644, in main File "click\core.pyc", line 991, in invoke File "click\core.pyc", line 837, in invoke File "click\core.pyc", line 464, in invoke File "main.py", line 115, in keys main.nRFException: Use either gen-key or show-vk.

What am I doing wrong ? I'm working with Windows7.

Regards,

Stef

[bjorn-spockeli]

Which SDK and SoftDevice version are you using? Are you using the legacy bootloader from SDK v11, the experimental signing bootloader from SDK v10 or the Secure Bootloader from SDK v12?

[Stef]

Hello,

I'm using:

• SDK 11.0.0
• softdevice s132_nrf52_2.0.0

But why would the choice of the bootloader have an impact on the key generation ?

Regards,

Stéphane

[bjorn-spockeli]

It does not, but the legacy bootloader in SDK v11.0.0 does not support signed firmware images, so you cannot use the keys generated with nrfutil from MCP v3.10.0. Or have you ported the experimental bootloader with signing from SDK v10.0.0 to SDk v11.0.0. In both cases I strongly recommend that you migrate to SDK v12.0.0 adn the Secure Bootloader, and use the newest version of nrfutil, found here, to generate the keys.