Hello,
I am working on nRF51822-QF-AAFQ chip using SDK 12.3.0 in IAR embedded workbench.
My question is, can I impliment DFU in nrf51822 chip?
If possible suggest Starting RAM address of application and bootloader.
Please give me suggestion as soon as possible.
Thanks & regards,
Urvisha Andani
Hello Urvisha,
I suggest you take a look at the SDK12.3.0\examples\dfu\bootloader\secure\pca10028. This guide is also useful, if you have not worked with our bootloader before.
Please be aware that there is a bug in the latest version of nrfutil (the tool that you use to generate keys and DFU images). The public keys that are generated is missing a comma. Please see this ticket for details. So just add that comma, or use nrfutil v5.0.0 instead.
Best regards,
Edvin
I suggest you take a look at the SDK12.3.0\examples\dfu\bootloader\secure\pca10028. This guide is also useful, if you have not worked with our bootloader before.
Thank you for reply, I use same bootloader.
In this when I add custom service in my application I successfully download firmware through bootloader but after that from application I can not able to jump in bootloader.
In my application I use five application timer.
So can I Implement DFU in nRF51822?
Please be aware that there is a bug in the latest version of nrfutil (the tool that you use to generate keys and DFU images). The public keys that are generated is missing a comma. Please see this ticket for details. So just add that comma, or use nrfutil v5.0.0 instead.
I am using nrfutil 5.1.0
Hello,
Urvisha Andani said:I am using nrfutil 5.1.0
As long as you are able to compile the bootloader with the custom made dfu public_key.c that is fine.
Urvisha Andani said:In this when I add custom service in my application I successfully download firmware through bootloader but after that from application I can not able to jump in bootloader.
So your application is starting up after you have updated via the bootloader, right?
When you have a valid application (verified by the bootloader), then the bootloader will typically run into the application, since you don't want it to require a DFU on every startup.
There are two main ways to "activate" DFU mode again when you have a valid application:
1: You can assign a button to trigger the bootloader to start the DFU mode instead of starting the application. If you check the nrf_dfu_enter_check() function in nrf_dfu.c, you can see that it checks whether or not a button is pressed. So basically, if this button is held when you restart the device, it will enter DFU mode.
2: There is something called a buttonless_dfu_service in the SDK. If you try to create a DFU image based on the experimental_ble_app_buttonless_dfu example in the SDK\examples\ble_peripheral, this has a custom service that can be used to trigger DFU mode. See how it is implemented.
Best regards,
Edvin
So your application is starting up after you have updated via the bootloader, right?
yes, my application is starting
I follow below step to download HEX file first time,
1) Download softdevice HEX using nRF studio.
2) Download bootloader HEX file using nRF studio.
3) connect device with nRF connect mobile application.
4) through DFU option i download .ZIP file which is create using below command,
nrfutil pkg generate --hw-version 51 --application-version 1 --application app.hex --sd-req 0x87 --key-file private.key app_dfu_package.zip
5) Successfully download and device gets disconnect with mobile application and start advertisement of application
6) connect device with application.
7) Enable notification of dfu service and send request from write.
8) Device gets disconnect with application and jump in to bootloader but not start advertisement.
so give me suggestion to solves this problem
There is something called a buttonless_dfu_service in the SDK. If you try to create a DFU image based on the experimental_ble_app_buttonless_dfu example in the SDK\examples\ble_peripheral, this has a custom service that can be used to trigger DFU mode. See how it is implemented.
I am using buttonless dfu and in this I am not getting any problem.
Also I add custom service in buttonless dfu code and in this I am not getting problem.
I attached map file for RAM address,
1)bootloader map file
secure_dfu_secure_dfu_ble_s130_pca10028.map
2) map file for buttonless dfu
ble_app_buttonless_dfu_pca10028_s130.map
3) map file for custom application
So does you application do the same when you receive it receives the command to go to the bootloader through the buttonless dfu service?
Have you included ble_dfu.c to your project? If so, did you do any changes to that file?
I guess it resets, if it disconnects, but make sure that is_waiting_for_disconnection is set to true in ble_dfu.c.
Can you send a copy of your ble_dfu.c file if you did any changes?
Basically what the buttonless dfu service needs to do is to write some new bootloader settings with the s_dfu_settings.enter_buttonless_dfu = true; and then wait for that to finish, disconnect, and reboot.
Does your application do that? If you haven't modified the ble_dfu.c it should do that by default.
You say that it stays in the bootloader, but doesn't advertise. Have you verified that by scanning for it with another device after it is in DFU mode?
