Cannot update zip file after enabling dfu

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Thu, 29 Oct 2020 13:15:00 GMT

Hi,

Thanks. I have tested your projects and see the same as you. Upgrade fails with an INSUFFICIENT RESOURCES error. This is unexpected, as the app clearly fits. I verified on a different project with a debug bootloader that putting data in the last available page before the app data reserved can work with the SDK 17 bootloader, and I do not see what is different in your case.

Debugging it is a bit difficult as it is a tight fit and the bootloader is built with size optimization, so I have not made progress in understanding what causes this issue yet.

Regarding reducing the reserved app data to 4 kB, this will not work if the application use FDS. FDS needs at least two pages - 8 kB (1 swap page and 1 data page).

RE: Cannot update zip file after enabling dfu

Vimalnath — Thu, 29 Oct 2020 10:42:03 GMT

go to->E:~\nRF5_SDK_17.0.2_\examples\dfu\secure_bootloader\pca10040e_s112_ble\ses for bootloader project.

And go to->~\nRF5_SDK_17.0.2_\examples\ble_peripheral\ble_app_buttonless_dfu\pca10040e\s112\ses for application project file.

RE: Cannot update zip file after enabling dfu

Vimalnath — Thu, 29 Oct 2020 10:26:19 GMT

oops.. my mistake. Complete project->devzone.nordicsemi.com/.../nRF5_5F00_SDK_5F00_17.0.2_5F00_.zip.And can you tell me the use of Application data area present above the application layer. By default it takes 8kB from the flash. I tried to reduce it to 4kB. Then I was able to update the application zip file, but after the update the device is not responding. From the nrf document I came to know that the application data size should be a multiple of the flash page size, which is 4kB.

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Thu, 29 Oct 2020 08:35:49 GMT

Hi,

Can you include everything used in the bootloader project, not just the project files itself? I am particularly interested in the bootloader's sdk_config.h, but other parts may also be relevant.

RE: Cannot update zip file after enabling dfu

Vimalnath — Wed, 28 Oct 2020 15:19:00 GMT

This is my project file->devzone.nordicsemi.com/.../ses.rar.

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Wed, 28 Oct 2020 14:54:57 GMT

Hi,

I see. This app should fit based on what you write. Can you share your bootloader project so that I can double check the configuration? If there is a problem with the NRF_DFU_APP_DATA_AREA_SIZE for instance, so that this is larger than you intend, then that could explain this. If not, this should be OK (this is handled by the nrf_dfu_cache_prepare() function in the bootloader).

RE: Cannot update zip file after enabling dfu

Vimalnath — Wed, 28 Oct 2020 06:07:58 GMT

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.(devzone.nordicsemi.com/.../5417.ble_5F00_app_5F00_buttonless_5F00_dfu_5F00_pca10040e_5F00_s112.hex this is not the exact example code of buttonless dfu application. I have added an ADC feature along with it.)

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Tue, 27 Oct 2020 14:01:23 GMT

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?

RE: Cannot update zip file after enabling dfu

Vimalnath — Tue, 27 Oct 2020 08:08:32 GMT

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.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_buttonless_5F00_dfu_5F00_pca10040e_5F00_s112.hex devzone.nordicsemi.com/.../secure_5F00_bootloader_5F00_ble_5F00_s112_5F00_pca10040e.hex

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Fri, 23 Oct 2020 12:28:02 GMT

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?

RE: Cannot update zip file after enabling dfu

Vimalnath — Fri, 23 Oct 2020 08:24:36 GMT

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.

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Thu, 22 Oct 2020 15:51:55 GMT

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.

RE: Cannot update zip file after enabling dfu

Vimalnath — Thu, 22 Oct 2020 09:47:02 GMT

devzone.nordicsemi.com/.../s112_5F00_nrf52_5F00_7.2.0_5F00_softdevice.hex This is the SD version I am using.

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Thu, 22 Oct 2020 08:15:27 GMT

Hi,

0x103 is not a valid ID (too large). Which exact SoftDevice version are you using?

RE: Cannot update zip file after enabling dfu

Vimalnath — Wed, 21 Oct 2020 13:34:22 GMT

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.

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Wed, 21 Oct 2020 12:50:51 GMT

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

RE: Cannot update zip file after enabling dfu

Vimalnath — Wed, 21 Oct 2020 12:37:21 GMT

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.

RE: Cannot update zip file after enabling dfu

Einar Thorsrud — Wed, 21 Oct 2020 12:11:32 GMT

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