Protect NVM from being overwritten during reflash

[Brian]

I'm using the pstorage driver on the nRF51 to maintain several NVM variables. The NVM functions correctly and maintains state between power cycles. However, when I reflash the device using OTA reflash (application only, not SoftDevice), all of my NVM variables are reset to 0xFF. How do I prevent reflashing from modifying my NVM variables?

This is the command line I'm using to generate the zip file used for OTA reflash -

nrfutil dfu genpkg myProgram.zip --application myProgram.hex --application-version 0xffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0xfffe

Thanks

Brian

[FormerMember]

The "Preserving application data" section in the bootloader documentation explains what to do to avoid loosing data during the DFU operation.

[Brian]

I'm using the dual-bank bootloader - based off of the Makefile in .../examples/dfu/bootloader/pca10028/dual_bank_ble_s110/armgcc. Is it possible that trying to update both bootloader and application at the same time did not fit in the available free space? Does this mean I need to perform the updates as 2 separate steps - first the bootloader, then the application? I'm assuming the change I made to DFU_APP_DATA_RESERVED does not change the actual code size of the bootloader, correct? Thanks...