Secure Buttonless DFU Problem on nRF52832 Soft Device 112

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Mon, 17 Aug 2020 09:59:45 GMT

Excellent! I'm glad to hear that it works now, thank you for the update.

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Mon, 17 Aug 2020 09:38:26 GMT

Hi Vidar

It worked!

Thanks again for all your help. No one has helped me on Nordic forum this much. I really think you went out of the way to help me.

God Bless you!

[quote userid="4240" url="~/f/nordic-q-a/63362/secure-buttonless-dfu-problem-on-nrf52832-soft-device-112/264734"]Yes, but it's not the same problem. This wouldn't have been limited to GPIOTE interrupts if the interrupt forwarding mechanism was incorrectly configured.[/quote]

Yes I get it now. I did your changes and it worked absolutely fine

[quote userid="4240" url="~/f/nordic-q-a/63362/secure-buttonless-dfu-problem-on-nrf52832-soft-device-112/264734"] What about P0.21, is it being used as a GPIO in your app? SDK examples enable the pinreset functionality on this pin by default (ie builds with CONFIG_GPIO_AS_PINRESET flag)[/quote]

No Vidar, I am not using this, however it's a great piece of information to have.

Once again really thanks. I am moved by your help.

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Mon, 17 Aug 2020 06:55:56 GMT

Hi Ali,

[quote user="AliMahmood123"]Only GPIOTE interrupts are the problem. As I shared in the links above for other soft devices, other people had this issue too. I couldnt see for S112 [/quote]

Yes, but it's not the same problem. This wouldn't have been limited to GPIOTE interrupts if the interrupt forwarding mechanism was incorrectly configured.

[quote user="AliMahmood123"]I will share results on what you shared. Thanks a lot again. However I dont think it would help as it is not going into DFU mode and I noticed these are basically LEDS which will be used once it goes in DFU mode; But my application successfully boots but interrupts dont work[/quote]

What about P0.21, is it being used as a GPIO in your app? SDK examples enable the pinreset functionality on this pin by default (ie builds with CONFIG_GPIO_AS_PINRESET flag)

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Sun, 16 Aug 2020 11:21:37 GMT

Hi Vidar, Sorry for catching up late

I have some timers for periodic self tests and SDK scheduler based state machine. It works absolutely fine.

Only GPIOTE interrupts are the problem. As I shared in the links above for other soft devices, other people had this issue too. I couldnt see for S112 😞

I hope this can be solved quickly.

I will share results on what you shared. Thanks a lot again. However I dont think it would help as it is not going into DFU mode and I noticed these are basically LEDS which will be used once it goes in DFU mode; But my application successfully boots but interrupts dont work

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Fri, 14 Aug 2020 06:06:45 GMT

Hi,

You need to comment the led functions as you said.

Disabling LEDs and Button:

diff --git a/components/boards/custom_board.h b/components/boards/custom_board.h
index 597ff69..3c8915c 100644
--- a/components/boards/custom_board.h
+++ b/components/boards/custom_board.h
@@ -47,7 +47,7 @@ extern "C" {
 #include "nrf_gpio.h"
 
 // LEDs definitions for PCA10040
-#define LEDS_NUMBER    4
+#define LEDS_NUMBER    0
 
 #define LED_START      17
 #define LED_1          17
@@ -67,7 +67,7 @@ extern "C" {
 #define BSP_LED_2      LED_3
 #define BSP_LED_3      LED_4
 
-#define BUTTONS_NUMBER 4
+#define BUTTONS_NUMBER 0
 
 #define BUTTON_START   13
 #define BUTTON_1       13
diff --git a/examples/dfu/secure_bootloader/main.c b/examples/dfu/secure_bootloader/main.c
index 0c72b38..44ebde3 100644
--- a/examples/dfu/secure_bootloader/main.c
+++ b/examples/dfu/secure_bootloader/main.c
@@ -106,14 +106,14 @@ static void dfu_observer(nrf_dfu_evt_type_t evt_type)
         case NRF_DFU_EVT_DFU_FAILED:
         case NRF_DFU_EVT_DFU_ABORTED:
         case NRF_DFU_EVT_DFU_INITIALIZED:
-            bsp_board_init(BSP_INIT_LEDS);
+            /*bsp_board_init(BSP_INIT_LEDS);
             bsp_board_led_on(BSP_BOARD_LED_0);
             bsp_board_led_on(BSP_BOARD_LED_1);
-            bsp_board_led_off(BSP_BOARD_LED_2);
+            bsp_board_led_off(BSP_BOARD_LED_2);*/
             break;
         case NRF_DFU_EVT_TRANSPORT_ACTIVATED:
-            bsp_board_led_off(BSP_BOARD_LED_1);
-            bsp_board_led_on(BSP_BOARD_LED_2);
+            /*bsp_board_led_off(BSP_BOARD_LED_1);
+            bsp_board_led_on(BSP_BOARD_LED_2);*/
             break;
         case NRF_DFU_EVT_DFU_STARTED:
             break;
diff --git a/examples/dfu/secure_bootloader/pca10040_s112_ble_debug/config/sdk_config.h b/examples/dfu/secure_bootloader/pca10040_s112_ble_debug/config/sdk_config.h
index 501ed20..e72d2d8 100644
--- a/examples/dfu/secure_bootloader/pca10040_s112_ble_debug/config/sdk_config.h
+++ b/examples/dfu/secure_bootloader/pca10040_s112_ble_debug/config/sdk_config.h
@@ -99,7 +99,7 @@
 // <e> NRF_BL_DFU_ENTER_METHOD_BUTTON - Enter DFU mode on button press.
 //==========================================================
 #ifndef NRF_BL_DFU_ENTER_METHOD_BUTTON
-#define NRF_BL_DFU_ENTER_METHOD_BUTTON 1
+#define NRF_BL_DFU_ENTER_METHOD_BUTTON 0
 #endif
 // <o> NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN  - Button for entering DFU mode.

[quote user="AliMahmood123"]just not the interrupts[/quote]

Only GPIOTE interrupts, or are there other interrupts that don't work either?

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Fri, 14 Aug 2020 05:32:41 GMT

Hi Vidar

I did try that. But removing LED pins in pca10040.h gave me led errors in main.c. I will try it again today by commenting out LED on functions.

I'll check P0.21 as well.

Yes advertising works infact even DFU works completely fine just not the interrupts

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Fri, 14 Aug 2020 05:26:36 GMT

Hi,

I don't think this has to do with interrupt forwarding. Did you disable the button and LED configurations in the bootlaoder project as I asked you to? Also, 1. does your board use P0.21 as a reset pin? 2. do other parts of the app work (e.g. does it start BLE advertising, etc)?

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Thu, 13 Aug 2020 13:06:20 GMT

Hi Vidar. I dug deep into my app. Yes its on custom board but we already had that covered according to link you have shared, taking inspiration from the DK board examples pinout configuration.

I have searched multiple posts online as well. Most notable is this although of different SoC:

https://devzone.nordicsemi.com/f/nordic-q-a/16398/gpio-interrupts-not-working-with-bootloader

Im pretty sure the bootloader must be doing something as my app works fine when standalone. You are well versed with the bootloader project. I used the one you sent in fact. Could you please help me in solving this issue?

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Thu, 13 Aug 2020 10:29:57 GMT

Hi Vidar
Thanks again for the prompt replies.

I'll look into it. Meanwhile I have a general question. When I run the application standalone, the interrupts work.

When I merge APP + SD + BL + Settings and flash it. The BL successfully boots the application as desired but interrupts dont work.

If the BL booted the application successfully, then the application is now basically running standalone right without any dependency on the bootloader? Im a bit baffled as to how the interrupts arent working when I merge

Keeping the issue aside, when bootloader boots the application, are there any dependencies such as GPIO interrupts which the bootloader may effect? Or the application is really running standalone

Thanks again

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Wed, 12 Aug 2020 14:47:31 GMT

The example I sent is configured to run on the PCA10040 (nRF52 DK) and I didn't change any of the default bootloader settings. See "Using the SDK with other boards" for general information on how you can adapt SDL examples for different boards.

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Wed, 12 Aug 2020 14:31:15 GMT

Vidar, I haven't initialized any pin configs in the bootloader project. I compiled it as it is you gave me

None of the interrupts work Vidar, I am using 2 interrupts with the button handler module. One for motor interrupts if manual locked / unlocked and the other for RFID.

None register an interrupt (i know this through J-link prints)

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Wed, 12 Aug 2020 14:24:49 GMT

Yes, you should probably remove all of the pin configurations in the bootloader. What pin number do you use for the RFID interrupt line? That's the only one that stops working with the bootloader, right?

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Wed, 12 Aug 2020 14:19:48 GMT

Hello Vidar. Thanks for the prompt response.

No I am not customizing the bootloader. However I am customizing a lot of GPIOs in my application. Would that effect?

I think the bootloader might be doing something as when I run the application standalone it works fine.

Anything specific I can look into??

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Wed, 12 Aug 2020 14:05:28 GMT

That's good to hear!

[quote user="AliMahmood123"]I noticed that OTA works but somehow my system has stopped giving me interrupts. I have a RFID Reader connected to one of the GPIOS and im using the button handler to register interrupt. They are not working at all.[/quote]

Are you configuring any IOs in your bootloader that may conflict with this interrupt pin? Remember that the bootloader configures some IOs by default (for led indication and button press)

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Wed, 12 Aug 2020 13:45:38 GMT

Hi Vidar. It worked!

Thanks a lot again for sending. However, I have to bother you again, we have another problem.

I noticed that OTA works but somehow my system has stopped giving me interrupts. I have a RFID Reader connected to one of the GPIOS and im using the button handler to register interrupt. They are not working at all.

However when I erase the flash and simply build and run my application (without bootloader and settings), the interrupts work fine. I have a dc motor on one of the GPIOs as well.

How come it doesnt work when i flash APP + SD + BL + Settings and use it as my base application?

I hope you can help me out with this it looks like the final nail in the coffin,

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Tue, 11 Aug 2020 06:55:28 GMT

Hi Ali,

It's not that much trouble. I just do an automatic search&replace of S132/s132 (case sensitive) with s112/S112. Here, I've done the same for the non-debug configuration:

devzone.nordicsemi.com/.../pca10040_5F00_s112_5F00_ble.zip

I expect it to work, but I've not verified it.

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Mon, 10 Aug 2020 17:46:21 GMT

Hi Vidar

I will do that and let you know. I hope it works. Because I really dont want to bother you again to send me another project with non debug changes.

I will keep you posted

Thanks again

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Mon, 10 Aug 2020 11:45:16 GMT

Hi Ali,

The main difference with the debug bootloader is that it enables debug logging over RTT and that it lets you skip version validation (see Validation).

[quote user="AliMahmood123"]And how to bring about changes in the non debug version? I can copy the text editor and just change the flash start from 72000 to 78000 right??[/quote]

I would suggest making a copy of the existing "pca10040_s132_ble" bootloader configuration and make it into a pca10040_s112_ble configuration, the same as I did for the debug bootloader I sent you earlier.

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Fri, 07 Aug 2020 09:46:11 GMT

Hi Vidar

Many thanks for the detailed explanation. I think my base application was fine because I did DFU on that as well. It worked same for modified blinky as it worked for without.

There was some problem with bootloader as you mentioned in:

[quote userid="4240" url="~/f/nordic-q-a/63362/secure-buttonless-dfu-problem-on-nrf52832-soft-device-112/263553"]2) It seemed like you were building to project for nRF52810 instead of nRF52382, so that could be one explanation[/quote]

I did the same. Just made S112 changes in the text editor. Perhaps I missed something.

Anyways now that all is done. Could you please tell me the differences between the debug and non debug version? I am assuming I cannot use the debug version for production obviously.

And how to bring about changes in the non debug version? I can copy the text editor and just change the flash start from 72000 to 78000 right??

If there is something else please let me know. I will share my results with you via non debug version in some days.

Enjoy the weekend though. I think you will reply on Monday

Thanks again

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Fri, 07 Aug 2020 08:55:29 GMT

Hello Ali,

I'm glad to hear that it finally worked.

[quote user="AliMahmood123"]I had some problems in DFU after your steps (invalid object error) because of invalid signature. Turns out I was signing with .pem key. When I created new keys nrfutil generated the private key in .key format. I dont know how this works but DFU used to work with me with .pem format[/quote]

Both formats should work. I used *.pem to generate the test image as you can see from the command I used:

nrfutil pkg generate --debug-mode --application ble_app_blinky_pca10040_s112.hex --key-file private.pem ble_app_blinky.zip

1) I did not modify the SDK itself. And the bootloader 'pca10040_s112_ble_debug' configuration is nearly identical with the original 'pca10040_s132_ble_debug' one. I just made a copy of the original "secure_bootloader_ble_s132_pca10040_debug.emProject" file and used a text editor to replace the occurense of "s132" with "s112".

The blinky app required a bit more work as I had to add the buttonless mechanism. I modified main.c and added the following source files:

    <folder Name="nRF_SVC">
      <file file_name="../../../../../../components/libraries/bootloader/dfu/nrf_dfu_svci.c" />
    </folder>
    <folder Name="nRF_DFU">
      <file file_name="../../../../../../components/ble/ble_services/ble_dfu/ble_dfu.c" />
      <file file_name="../../../../../../components/ble/ble_services/ble_dfu/ble_dfu_bonded.c" />
      <file file_name="../../../../../../components/ble/ble_services/ble_dfu/ble_dfu_unbonded.c" />
    </folder>

Pre-processor definitions:

c_preprocessor_definitions="NRF_DFU_SVCI_ENABLED;BL_SETTINGS_ACCESS_ONLY;NRF_DFU_TRANSPORT_BLE=1"

And include paths:

c_user_include_directories="../../../../../../components/libraries/bootloader;../../../../../../components/libraries/bootloader/ble_dfu;../../../../../../components/libraries/bootloader/dfu"

2) It seemed like you were building to project for nRF52810 instead of nRF52382, so that could be one explanation.

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Thu, 06 Aug 2020 14:36:25 GMT

Hi Vidar. It worked! Thank God.

Thanks a lot for your helped Vidar. It means a lot to me that you sent me a custom bootloader application and all your help that helped me get through this. I'm indebted to you. Thanks a lot to Hung as well.

I had some problems in DFU after your steps (invalid object error) because of invalid signature. Turns out I was signing with .pem key. When I created new keys nrfutil generated the private key in .key format. I dont know how this works but DFU used to work with me with .pem format

However, thanks a lot once again. Should I verify this answer?

Also, I have a few questions before we part ways

1) What did you do different with the ble debug application? Perhaps some changes in the SDK because i could notice some changes

2) I did OTA with your blinky application as well as my own. It worked perfectly for both so looks like there was some problem with bootloader application. I have spent more than a month on this. I would like to know what went wrong

Warm Regards

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Wed, 05 Aug 2020 08:11:52 GMT

Hi Ali,

The bootloader also uses the BOOTLOADER_SETTINGS_ADDRESS and NRF_MBR_PARAMS_PAGE_ADDRESS symbols defined in nrf_dfu_types.h, and the fact that it says the settings page is *backed* up to 0x2E000 indicates that you are still building the project for NRF52810_XXAA.

Attached below is the bootloader project I configured earlier and a version of the ble_app_blinky example thatI have modified to include the buttonless DFU mechanism. Please try DFU with these. Test image is included so you don't have to generate the zip file.

devzone.nordicsemi.com/.../nRF5_5F00_SDK16.0.0_5F00_examples.zip

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Mon, 03 Aug 2020 13:58:10 GMT

Hi Vidar. I tried your project's hex file.I merged it with my application and ran it. Same result as before.

I really need guidance here. Why would it go to 2E000 address when I set address as 7E000. This issue is being delayed at work as well.

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

AliMahmood123 — Sun, 02 Aug 2020 21:59:08 GMT

Hi Vidar

I like this Idea, I shall try it and update you soon. I hope you read the OP and all the prevailing discussions.

Your idea was great Vidar, but can I get back to Hung with this if this doesnt work? He knows complete history would save you a lot of trouble?

Ali

RE: Secure Buttonless DFU Problem on nRF52832 Soft Device 112

Vidar Berg — Fri, 31 Jul 2020 11:11:04 GMT

Hi Ali,

[quote user="AliMahmood123"]One thing I see is that in both prints it is finding bootloader settings in 2E000 even when I have placed in 7E000 accordingly. Perhaps that issue.[/quote]

The settings address is wrong as you say, but did you mean to write 0x2F000? That's the default BL settings address if you build the project for the nRF52810 (see nrf_dfu_types.h).

And with regards to porting, it's easier to take an existing nRF52832+s132 and change out the Softdevice than it is to take a 52810+s132 project and port it to nrf52832. I just did that for 'pca10040_s132_ble_debug' configuration in SDK 16.0.0, see attached below. Can you give this project a try?

devzone.nordicsemi.com/.../pca10040_5F00_s112_5F00_ble_5F00_debug.zip