Default storage of persistent info for OpenThread

[tush3094]

Hello,

I wanted to understand what is the default storage place in the internal flash memory region of persistent info for OpenThread. In the previous SDK (Thread and Zigbee) it was clearly mentioned the default memory region as shown below, (reference: Persistent storage of the thread instance)

But with the nrf connect SDK I did not find any such document stating a clarity at this. Currently, I build openthread in my project with the configs shown below,

# Generic networking options

CONFIG_NETWORKING=y

# OpenThread enabling

CONFIG_NET_L2_OPENTHREAD=y

# Openthread build from source

CONFIG_OPENTHREAD_SOURCES=y

CONFIG_OPENTHREAD_NORDIC_LIBRARY_FTD=n

CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y

CONFIG_OPENTHREAD_MTD=y

CONFIG_OPENTHREAD_MTD_SED=y

CONFIG_OPENTHREAD_THREAD_VERSION_1_3=y

# OpenThread config

CONFIG_OPENTHREAD_MANUAL_START=y

CONFIG_OPENTHREAD_JOINER=y

CONFIG_OPENTHREAD_JOINER_AUTOSTART=n

 Partition manager static yml file the nvs storage location is provided as,

nvs_storage:

  address: 0xFA000

  end_address: 0x100000

  placement:

    before:

    - end

  region: flash_primary

  size: 0x6000

As per the NVS documentation OpenThread data should be stored in NVS data partition.The place at which the dataset is stored currently is in internal flash at address: 0xF3000. How is this address selected?

Kind regards,
Tushar D

[Maria Gilje]

Hello,

The defaultt storage location for the OpenThread network data in NCS is in settings storage which again is in NVS. It is the settings subsystem which handles storing in NVS when using Thread in NCS. See the documentation for Configuring Thread in NCS for general information on Thread in NCS, the Settings service documentation, and NVS.

Best regards,

Maria

[tush3094]

Hello Maria,

Thank you for your quick reply. I have add these extra configs in my proj.conf

CONFIG_NVS=y

CONFIG_SETTINGS=y

CONFIG_SETTINGS_NVS=y

Also I have edited my .dts file to have the label "storage" for the storage partition with start address @FA000.

Even though this is set the openthread data is still stored at 0xF3000.

Is the openthread handling the storage by itself or we need to over ride some functions of openthread? 
Currently, I am just not able to store the openthread data at this address.

[Maria Gilje]

How and where do you read out the 0xF3000 address for the OpenThread data?

Are you using an NCS sample or your own code? For the Thread samples in NCS, the settings service is included by default. Do you see the same when reading out the address for the OpenThread data for an NCS sample?

[tush3094]

I read it out via the debugger (entire flash)

I consider this as the openthread data as I can see the panid (Openthread-e193) which is same as my dataset of the mesh.

I am using my own code. How can I include this settings service in my application? 

I have not tried to read out the OpenThread data from NCS sample. I can try it and get back to you.

[tush3094]

So I tested with the thread CLI example for nrf52840,

Here the openthread data is stored correctly

I am not sure what I am doing wrong in my build

[tush3094]

Some more information regarding the above issue. OpenThread data is stored correctly on our firmware when partition manager and bootloader are not used. Just the firmware is built and flashed. 

So basically this issue comes up when we built the firmware as a whole with application and MCU boot. 

Is there any specific change required here that needs to be done with partition manager enabled?

[AHaug]

Hi,

Maria is currently on vacation so I will be monitoring this case meanwhile. I will need some time to sync up with the information in this case, but I will get back to you later this week.

Kind regards,
Andreas

[AHaug]

Hi,

From what we can see it looks like you're the Partition Manager, and when you are using this the DTS partitioning is no longer used.

Instead you should use "west build -t partition_manager_report" to see your new partitioning, and try to read from that area instead.

See https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/ for some background on this

Kind regards,
Andreas

 

[tush3094]

Hello Andreas,

Thank you for looking into it. In the last 2 days I tried some more stuff and made some changes into the partition manager .yml file and already reached this point.

As per the info OpenThread data is stored in settings_storage partition which is at 0xF7000 after my changes. This is all good. 

My only concern is if in future the firmware size increases and reaches this point will these stored settings be deleted or automatically handled by the partition manager?

Kind regards,

Tushar 

[AHaug]

tush3094 said:

My only concern is if in future the firmware size increases and reaches this point will these stored settings be deleted or automatically handled by the partition manager?

I assume by this that you mean in case you have to store more data in your settings_storage partition than the declared size, and not if the application firmware size itself increases in the future (correct me if I'm wrong):

If this is the case then he partition manager uses the settings_storage subsystem which in turn should have its own garbage-collection procedure, mentioned https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/settings/index.html, as described here: "When storage becomes full (FCB) or consumes too much space (file), the backend removes non-recent key-value pairs records and unnecessary key-delete records."

Let me know if this answers your question

Kind regards,
Andreas

[tush3094]

Sorry, I was not clear. I meant if the firmware application size increases and reaches this point. After a firmware update would it be restored again? Because settings_storage address is not something which I declare in the partition manager .yml file. This address 0XF7000 is randomly chosen.