Utilizing Bank 1 between Dual-bank DFUs?

[ykChang]

I am using nRF5_SDK_15.2.0_9412b96. I have application data that accumulate in flash but can be thrown away before re-flashing new app image. I am thinking about instead of using the app_data space, storing them in the free space reserved for caching app image in dual-bank update (Bank 1). Then, before the next DFU, the data would be uploaded and Bank 1 space erased, ready for caching DFU image for dual-bank. Any possible side effects?

[bjorn-spockeli]

Hi Chang,

if the DFU_APP_DATA_RESERVED definition in the bootloader is set to 0, then the application data stored in the app_data section will be erased during DFU. So I do not really see the point of storing application data outside the app_data space. 

Best regards

Bjørn

[ykChang]

Hi Bjorn

Thanks for the response. Sorry you did not see the point of my question because perhaps I didn't make my intention more clear. I do store data in the APP data area that we need to preserve forever across DFUs. However we also have data that can be uploaded and thrown away before each DFU (user's intention to OTA DFU presumably provides the network engagement opportunity). We need as much "upload and throw away" space as possible, preferably outside of the persistent app data budget.

[bjorn-spockeli]

Thanks for the clarification, now I understand. 

In that case, placing the persistent data in the app_data area and the non-persistent data below the app_data region in Bank 1 is the way to go. 

[ykChang]

Thanks Bjorn!