Why doesn't Device State Manager allow to increase the number of entries?

RE: Why doesn't Device State Manager allow to increase the number of entries?

Joakim Jakobsen — Thu, 13 Feb 2020 09:38:44 GMT

Hi again.

The problem with allowing this use case is that; if a number of DMS pages get changed as a result of increasing values of DSM_*MAX defines, it will trigger either an assertion in subsequent modules when they see that the flash page metadata is different than expected. Or it may lead to corrupted data loading other modules.
It is better to plan in advance and allocate more space for a sufficient number of DSM entries.

Regards,
Joakim

RE: Why doesn't Device State Manager allow to increase the number of entries?

Joakim Jakobsen — Mon, 20 Jan 2020 13:10:13 GMT

Hi.

Sorry about the delay.

I have an open internal request to our developers to comment on this. I'll update you as soon as I get any feedback.

Br,
Joakim

RE: Why doesn't Device State Manager allow to increase the number of entries?

JonasJ — Mon, 13 Jan 2020 10:41:57 GMT

Hi,

Any comment from the developers?

The same "problem" remains with Mesh SDK 4.0.0.

The new metadata should also be written to the flash when they mismatch. Otherwise there could be more entries in the flash than the metadata indicate causing issues later on.

Thanks.

RE: Why doesn't Device State Manager allow to increase the number of entries?

Joakim Jakobsen — Tue, 19 Nov 2019 13:36:45 GMT

Hi.

What you describe above seems to be the correct behavior.

[quote user=""]Thus, is there an issue of changing dsm_flash_config_load() according to the following patch.[/quote]

I'll ask for a comment from our developers about this.

Cheers,
Joakim