As the title suggests, is this a specification? or bug? otherwise something missing in the settings?
NVS values did not vanished while nRF5 SDK used.
before DFU
after DFU
As the title suggests, is this a specification? or bug? otherwise something missing in the settings?
NVS values did not vanished while nRF5 SDK used.
before DFU
after DFU
Hi,
Please use the same pm_static.yml for FOTA. See Static partition requirement for DFU.
Regards,
Amanda H.
Hi,
Thanks for the answer. I understand that I am missing a setting. I also read the link.
But...what exactly do I should to do?
I turned on CONFIG_PARTITION_MANAGER, but that causes a build error. (What does read-only mean?)
C:/ncs/v2.4.2/nrf/subsys/partition_manager/flash_map_partition_manager.c:12:10: fatal error: pm_config.h: No such file or directory 12 | #include <pm_config.h>
I can see that there is a partition.yml file in the existing build folder, does that mean I should move it to the root folder of the project?
Hi,
-Amanda H.
Hi,
Thank you for your advice.
Best Regards,
Yoshihiro Goto
Hi,
I actually verified this. And I also confirmed that the following message appears during the build.
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined. Partition 'mcuboot_pad' is not included in the dynamic resolving since it is statically defined. Partition 'mcuboot_primary' is not included in the dynamic resolving since it is statically defined. Partition 'mcuboot_primary_app' is not included in the dynamic resolving since it is statically defined. Partition 'mcuboot_secondary' is not included in the dynamic resolving since it is statically defined. Partition 'settings_storage' is not included in the dynamic resolving since it is statically defined. -- Configuring done
But...
Stored values in flash memory are still lost by DFU. Am I missing some setting?