The problem of Uploading Zip file with DFU

RE: The problem of Uploading Zip file with DFU

micmind — Sat, 30 Nov 2019 14:06:45 GMT

the issue is fixed now.

it is caused by tool "nrfutil". the vesion in my test is 6.0.0a1 before. Maybe this version has bug.

after I updated it with the version 6.0.0 <published in date 29/10/2019> , ota can be done without any error.

So I think it must be the issue of tool nrfutil.exe.

by the way, nrfutil.exe can be download from website <github.com/.../releases>

RE: The problem of Uploading Zip file with DFU

speedycat — Fri, 29 Nov 2019 12:44:33 GMT

YoungMin: Since you eventually made it working, can you try to generate `dfu_public_key.c` with the older v3.5.1 version of nrfutil and see if that file also works. i.e. the bytes are in correct order? See my reply to Hung Bui above. It would be good for NordicSemi to fix this problem for others.

RE: The problem of Uploading Zip file with DFU

speedycat — Fri, 29 Nov 2019 12:40:05 GMT

There is something wrong with how nrfutil generates the `dfu_public_key.c` in newer versions of nrfutil. We used lot of time getting the examples run with our own keys, and eventually stumbled upon this thread which solved our issue: https://devzone.nordicsemi.com/f/nordic-q-a/52946/nrfutil-and-dfu---invalid-object . Using the older v3.5.1 of nrfutil generates `dfu_public_key.c` with the bytes in correct order for bootloader to work.

I don't know how it suppose to work, but something inconsistent.

RE: The problem of Uploading Zip file with DFU

YoungMin — Thu, 28 Nov 2019 11:24:58 GMT

thank you for your reply.

i already solved this problem.

it is the problem key file -> .c code file

i dont know why nrfutil command work strange.

so i use command "nrfutil keys display --key pk --format hex ...\Desktop\pip\private_key.pem"

and, make the .c key file myself.

RE: The problem of Uploading Zip file with DFU

YoungMin — Thu, 28 Nov 2019 11:20:51 GMT

Yep, it was solved.

i dont know why the wrong .c key file appear, when i use the command nrfutil(nrfutil keys display --key pk --format code ...\Desktop\pip\private_key.pem --out_file private_key.c)

the problem is wrong .c key file.

so, what should you check the key between .c file and generated code (it can show through command "nrfutil keys display --key pk --format hex ...\Desktop\pip\private_key.pem" in cmd)

RE: The problem of Uploading Zip file with DFU

Hung Bui — Thu, 28 Nov 2019 09:50:03 GMT

Hi CUI,

We need to debug the bootloader to check what went wrong here.
Please try testing with the bootloader _debug version where you can have the RTT log.

Make sure the log level is set to DEBUG in sdk_config.h

There are several reasons the DFU return INVALID_OBJECT. One of them is the signature is not correct , see nrf_dfu_validation_signature_check() in nrf_dfu_validation.c .
Another option could be that the init packet was corrupted.

There are about 5-6 places where NRF_DFU_RES_CODE_INVALID_OBJECT returned. If the logging doesn't help, you can add breakpoints at those place to check what returned.

Since you mentioned that "only the example target file in folder “examples\dfu\secure_dfu_test_images\ble\nrf52832” can be OTA " , most likely you haven't updated the bootloader with your own PUBLIC key.
In this line, you should generate an output public key file: nrfutil keys display --key pk --format code private.pem

For example:

nrfutil keys display --key pk --format code private.key --out_file public_key.c

Then you include the public_key.c in your bootloader, replacing the dfu_public_key.c default in the bootloader.

RE: The problem of Uploading Zip file with DFU

micmind — Wed, 27 Nov 2019 15:50:02 GMT

yes, I tried more than 20 times, with different solution base on official guide and others.

I can't figure out what is the problem eventually.

my test bed is

1. IAR 8.30.1

2. nRF5_SDK_15.3.0

3. Chip: NRF52832

4.version of make is 3.81

5. version of urfutil is 6.0.0a1

7. version of mergehex is 8.5.0

8. and version of arm-none-eabi-gcc is 9.2.1

I compiled bootloader project in foler "examples\dfu\secure_bootloader\pca10040_ble" and the debug version.

and the app is come from "examples\ble_peripheral\ble_app_buttonless_dfu\pca10040".

at the previous several times, I didn't change anything of these project to verify the dfu and OTA.

all my test are failed at the end.

but, only the example target file in folder “examples\dfu\secure_dfu_test_images\ble\nrf52832” can be OTA 。

I don't whether it is the issue related with "micro-ecc" . but there is no any error reported during my test.

And I found the example bootloader proect called the ecc lib of the folder "external\micro-ecc\nrf52hf_iar\armgcc\micro_ecc_lib_nrf52.a". Help document from sdk said it is currect if I enable hardware FPU.

And i also solved the issue "-short-char' related with "wchar_t" is 16bit or 32bit.

besides, i tried with different application version and --bl-settings-version, no one can give me a success result.

i also checked the help of nrfutil, --bl-settings-version should be 2 for SDK15.3.0, and --sd-req should 0xB7. So I think my script might be no problem.

I also tried the buttonless example with different version and other app example such as uart or hrs.but no one can be successfully ota.

here is my script related this process. I really don't know where I was wrong.

::step1 generateo private key-file
nrfutil keys generate private.pem
nrfutil keys display --key pk --format code private.pem

::step2
nrfutil settings generate --family NRF52 --application app_ota.hex --application-version-string 0.0.0 --bootloader-version 0 --bl-settings-version 2 settings.hex

::step3
mergehex.exe --merge s132_nrf52_6.1.1_softdevice.hex bootloader.hex   --output ota_sd_boot.hex
mergehex.exe --merge app_ota.hex ota_sd_boot.hex settings.hex         --output ota_all.hex

del /f ota_sd_boot.hex

::step4
nrfjprog.exe --family NRF52 --eraseall
nrfjprog.exe --family NRF52 --program ota_all.hex --verify
nrfjprog.exe --family NRF52 --reset

::step5
nrfutil pkg generate --hw-version 52 --sd-req 0xB7 --application-version 1 --application app_ota.hex --key-file private.pem app_ota.zip

here is error message form IOS and android during OTA.

RE: The problem of Uploading Zip file with DFU

Hung Bui — Wed, 27 Nov 2019 13:28:50 GMT

Hi,

Could you try follow my step by step guide here and check if you have the same issue ?
Could you try setting application version to 1 instead of 0 ?

RE: The problem of Uploading Zip file with DFU

micmind — Wed, 27 Nov 2019 03:15:16 GMT

i met this issue for several days. still not fix it.....do you have any suggest ???