nrfutil and dfu - invalid object

[SirKazik]

Hello. I'm reviving an old project (nrf51 and 12.3.0 SKD with sd130 2.0.1). Unfortunately bootloader is not working properly. It worked just fine at the beginning of the year (last commit is from 10th February of current year). Now when I'm trying to update firmware I'm getting an INVALID OBJECT error. I've tracked it down to line 308 in dfu_req_handling.c from 12.3.0 SDK. To be specific: uECC_vli_equal in uECC_verify returns 0. I suspect that something changed in nrfutil. I'm using: nrfutil settings generate --family NRF51 --application <PATH_TO_APP_HEX> --application-version 0 --bootloader-version 0 --bl-settings-version 1 boot_settings.hex --no-backup to create settings hex file, and nrfutil pkg generate --hw-version 51 --application-version 5 --application --sd-req 0x87 --key-file --app-boot-validation NO_VALIDATION app_dfu_package.zip to generate a package. As i was debugging, signature and public key seemed OK. Maby there is something different in hash calculation? I really can't figure it out. I'm using nrfutil version 5.2.0

[AndreasF]

Hi.

To be specific: uECC_vli_equal in uECC_verify returns 0.

 So the signature verification fails then.

Could you try to perhaps downgrade nrfutil?

Best regards,

Andreas

[SirKazik]

I did. It works. I used 3.5.1 version. Did something change with hash calculation?

[AndreasF]

Hi.

Great to hear that it works, I'm not sure if anything has changed, probably it has since downgrading worked.

Best regards,

Andreas

[speedycat]

I found this post and this made me able to do DFU. `./nrfutil.exe keys display --key pk --format code` displays the code for the dfu_public_key.c file with different byte orders, comparing nrfutil v3.5.1 vs v6.0.0a1. Using the code shown by the old nrfutil made DFU work (however, the updated firmware did not work - I need to find out what's going on. We use a Laird DVK652 instead of PCA10040). But I was able to transfer the .zip file from mobile phone to microcontroller when using code from old nrfutil.

I've been using the `secure_bootloader/pca10040_s132_debug` example from newest NordicSemi SDK16, using Segger Embedded Studio.

[Kenneth]

Please create a new devzone case for this issue.

Best regards,
Kenneth