Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

PeterInStillwater — Wed, 01 Jul 2020 16:03:19 GMT

Hung - 

I'm at a loss as to what happened here.  I used your string:

nrfutil pkg generate --hw-version 52 --application-version 0 --application ble_app_blinky_pca10040_s132.hex --sd-req 0xCB --key-file private.key app_dfu_package.zip

modified --sd-req 0xCB for SD package

And programmed the bootloader via Segger IDE, after erasing memory.


It worked two times in a row.  

Here's the log file and app zip file.

Have you seen this before - I swear I went through your example at least a half dozen times with no success.
That's why I tried the second approach.

Anyway - thanks for your assistance on this.  I have to noodle this out and see what I'm doing different.

devzone.nordicsemi.com/.../DFU_5F00_070120.log devzone.nordicsemi.com/.../ble_5F00_app_5F00_blinky_5F00_pca10040_5F00_s132.zip

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

Hung Bui — Wed, 01 Jul 2020 15:22:03 GMT

Hi Petter,
I'm not sure why you generate bootloader setting ? You don't really need to generate bootloader setting if you don't do DFU with bonding. And that requires modification in the application as well.

Please try to test without bootloader setting. Please follow my blog as linked in the earlier reply.

In addition, you are using "--family NRF5240 " this is wrong. You are working on nRF52832 QFAA chip. You should use NRF52 in this case. (but you don't need to generate bootloader setting if you don't have a special need, for example combine application and bootloader, or do DFU with bonding)

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

PeterInStillwater — Wed, 01 Jul 2020 14:45:21 GMT

I'm using nrfjprog version 10.9.0 -

The family version was with respect to nrfUtil

Here are the files you requested:

devzone.nordicsemi.com/.../3618.app_5F00_dfu_5F00_package.zip devzone.nordicsemi.com/.../0131.settings.hex devzone.nordicsemi.com/.../MDFU.bat
devzone.nordicsemi.com/.../1256.s132_5F00_nrf52_5F00_7.0.1_5F00_softdevice.hex devzone.nordicsemi.com/.../my_5F00_bootloader.hex devzone.nordicsemi.com/.../ble_5F00_app_5F00_blinky_5F00_pca10040_5F00_s132.hex

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

Hung Bui — Wed, 01 Jul 2020 14:06:41 GMT

I assume the family argument you quoted was from nrfjprog ? Which version are you using ? The current version is v10.9.0 and you don't have to select NRF52840, you only have 4 options NRF51, NRF52, NRF53 and NRF91. I'm not sure why you used "NRF52QFAB" but not "NRF52QFAA" ?

Could you send us your hexes you used (softdevice, bootloader, application) and the .zip file you used for testing ?

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

PeterInStillwater — Wed, 01 Jul 2020 12:56:50 GMT

Thank You Hung -

I just checked out your link and that is actually where I started my learning process. Those were the steps I followed in my first post.

The second post are steps I followed off of a different link (see link above)

Both yielded the same results.

Note that I have tried this on three nrf52DKs. All have nrf52832 QFAA micros.

Also, I'm only running the example code provided with SDK16 - the only contribution I've made to the process is to run nrftuil, merghex and nrfproj.

I'll look into your last paragraph this afternoon.

Could it be related to the:

"--family: Device family, match with your chip. If you have nRF52840 you have to use NRF52840 instead of NRF52." ?

I used --family NRF52QFAB

Thanks Again!!

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

Hung Bui — Wed, 01 Jul 2020 12:04:23 GMT

Hi Peter,

Thanks for very detailed description.

From the log I can find that the image has been transferred successfully and the hash has been verified correctly so it's not the issue with the init packet. However, there is something strange is that when it's rebooting it's trying to erase the bootloader setting at address 0x00000002 (you can see that in the log). This is definitely wrong. The bootloader setting should be at address 0x7E000. Erasing address 0x0000002 will clear the MBR and brick the application/bootloader.

This is quite strange. I have made a blog here with step by step instruction to test DFU. It's for SDK v15 but should work in newer SDK as well.
Please try to test using a fresh copy of the SDK.

In the last log by the softdevice it's also crashed when trying to write to the bootloader setting, I suspect there could be something wrong there. Please try to test on a different board as well.

Error 0x00004002 means NRF_FAULT_ID_SDK_ASSERT. But it doesn't explain much if you don't build the softdevice with debug mode. You can change the optimization level to 0 and add DEBUG into the preprocessor symbol. You may need to move the softdevice down in the flash to make more space for it, build with no optimization and debug make the bootloader bigger.

RE: Simple, Secure DFU setup Fails to start - Received a fault id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

PeterInStillwater — Tue, 30 Jun 2020 17:34:35 GMT

P.S. As part of my exercise I did perform the steps outlined in this post:

https://devzone.nordicsemi.com/f/nordic-q-a/53662/secure-dfu-successful-but-application-not-loading?tempkey=17317c1d-ed9d-426c-b0f9-c2ad74347be1

nrfutil settings generate --family NRF52QFAB --application ble_app_blinky_pca10040_s132.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 settings.hex

mergehex.exe --merge settings.hex secure_bootloader_ble_s132_pca10040_debug.hex --output my_bootloader.hex

nrfutil pkg generate --hw-version 52 --application-version 3 --application ble_app_blinky_pca10040_s132.hex --sd-req 0xCB --key-file private.key app_dfu_package.zip

nrfjprog.exe -e

nrfjprog.exe --program s132_nrf52_7.0.1_softdevice.hex --verify

nrfjprog.exe --program my_bootloader.hex --verify -r


And received the exact same RTT results as in my original post.  

<error> app: Received a fault! id: 0x00004002, pc: 0x00000000, info: 0x2000FF30

Just in case anyone thought I should try that out.

THANKS AGAIN - 
If it wasn't for this forum I (and I suspect many others) would not be able to work with these devices.  

Peter