(Zephyr / NCS) NVS Error: flash_nrf: invalid address: with CONFIG_SETTINGS=y

RE: (Zephyr / NCS) NVS Error: flash_nrf: invalid address: with CONFIG_SETTINGS=y

Simonr — Fri, 11 Mar 2022 12:42:55 GMT

Hi Eric

It's correct that you should wait to set up a static configuration of the partition manager until you have a product out in the field where the partitions are supposed to be locked.

I discussed your issue with a couple of colleagues, and we think it would be best to split the partitions into two separate NVS partitions, so you don't have to synchronize between mulitple images like this. 1 for the settings NVS and one for the "user NVS".

Best regards,

Simon

RE: (Zephyr / NCS) NVS Error: flash_nrf: invalid address: with CONFIG_SETTINGS=y

zciwor — Thu, 10 Mar 2022 17:04:47 GMT

So it seems that my issue is due to using MCUBoot in combination with NVS. I understand that the device tree is ignored when using a multi-image build configuration.

This can be re-created by trying to compile the NVS sample with CONFIG_BOOTLOADER_MCUBOOT=y set. The problem line is below and is because the macro cannot find the storage label which was defined in the device tree (being ignored).

#define STORAGE_NODE DT_NODE_BY_FIXED_PARTITION_LABEL(storage)
#define FLASH_NODE DT_MTD_FROM_FIXED_PARTITION(STORAGE_NODE)
flash_dev = DEVICE_DT_GET(FLASH_NODE);

Here is the error:

error: '__device_dts_ord_DT_COMPAT_fixed_partitions_LABEL_nvs_storage_PARENT_PARENT_ORD' undeclared (first use in this function)
   80 | #define DEVICE_NAME_GET(name) _CONCAT(__device_, name)

I am able to fix the compilation error by adding a pm_static.yml file to the root directory of the NVS sample as described far down in this thread.

storage:
  address: 0x7a000
  size: 0x6000
  end_address: 0x80000
  placement:
    before: 
    - user_storage
  region: flash_primary
user_storage:
  address: 0x80000
  size: 0x2000
  end_address: 0x82000
  placement:
    before:
    - end
  region: flash_primary

However, in a different thread (that I cannot find right now), it is recommended to avoid static configuration. This seems to make sense.

So in order to prefer the partition manager's output, I have removed the two problems lines (above) and ran a `ninja report` in the build folder. The output is below:

  flash_primary (0x80000 - 512kB): 
+-------------------------------------------------+
| 0x0: mcuboot (0xc000 - 48kB)                    |
+---0xc000: mcuboot_primary (0x37000 - 220kB)-----+
| 0xc000: mcuboot_pad (0x200 - 512B)              |
+---0xc200: mcuboot_primary_app (0x36e00 - 219kB)-+
| 0xc200: app (0x36e00 - 219kB)                   |
+-------------------------------------------------+
| 0x43000: mcuboot_secondary (0x37000 - 220kB)    |
| 0x7a000: nvs_storage (0x6000 - 24kB)            |
+-------------------------------------------------+

  sram_primary (0x10000 - 64kB): 
+-------------------------------------------+
| 0x20000000: sram_primary (0x10000 - 64kB) |
+-------------------------------------------+

This seems to imply that there is a partition labeled `nvs_storage` that I can use as a FLASH_NODE.

However, when changing my problem lines to target the partition labeled nvs_storage (as described in the report output) I am still faced with the same compilation error.

I do not see any documentation on the partition manager page that describes how to actually use it in the multi-image builds. Am I missing something? What is the alternative to defining a static partition?

RE: (Zephyr / NCS) NVS Error: flash_nrf: invalid address: with CONFIG_SETTINGS=y

Simonr — Thu, 10 Mar 2022 13:13:20 GMT

The Partition Manager documentation is available here. I'm not sure what you're looking for in terms of "calculating partitions", but the size of Flash and RAM is stated in the nRF52 product specification, and the size of I.E. the Bluetooth LE controller you're using can be found here.

Best regards,

Simon

RE: (Zephyr / NCS) NVS Error: flash_nrf: invalid address: with CONFIG_SETTINGS=y

zciwor — Wed, 09 Mar 2022 15:20:15 GMT

Thanks Simonr, can you point me to documentation that describes how to calculate these partitions for a given chip? So far I have been using the default partitions for the nRF52 DK dts file.

RE: (Zephyr / NCS) NVS Error: flash_nrf: invalid address: with CONFIG_SETTINGS=y

Simonr — Wed, 09 Mar 2022 14:57:18 GMT

Hi Eric

It looks like something is trying to write data outside of the flash of the nRF52832, are you trying to write data outside of the partitions you have allocated somewhere? I guess you could try reducing some of your partitions so the entire flash isn't taken by these partitions.

Best regards,

Simon