Unstable ZMS

RE: Unstable ZMS

Håkon Alseth — Thu, 30 Jan 2025 15:40:28 GMT

Hi,

Could you try to declare a zms_settings partition?

[quote user="Allan-led"]Here's the yml file from the project that does not work: [/quote]

This yaml file does not seem to have a zms_storage partition:

app:
  address: 0x0
  end_address: 0xf8000
  region: flash_primary
  size: 0xf8000
nvs_storage:
  address: 0xf8000
  end_address: 0xfe000
  placement:
    before:
    - end
  region: flash_primary
  size: 0x6000
settings_storage:
  address: 0xfe000
  end_address: 0x100000
  placement:
    align:
      start: 0x1000
    before:
    - end
  region: flash_primary
  size: 0x2000
sram_primary:
  address: 0x20000000
  end_address: 0x20040000
  region: sram_primary
  size: 0x40000

If you create a pm_static.yml file in your application/ folder containing this:

zms_storage:
  address: 0xfa000
  end_address: 0x100000
  placement:
    before:
    - end
  region: flash_primary
  size: 0x6000

And nothing else; it should adjust other partitions as needed in the new_build-folder/partitions.yml.

PS: You need to do a new build (not pristine) for such static partition layout to be included.

Kind regards,

Håkon

RE: Unstable ZMS

Allan-led — Wed, 29 Jan 2025 18:03:18 GMT

An update:

I copied the successful yml file to the unsuccessful project, and it still gave the same error of invalid address: 0x00100fe0:16 while trying to mount ZMS, even though I believe the address has made it clear that this is an invalid address.

RE: Unstable ZMS

Allan-led — Wed, 29 Jan 2025 17:22:59 GMT

Hi!

I have based my work off of the Thread CLI sample, and I have been building off of that for quite a while now. The ZMS project that works was built as a new project.

Here's the yml file from the project that does not work:

app:
  address: 0x0
  end_address: 0xf8000
  region: flash_primary
  size: 0xf8000
nvs_storage:
  address: 0xf8000
  end_address: 0xfe000
  placement:
    before:
    - end
  region: flash_primary
  size: 0x6000
settings_storage:
  address: 0xfe000
  end_address: 0x100000
  placement:
    align:
      start: 0x1000
    before:
    - end
  region: flash_primary
  size: 0x2000
sram_primary:
  address: 0x20000000
  end_address: 0x20040000
  region: sram_primary
  size: 0x40000

and the yml file from the project that does work:

app:
  address: 0x0
  end_address: 0xfa000
  region: flash_primary
  size: 0xfa000
sram_primary:
  address: 0x20000000
  end_address: 0x20040000
  region: sram_primary
  size: 0x40000
zms_storage:
  address: 0xfa000
  end_address: 0x100000
  placement:
    before:
    - end
  region: flash_primary
  size: 0x6000

Yes, I am indeed working on an nRF52840 board!

I would appreciate any further help! Thanks!

RE: Unstable ZMS

Håkon Alseth — Wed, 29 Jan 2025 14:52:44 GMT

Hi,

Q1: Which sample are you using to recreate this scenario? I would like to recreate this on my end as well.

Q2: are you performing a full erase of the device when moving from one project with zms to another?

The reason I ask is because they can overlap in address area between applications.

Check your build-folder/partitions.yml and see if the "zms_storage" is changed between the two samples.

Preferably share both .yml files.

Q3: I suspect these are logs from a nRF52840 device?

[quote user=""]

Below are the error messages:

- flash_nrf: invalid address: 0x00100fe0:16

- fs_zms: zms not initialized.

[/quote]

If yes, then the 0x100fe0 is out-of-bounds of the flash itself, indicating that there's something with the originating fs structure (addr + size variables).

Kind regards,

Håkon

RE: Unstable ZMS

Allan-led — Wed, 29 Jan 2025 00:52:39 GMT

Edit: Now restarting the PC entirely won't even fix the issue. I built another project that uses zms, and everything works out there. Thus, I replaced everything within my old directory with the content of the new project, and it still fails. How come the directory affects the success of zms initialization?