using persistent data storage, NRF Connect.

[Johan.h]

I am trying to save some data in flash.

it works, but it corrupts the Bluetooth thread .

If  I call my_settings_init(), then bt_enable(NULL) never returns.

in prj.conf I added:

--------------------------------------------------------

# config using settings store and load:
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y
# in file my.overlay the storage allocated is 8 pages = 32K (8 x 0x1000)
CONFIG_SETTINGS_NVS_SECTOR_COUNT=8

------------------------------------------------------------------------

the my.overlay is as so:

&flash0 {
   partitions {
       compatible = "fixed-partitions";
       #address-cells = <1>;
       #size-cells = <1>;

       storage_partition: partition@78000 {
           label = "storage";
           reg = <0x00078000 0x00008000>;  // Allocate 32K for settings storage
       };
   };
};

added in Cmakelist.txt:

set(DTC_OVERLAY_FILE "my.overlay")

 BT working is no setting system is used, setting working but currups BT.

What is wrong?

Thanks

void read_settings(void)
{
	settings_load();
}

int my_settings_init(void)
{
	int err = settings_subsys_init();
	if (err) {
		LOG_INF("Can't init settings subsys (%d)\n", err);
		return err;
	}
	
	err = settings_register(&my_conf);
	if (err) {
		LOG_INF("Can't register my settings handler (%d)\n", err);
		return err;
		
	}
	/* Load settings from persistent storage */
	read_settings();
	return 0;
}

[Håkon Alseth]

Hi,

 

If a single-image build is being performed, zephyr's DT defined partition layout is used.

If a multi-image (for instance with MCUBoot) is performed, then the Partition Manager is used for defining the partition layout.

 

The latter uses a yml-based layout (check if build-folder/partitions.yml is present), and requires a different syntax.

One can create a my_application/pm_static.yml file containing:

storage:
    address: 0x78000
    size: 0x8000
    region: flash_primary

 

For the same functionality as you have set in the overlay.

 

If you're not using partition manager, can you please share the build-folder/zephyr/zephyr.dts file?

 

Kind regards,

Håkon

[Johan.h]

Hi Håkon,

Obviously, my knowledge map of Zephyr and NRF Connect has many white spots. Current project will need a bootloader for firmware update via mobile DFU. So should I develop the project for multi image from start, or should I develop as singly image, and later do the partition for application and bootloader?

If the correct approach is to go for multi-image at the development stage, how do I test the application without a debugger connected ?(I do it every step I take, removing the debugger and restarting, in order to check that power consumption has not jumped due to some added new code)

I tried to set that pm_static.yml, but then setting_init() failed and the bl_enable() also never returned.. I need to get better understanding of the whole  system configurations.

Thanks for your help.

Johanan

[Johan.h]

Hi,

To recap: (note: I reduced size to 1 page eeprom simulation =0x1000, as I need only 3 numbers to store)

Now, I get a Cmake error when I add pm_static.yml to the project directory:

CMake Error at E:/ncs/v2.3.0/nrf/cmake/partition_manager.cmake:304 (message):
  Partition Manager failed, aborting.  Command:
  C:/ncs/toolchains/v2.3.0/opt/bin/python.exe;E:/ncs/v2.3.0/nrf/scripts/partition_manager.py;--input-files;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/zephyr/include/generated/pm.yml;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/modules/nrf/subsys/partition_manager/pm.yml.settings;--regions;sram_primary;flash_primary;--output-partitions;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/partitions.yml;--output-regions;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/regions.yml;--static-config;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/pm_static.yml;--sram_primary-size;0x10000;--sram_primary-base-address;0x20000000;--sram_primary-placement-strategy;complex;--sram_primary-dynamic-partition;sram_primary;--flash_primary-size;0x80000;--flash_primary-base-address;0x0;--flash_primary-placement-strategy;complex;--flash_primary-device;flash_controller;--flash_primary-default-driver-kconfig;CONFIG_SOC_FLASH_NRF
Call Stack (most recent call first):

in prj.conf:

# config using settings store and load:
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_NVS_SECTOR_COUNT=1

The pm_static.yml:

settings_storage:
    address: 0x7E000
    size: 0x1000
    region: flash_primary

The build/zephyr.dts is here.

If I remove pm_static.yml from the directory, I can build the project with no errors.

BR

Johanan

[Håkon Alseth]

Hi,

 

Could you share the full error log?

 

Kind regards,

Håkon

[Johan.h]

I sent link to project in private msg. Thanks.

[Håkon Alseth]

Hi,

 

Thanks for the project.

 

I am sorry, but I have misinformed you earlier. When a pm_static.yml file is present, the build-system assumes to use PartitionManager, even for single-image builds. The problem is that the firmware requires an added kconfig.

In your prj.conf, try to add:

CONFIG_PM_SINGLE_IMAGE=y

 

 

PS: You need to set aside a minimum of two flash pages for the settings subsys:

settings_storage:
    address: 0x7E000
    size: 0x2000 # changed this
    region: flash_primary

 

Kind regards,

Håkon

[Johan.h]

I tried, but no joy yet.

I added in prj.conf:

CONFIG_PM_SINGLE_IMAGE=y

and fixed:

CONFIG_SETTINGS_NVS_SECTOR_COUNT=2

in pm_static.yml:

settings_storage:
    address: 0x7D000  # fixed to 7D000
    size: 0x2000
    region: flash_primary

Configuration build is OK but still have that build error:

Severity Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        Project  File                                            Line
Error    Partition Manager failed, aborting.  Command: C:/ncs/toolchains/v2.3.0/opt/bin/python.exe;E:/ncs/v2.3.0/nrf/scripts/partition_manager.py;--input-files;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/zephyr/include/generated/pm.yml;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/modules/nrf/subsys/partition_manager/pm.yml.settings;--regions;sram_primary;flash_primary;--output-partitions;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/partitions.yml;--output-regions;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/build/nrf52dk_nrf52832/Debug/regions.yml;--static-config;E:/MyWork/FeedSens_NRF_Connect/fdSensV2/pm_static.yml;--sram_primary-size;0x10000;--sram_primary-base-address;0x20000000;--sram_primary-placement-strategy;complex;--sram_primary-dynamic-partition;sram_primary;--flash_primary-size;0x80000;--flash_primary-base-address;0x0;--flash_primary-placement-strategy;complex;--flash_primary-device;flash_controller;--flash_primary-default-driver-kconfig;CONFIG_SOC_FLASH_NRF fdSensV2 E:\ncs\v2.3.0\nrf\cmake\partition_manager.cmake 304 
https://devzone.nordicsemi.com/f/nordic-q-a/99956/using-persistent-data-storage-nrf-connect/427116#

BTW did you try to build the project?

Thanks

Johanan

[Håkon Alseth]

Your offset address is incorrect in the pm_static.yml, shall be:

address: 0x7e000

for a size of 0x2000.

 

Kind regards,

Håkon

[Johan.h]

Well, that was rather silly of me :-), I should know HEX numbers already.

Now it builds OK, I will test the setting save/load later today.

Thanks very much.

Johanan

[Johan.h]

The following creates a hard error:

static ssize_t write_char_fun(struct bt_conn *conn,
	const struct bt_gatt_attr *attr,
	const void *buf,
	uint16_t len,
	uint16_t offset,
	uint8_t flags)
{
	LOG_INF("Attribute write, handle: %u, conn: %p",
		attr->handle,
		(void *)conn);
	
	// store in eeprom: 
	if (len == 1)
	{
		house_id = ((int8_t *)buf)[0];  
		save_settings(); // ,<<<--- This creates MPU FAULT, Data Access violation
		LOG_INF("Write House: %d ",house_id);
		return len;
	}
	LOG_INF("Write House fail len=: %d ", len);
	return BT_GATT_ERR(BT_ATT_ERR_INVALID_ATTRIBUTE_LEN);
}

However, if I call save_settings()  just at main() , before anything else, like bt_enable() , it works OK, and writes the setting in memory.

What can be the reason?

Thanks.

Johanan

[Johan.h]

I resolved the save_settings issue by taking it to the main loop from the write cb function, using a queue.

So now it works, but I would like to know why it does not work from inside the char write cb function.

BR

Johanan

//------  in the char write cb: 
	
	// store in eeprom: 
	if (len == 1)
	{
		
		house_id = ((int8_t *)buf)[0]; 
		
		// save_settings();// ,<<<--- This creates MPU FAULT, Data Access violation
		k_msgq_put(&setting_q, NULL, K_FOREVER); // just signal to save settings in main
		LOG_INF("Write House: %d ",house_id);
		return len;
	}
	
	// --- and in the main loop:
	 	
		k_sleep(K_MSEC(RUN_LED_BLINK_INTERVAL));
		
		if (k_msgq_get(&setting_q, NULL, K_NO_WAIT)== 0)
		{
			save_settings(); 
			LOG_INF("Settings successfully saved");
		}

[Håkon Alseth]

Hi,

 

BT callbacks are running in interrupt context, and you should not call such functions directly from interrupts.

 

Kind regards,

Håkon