Adding DFU to NCS example on nRF52832

RE: Adding DFU to NCS example on nRF52832

Edvin — Fri, 19 Mar 2021 08:07:36 GMT

I actually had no idea that this app existed. The more you know... 🙂

Ok, I see. Without having tested this one, I am not sure it will replace my goto: nRF Connect for iOS, but I will give it a try. I guess this is targeting only DFU, while the nRF Connect for iOS is a more all in one app.

I'll try to look into the last questions later today.

BR,

Edvin

RE: Adding DFU to NCS example on nRF52832

nrbrook — Thu, 18 Mar 2021 13:07:03 GMT

[quote userid="26071" url="~/f/nordic-q-a/72135/adding-dfu-to-ncs-example-on-nrf52832/300674#300674"]What app are you using that applies this filter?[/quote]

www.nordicsemi.com/.../nRF-Connect-Device-Manager

RE: Adding DFU to NCS example on nRF52832

Edvin — Thu, 18 Mar 2021 13:04:51 GMT

[quote user="nrbrook"]5. No I don't, but I'm just pointing it out as the App clearly expects SMP UUID to be advertised by default as the switch is hidden, and it doesn't seem to be advertised by default, so there may be a bug there[/quote]

What app are you using that applies this filter? I am using nRF Connect for iOS. If you are using nRF Connect for Android, then it must be different. Or are you using nRF Toolbox -> DFU? In that case, I can recommend nRF Connect for Android/iOS, as you can connect to all devices, interact with all of it's characteristics, and perform DFU.

Let me get back to question 6. This is about the same that I struggled with when I tested this in the peripheral_uart example, and I don't know how to work around it yet. I just wanted to answer this before I get the time to look into this again. I will leave this ticket open until I have had the chance to look into it.

BR,

Edvin

RE: Adding DFU to NCS example on nRF52832

nrbrook — Thu, 18 Mar 2021 09:04:57 GMT

Hi Edvin,

1. No I haven't, but I'm sure that would work – although as you recognize, isn't a proper solution that can easily be shared with other developers etc.

2,3,4 ok thanks

5. No I don't, but I'm just pointing it out as the App clearly expects SMP UUID to be advertised by default as the switch is hidden, and it doesn't seem to be advertised by default, so there may be a bug there

6. Yes this is without changing the private key. I can't build without using the default key. I tried creating an app_update.bin with a later CONFIG_FW_INFO_FIRMWARE_VERSION but the results are the same (I think).

First attempt on the "Image" tab on nRF Connect Device Manager using "test and confirm" seems successful (it says "Upload complete") however this happens almost instantly which seems too fast to transfer 200+kb, and all I get from the firmware is "I: Swap type: none", it doesn't appear to restart.
The "start" button is then disabled so I can't try again
On the "Files" tab I can try to upload the firmware image (not sure if this is the same thing) but then it says "Remote error: Unrecognized (7)".

7. Thanks

8. Already in touch, thanks

RE: Adding DFU to NCS example on nRF52832

Edvin — Thu, 18 Mar 2021 08:35:53 GMT

Hello,

1. Have you tried just replacing the actual priv.pem file in the SDK? I know it isn't ideal, but for now it may be easier just to get things up and running. I don't have anything to point to, but I remember a colleague saying it was quite the hazzle to make it point to another key. Sorry. I don't have the details.

2. I agree. Unfortunately, NCS is still quite new, so we have not gotten all the nice to have guides up and running at this point in time. Zephyr is a 3rd party product, so we need to get familiar ourselves as well.

3. Thanks for the input. If you find other things that are missing, feel free to say it here, and I can take it onward to the person who will eventually write the guide.

4. (same as 3.).

5. Do you strictly need it to advertise the SMP UUID? Typically, you would choose a more prominent UUID, that is more descriptive of your device so that the central knows what to connect to.

6. Did you get this before you started changing the private key as well?

7. I think this config can be used the firmware version that you are looking for: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/CONFIG_FW_INFO_FIRMWARE_VERSION.html?highlight=firmware%20version#cmdoption-arg-CONFIG_FW_INFO_FIRMWARE_VERSION

8. That would be my guess, but for roadmap questions like this, you need to check with our RSM (Regional Sales Manager) for your area. Since this is a public ticket, please send me a PM with the link to this ticket if you want the contact information for our RSM for your area.

BR,
Edvin

RE: Adding DFU to NCS example on nRF52832

nrbrook — Tue, 16 Mar 2021 16:57:00 GMT

Hi Edvin,

Thanks I've got a bit further.

Using the built in key works. I don't know why specifying my own key is failing. As per my linked solution, I'm doing this in CMakeLists.txt:
```
set(mcuboot_key_file ${CMAKE_CURRENT_LIST_DIR}/priv.pem)
set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE "\"${mcuboot_key_file}\"")
```
Any idea?
That guide helped, but it would be great to have a more visible and generic (for all boards) guide covering the whole process like the Getting started with Nordic's Secure Bootloader guide
The guide is missing "CONFIG_MCUMGR=y" from the project config

The guide is missing what files need to be included:

#ifdef CONFIG_MCUMGR_CMD_OS_MGMT
#include "os_mgmt/os_mgmt.h"
#endif
#ifdef CONFIG_MCUMGR_CMD_IMG_MGMT
#include "img_mgmt/img_mgmt.h"
#endif
#include <mgmt/mcumgr/smp_bt.h>

It doesn't seem to advertise the SMP UUID, In nRF Connect Device Manager I have to disable "Only devices advertising SMP UUID". Then I can connect and perform echo.
When I try to upload app_update.bin I get "Remote error: Unrecognized (7)"
How do you specify what the firmware version is? Or will it just blindly perform the update with any app_update.bin?
Is bootloader update planned for the future on nRF52?

RE: Adding DFU to NCS example on nRF52832

Edvin — Thu, 11 Mar 2021 10:45:18 GMT

Hello,

Sorry for the slow response. I have spent about a day trying to add a bootloader to another project, and I almost made it. I failed due to some flash conflicts in the projects.

Have you tested the smp_svr example description found here?

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf52.html#fota-upgrades

I didn't see the same error as you did when I tried to follow the guide. It claims that there are some missing references to the key. Where is this key located? And is that file included in your project? Usually, you need to include both the header files, and add some definitions in the prj.conf file to add a module.

app/libapp.a(keys.c.obj):(.rodata.bootutil_keys+0x0): undefined reference to `rsa_pub_key'
undefined reference to `rsa_pub_key_len'

Where are these used, and where are they defined? Is that .h/.c file included in your project properly? A quick search shows me that it is found in bootloader\mcuboot\boot\cypress\MCUBootApp\keys.c. Is that intentional? I don't think the bootloader for nRF52 should use the cypress files by default. Did it work before you tried to set your own key? By using the default key in NCS? I am not saying you should use that specific key in the end, but just to see that things are working before you start modifying too much.

BR,

Edvin

RE: Adding DFU to NCS example on nRF52832

nrbrook — Mon, 01 Mar 2021 15:47:42 GMT

Hi Edvin, no I haven't got this working in any previous version.

I set the key as in my solution here: https://devzone.nordicsemi.com/f/nordic-q-a/71892/cmake-warning-using-default-mcuboot-key-it-should-not-be-used-for-production/295833#295833

I am following these steps: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_bootloader.html#adding-a-bootloader-chain-to-your-application

I tried adding both immutable bootloader and MCUBoot but it seems there is not enough flash to do that on nRF52832 (or the bootloader configuration for the board is incorrect) as I got a flash overflow error at build time, so I switched to just using MCUBoot.

RE: Adding DFU to NCS example on nRF52832

Edvin — Mon, 01 Mar 2021 15:42:48 GMT

Hello,

Did you follow some guide to get to this point? If so, what guide did you follow. Let me know, and I can see if I can reproduce the issue you are seeing. If you didn't have a guide, did you do anything other than just adding the config CONFIG_BOOTLOADER_MCUBOOT=y in your prj.conf file? I see that you are using NCS v1.5.0. Did it work in a previous NCS version, or is this your first attempt?

Best regards,

Edvin