Secure bootloader upload failed: UNKNOWN (8202)

RE: Secure bootloader upload failed: UNKNOWN (8202)

Luccas — Tue, 25 Jul 2017 13:10:14 GMT

Sorry for delay. Have you solved? You could try to use an earlier softdevice.

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Mon, 10 Jul 2017 07:07:16 GMT

I used 0x8C but then I'm on an earlier softdevice (3.0.0). All my code is Open Source if you need to check: github.com/.../Espruino but I can't help you out further. Perhaps one of the Nordic Employees would be able to help if you posted a new question - as it looks like they may not get notified for comments?

RE: Secure bootloader upload failed: UNKNOWN (8202)

khan_khan — Sat, 08 Jul 2017 09:41:03 GMT

as i am using 132_nrf52_5.0.0-1.alpha_softdevice so sq-req 0x9D must be used for that .you CAN CHECK your sd-req by using this command: nrfutil pkg generate --help

RE: Secure bootloader upload failed: UNKNOWN (8202)

Luccas — Fri, 07 Jul 2017 21:05:49 GMT

I used --sd-req 0x8C in my case.

RE: Secure bootloader upload failed: UNKNOWN (8202)

khan_khan — Fri, 07 Jul 2017 19:43:40 GMT

i did everything according to your instructions. i am using nRF5_SDK_13.0.0-1.alpha_055eef3 ands132_nrf52_5.0.0-1.alpha_softdevice and used nRF5_SDK_13.0.0-1.alpha_055eef3\examples\dfu\bootloader_secure\pca10040\arm5_no_packs_build example for secure DFU using OTA . but everytime i try i get the same 8202 error when i use nRF toolbox app and "[DFU] Remote DFU error: REMOTE DFU OPERATION FAILED" when I use Nrf connect app . I used following command .

nrfutil pkg generate --hw-version 52 --application-version 1 --application nrf52832_xxaa_s132.hex --sd-req 0x9D --key-file my_secret_private_key.pem app_dfu_package.zip .

But this zip package created doesnt upload . when i use the following command

nrfutil dfu ble -f -pkg app_dfu_package.zip -ic NRF52

i got this error

pc_ble_driver_py.exceptions.NordicSemiException: Timeout. Target device not found.

what should i do now ?

RE: Secure bootloader upload failed: UNKNOWN (8202)

Luccas — Thu, 17 Nov 2016 14:46:48 GMT

I was getting the same errors, fix it with this answer! Thanks!

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Tue, 18 Oct 2016 14:20:07 GMT

Right, thanks to Bjørn's help outside the forum we've sorted this.

It looks like 8202 is the Nordic App's error code for InvalidObject, which in turn means the package couldn't be verified, because of some key problem.

You get much more information by trying to upload from your PC with

nrfutil dfu ble -f -pkg you_package.zip

In my case, the keys were fine. The issue was actually the compilation of micro-ecc, which requires the following definitions:

-DuECC_ENABLE_VLI_API -DuECC_VLI_NATIVE_LITTLE_ENDIAN=1 -DuECC_SQUARE_FUNC=1 -DuECC_SUPPORTS_secp256r1=1 -DuECC_SUPPORT_COMPRESSED_POINT=0 -DuECC_OPTIMIZATION_LEVEL=3

If you were using Nordic's provided toolchain you wouldn't have this, but I was building myself with GCC and Makefiles, so I didn't spot this buried in external/micro-ecc/nrf52_armgcc/armgcc/Makefile.

Now when that is done, I succeeded in uploading one of the example hex files with the example public key, but I got OperationFailed when uploading my own file.

It turns out that when making the package with nrfutil pkg generate you need to provide the correct hardware version --hw-version 52. I'd been using 1.

RE: Secure bootloader upload failed: UNKNOWN (8202)

parco — Mon, 10 Oct 2016 14:25:10 GMT

Hi Gordon, I'm not sure if this will help, but I had this exact issue until I removed the --debug-mode flag and specified actual version requirements during the creation of the init package.

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Fri, 07 Oct 2016 12:19:52 GMT

Ok, same error when using the pre-built DFU hex file. I don't seem to have the Nordic private key so I can't test uploading a properly signed ZIP, but I'd kind of hoped that if that were the problem there would have been a more helpful error message.

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Thu, 06 Oct 2016 12:23:57 GMT

8202 = 0x200A, which is NRF_ERROR_SOC_BASE_NUM+10... However there isn't one of those (only errors up to 9). Maybe it's something internal?

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Wed, 05 Oct 2016 15:03:10 GMT

No, the device is staying in bootloader mode(in fact you can reconnect). So the fact that bank_code is currently 0 won't be an issue, as all being well the bootloader should just upload the binary and then overwrite it?

RE: Secure bootloader upload failed: UNKNOWN (8202)

bjorn-spockeli — Wed, 05 Oct 2016 14:44:20 GMT

Is the device resetting to the application when it disconnects or is it still in bootloader mode? If you want the bootloader to start the application without having to perform DFU, then yes, s_dfu_settings.bank_0.bank_code must be set to NRF_DFU_BANK_VALID_APP (i.e. 0x01). Yes, the bank code will be overwritten when you update the application.

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Wed, 05 Oct 2016 13:24:55 GMT

I'm using nRF toolbox, 1.18.4. nRF connect 4.5.0 just connects and for a few seconds and then disconnects without any warning. I haven't tried the test images, but I'd imagine that they would be ok. Is it vital that bank_0.bank_code is 1? I'd sort of assumed that all that info would get overwritten after a successful DFU?

RE: Secure bootloader upload failed: UNKNOWN (8202)

bjorn-spockeli — Wed, 05 Oct 2016 13:18:34 GMT

Do you see the same behavior with the test images that are provided in the SDK? Which Android app are you using ( nRF COnnect or nRF Toolbox) and which version is it?

RE: Secure bootloader upload failed: UNKNOWN (8202)

Gordon — Wed, 05 Oct 2016 13:15:16 GMT

Yes, it's all SDK12. I have a merged image with an application that works, an a self-compiled secure bootloader that runs when power is applied with a button pressed. The issue I'm having is when I try to use that bootloader to upload a new application binary over BLE (also SDK12 - in fact identical to the firmware that's already on there and working).

RE: Secure bootloader upload failed: UNKNOWN (8202)

bjorn-spockeli — Wed, 05 Oct 2016 13:07:12 GMT

Just to clarify: You're not trying to update from the legacy bootloader from SDK v11 to the Secure bootloader from SDK v12? Your only trying to flash the Secure bootloader and an application as a merged image with the valid app flag set right?