Secure Buttonless DFU Problem on nRF52832 Soft Device 112

[AliMahmood123]

Hello

I am facing problem from many days on buttonless DFU.

Whoever from Nordic approaches kindly give a customized solution rather than other links. I have almost gone through all the links with none exactly matching my issue. I will be really thankful.

I am trying to perform Buttonless DFU on nRF52832 512 kB version on nRF DK. I am using SDK 112 v7 (the latest one) and latest versions of nRF util, etc.. as well. Although I am using SDK 16.

My first act was to convert my application from s132 to S112 on nRF52832 a few months ago as I was using default ble_app_blinky as my base. A kind person from nordic helped me on the issue since the memory mapping on s112 pca10040 example is that of nRF52810

Now for DFU, I am supposed to convert the bootloader s112 example on nRF52810 to nRF52832 by editing the project file for library and memory mapping right?

I used the following links:

1) https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.3.0%2Flib_bootloader.html

2) https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader#h61sjziauupw1j397q9s9ldr01q4j6d5

3) https://devzone.nordicsemi.com/f/nordic-q-a/41386/guide-to-allocate-the-amount-of-ram-rom-i-need

and my project application  + BL + setting + SD oombined well using merge hex. It  went into DFU mode on start up and I started OTA 

OTA package is received successfully and after 100% OTA the DK rebooted and nRF log said bootloader not found:

My guess is something is wrong in my conversions as I am trying to convert from s112 nRF52810 examples to nrf 52832 the following projects:

1) Bootloader S112 example

2) I OTA ble_app_blinky s112 example and change it's memory mapping and nrf52832 libraries as we have to keep the same soft device in OTA

Please note from above screenshot that my OTA is fully complete (100%)

I am using the following memory mapping:

1) Bootloader example: nrf52832 s112

linker_section_placement_macros="FLASH_PH_START=0x0;FLASH_PH_SIZE=0x80000;RAM_PH_START=0x20000000;RAM_PH_SIZE=0x10000;FLASH_START=0x78000;FLASH_SIZE=0x6000;RAM_START=0x20005968;RAM_SIZE=0xa698"

linker_section_placements_segments="FLASH RX 0x0 0x80000;RAM RWX 0x20000000 0x10000;uicr_bootloader_start_address RX 0x10001014 0x4;uicr_mbr_params_page RX 0x10001018 0x4;mbr_params_page RX 0x0007E000 0x1000;bootloader_settings_page RX 0x0007F000 0x1000"

2) Base Application FW - nrf52832 s112

linker_section_placement_macros="FLASH_PH_START=0x0;FLASH_PH_SIZE=0x80000;RAM_PH_START=0x20000000;RAM_PH_SIZE=0x10000;FLASH_START=0x26000;FLASH_SIZE=0x5a000;RAM_START=0x200022f0;RAM_SIZE=0xdd10"

linker_section_placements_segments="FLASH RX 0x0 0x80000;RAM RWX 0x20000000 0x10000"

3) The OTA package - S112 nRF52832

linker_section_placement_macros="FLASH_PH_START=0x0;FLASH_PH_SIZE=0x80000;RAM_PH_START=0x20000000;RAM_PH_SIZE=0x10000;FLASH_START=0x26000;FLASH_SIZE=0x5a000;RAM_START=0x20001ae0;RAM_SIZE=0x4520"

linker_section_placements_segments="FLASH RX 0x0 0x80000;RAM RWX 0x20000000 0x10000"

Here are my nrfutil commands -

1) Bootloader settings and hex merges

BOOTLOADER SETTINGS
nrfutil settings generate --family NRF52 --application E_MCB_Project.hex --application-version 1 --bootloader-version 1 --bl-settings-version 2 bootloader_settings.hex

nrfutil settings generate --family NRF52 --application E_MCB_Project.hex --application-version 1 --bootloader-version 1 --bl-settings-version 2 --app-boot-validation VALIDATE_GENERATED_CRC --softdevice s112_sd.hex --sd-boot-validation VALIDATE_GENERATED_CRC bootloader_settings.hex

SETTING AND BOOTLOADER MERGE
mergehex -m secure_bootloader.hex bootloader_settings.hex -o bootloaderAndSettings.hex

PACKAGE HEX FROM ABOVE
mergehex -m bootloaderAndSettings.hex s112_sd.hex -o random.hex

PACKAGE HEX FROM ABOVE 2
mergehex -m random.hex E_MCB_Project.hex -o package_EMCB.hex

Here are commands I used for OTA package

echo "## Creating a FW.zip package that can be used to update the FW on the DK"

nrfutil pkg generate --application blinky_112_2.hex --application-version 61 --application-version-string "1.0.61" --hw-version 52 --sd-req 0xCD --sd-id 0xCD --softdevice s112_sd.hex --key-file private.pem fw81_MCB.zip

echo.

sd_112. hex is default  soft devicce 112 I just renamed it rest is self explanatory.

I have provided complete details and I need help on this. Please provide a customized solution and please dont divert me to other links. Its not a huge issue the OTA happens perfectly  but after reboot it cannot find the bootloader

I am assuming its something withbootloader settings or bootloader memory mapping

Regards

Ali

[Edvin]

Hello,

Try to use only --application-version 61. You are not supposed to use both --application-version and --application-version-string in the same packet. So try to use just one of them.

You can't update a major softdevice version without updating the bootloader. You should actually probably always update the bootloader when you update the softdevice, so that you are 100% sure that you have a working pair. The bootloader depends on a compatible softdevice to be able to advertise and receive packets for the new application.

Does it work to update the application only? (to another application using the same version of the softdevice)

When you try to do SD+BL+APP, what was the old present softdevice version, what is the new one, and what command do you use to generate the DFU image?

BR,

Edvin

[AliMahmood123]

Hello Edvin

I will try without application version string.

Oh so you mean to say we cant do APP + SD we need to do APP + SD + BL always. That makes sense why it wasn't working with APP + SD

Yes it does work when I OTA application only; and yes the soft device versions were same of both - S112

I wanted to know if the steps were right. I changed linker addresses according to S112 on nRF52832 using info center links in the post. Please tell me if this was corrrect.

On SD + BL + APP it seemed to send the TWO zip packages around 2-3 times (It said uploading 1 0f 2 and then 2 of 2) and then repeat.

The old soft device was S112 and new one was S132 (OTA package). It worked on S132 SD + BL + APP with repetitions like I said but it didn't work at all with S112 in OTA package.

The command was this:

nrfutil pkg generate --application E_MCB_Project_CRC.hex --application-version 61 --application-version-string "1.0.61" --bootloader secure_bootloader.hex --bootloader-version 1 --hw-version 52 --sd-req 0xCD --sd-id 0xCD --softdevice s112_132.hex --key-file private.pem fw87_BL_SD_APP.zip

secure_bootloader. hex is s112 project with all changes and details in original post please and the soft device is S132 default hex file.

The code on the DK had S112

Ali

[Vidar Berg]

Hello Ali,

I'm glad to hear that it finally worked.

AliMahmood123 said:

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

 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.

[AliMahmood123]

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:

 

Vidar Berg said:

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

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

[Vidar Berg]

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).

AliMahmood123 said:

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??

 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.

[AliMahmood123]

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

[Vidar Berg]

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:

pca10040_s112_ble.zip

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

[AliMahmood123]

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,

[Vidar Berg]

That's good to hear!

AliMahmood123 said:

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.

 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)

[AliMahmood123]

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

[Vidar Berg]

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?

[AliMahmood123]

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)