Hi,
I am using sdk_17 and nrf52810. I have build a bootloader from the examples folder(examples/dfu/secure_bootloader/pca10040e_S112_ble) for my device. After flashing, the device enters into dfu mode. When I select the required zip package from my phone for updating, it simple just gets disconnected. I am using the proper private and public keys for creating the files.
Hi,
Can you share the log from nRF Connect on mobile (or other), which could indicate the issue? It is sometimes also very useful to see the RTT log from the bootloader, but to get that you need to flash a debug bootloader project (example bootloader project with the suffix "_debug").
The logs from my mobile app indicates->
[DFU]Remote DFU error:
EXTENDED ERROR
[DFU]Details: SD version failure
(code =7)
I have also checked the version of the softdevice(S112) its 0xc4.
"nrfutil pkg generate --hw-version 52 --application-version 1 --application ble_app_template_pca10040e_s112.hex --sd-req 0xc4 --key-file private.key app_dfu_package.zip"
This is the command that I have used to generate the zip file.
And I have also tried this nrf52832 EVK board as well, but the result remains the same.
Hi,
This means that the SoftDevice ID you require (0xC4) is not the ID of the SoftDevice that is currently flashed to the board. You either use/add the ID of the currently used SoftDevice id to the --sd-req option (if compatible), or include the SoftDevice in the ugpradei mage as well. (Note that if you need to update to a new SoftDevice you also need to update the bootloader, as it has dependencies on the SoftDevice.)
Yes, what you have said is right. I have verifies the SD ID using "nrfjprog --memrd 0x300c" command and it returned "0x0000300C: FFFF0103", which means the ID is "0x103". I generated the DFU package using this ID. Now the nRF Connect is throwing "INSUFFICIENT RESOURCES" as error.
Hi,
0x103 is not a valid ID (too large). Which exact SoftDevice version are you using?
s112_nrf52_7.2.0_softdevice.hex This is the SD version I am using.
Hi,
I see. Then 0x0103 is the correct ID as you write. My mistake.
The INSUFFICIENT RESOURCES error typically means that there is not enough flash available, so the new firmware cannot fit. If you are updating the application only this means that either the new application is in fact too large to fit, or it is too large to fit with dual bank update, and you have configured the bootloader to force dual bank updates by setting NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES to 1 in the bootloader's sdk_config.h file.
Hi,
I see. Then 0x0103 is the correct ID as you write. My mistake.
The INSUFFICIENT RESOURCES error typically means that there is not enough flash available, so the new firmware cannot fit. If you are updating the application only this means that either the new application is in fact too large to fit, or it is too large to fit with dual bank update, and you have configured the bootloader to force dual bank updates by setting NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES to 1 in the bootloader's sdk_config.h file.
No I haven't configured the NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES macro. Its zero.
From nrf connect programmer tool I can see the memory address maps to verify whether my application size is larger or not. The application starting address is 0x00019000 to 0x000266EF(Limit is 0x00028000), that means my application size is under 60KB and it should fit perfectly.
Hi,
Where does the limit of 0x00028000 come from? What is the bootloader start address, and how many pages below the bootloader are reserved for application data (configured by NRF_DFU_APP_DATA_AREA_SIZE in the bootloader's sdk_config.h file)? Perhaps you can share details of your flash memory layout?
From the nordic infocenter(https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_nrf52%2Fstruct%2Fnrf52.html) I came to know about the 0x00028000 address. NRF_DFU_APP_DATA_AREA_SIZE is 8192. I'll share you my hex files for your clarification.
ble_app_buttonless_dfu_pca10040e_s112.hexsecure_bootloader_ble_s112_pca10040e.hex
Hi,
I see. Your bootloader starts at 0x2A000 and you have two pages reserved for user data before that, starting at 0x28000? And the size of S112 7.2.0 is 1000 kB, so the application start ddress is 0x19000. In sum this means that the maximum size of your application is 0xF000 – 60 kB, as you write. That should fit.
Can you confirm that you are only trying to update the application, or does the upgrade image also include a SoftDevice and/or bootloader?
Yes, you are right, 60kB is enough. My application size is 55kB and it should fit perfectly. I am updating only the application and it does not include any SoftDevice. I'll include my application hex file for your reference here.(5417.ble_app_buttonless_dfu_pca10040e_s112.hex this is not the exact example code of buttonless dfu application. I have added an ADC feature along with it.)
