nRF5340 - Setting Feature with Custom Partition

RE: nRF5340 - Setting Feature with Custom Partition

AHaug — Tue, 24 Oct 2023 13:31:39 GMT

Hi,

Apologies for the delayed response, I had to check up on some things

In general we don't recommend you to remove the settings_partition that Bluetooth and/or Matter uses as this is a persistent part of the memory
After some input from the creator of the sample you refer to from Setting and using NVS and BT Settings with Static Partition Manager :
Adding another settings partition should be relatively straight forward, and can be done by
1. Adding a new partition in pm_static.yml
2. Change this line: https://github.com/nrfconnect/sdk-zephyr/blob/32a51d982e0b7eba7e458678a8246440b25c3916/samples/subsys/settings/src/main.c#L20

[quote user="skim"]If I disable it, will the BT_SETTINGS feature be entirely deactivated? Would I then be responsible for handing the storage and restoration of BT state (including pairing keys)? If so, how should I proceed?[/quote]

As the other case you refer to states, this is possible and the sample that Sigurd has provided showcases how to do this. Item number 1 in my previous list explains why you should not disable bt_settings and thus remove the persistant storage for the wireless protocols that use it.

[quote user="skim"]a) Define a partition in the 'external_flash' area using pm_static.yml (Currently, it is defined in the 'primary_flash' area as a name of custom_nvs_storage)[/quote]

developer.nordicsemi.com/.../partition_manager.html https://github.com/nrfconnect/sdk-zephyr/blob/32a51d982e0b7eba7e458678a8246440b25c3916/samples/subsys/settings/src/main.c#L20 and the Note in that section should explain how to do this

Regarding b) and c) I also believe that this should be handled by the sample Sigurd created. I will look closer into the sample at the end of this week, but in the meanwhile I hope this is enough to keep you going

Kind regards,
Andreas

RE: nRF5340 - Setting Feature with Custom Partition

skim — Fri, 20 Oct 2023 21:48:15 GMT

Hello, I apologize for the truncated image. Here is the textual representation of the kernel error:

ASSERTION FAIL [handler != ((void *)0)] @ WEST_TOPDIR/zephyr/kernel/work.c:667
[00:00:00.807,373] <err> os: esf_dump: r0/a1:  0x00000004  r1/a2:  0x0000029b  r2/a3:  0x00000024
[00:00:00.807,403] <err> os: esf_dump: r3/a4:  0x0000029b r12/ip:  0xb6a93df4 r14/lr:  0x000351a7
[00:00:00.807,434] <err> os: esf_dump:  xpsr:  0x61100000
[00:00:00.807,495] <err> os: esf_dump: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000
[00:00:00.807,525] <err> os: esf_dump: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000
[00:00:00.807,556] <err> os: esf_dump: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000
[00:00:00.252,716] <dbg> nrf5340dk_nrf5340_cpuapp: remoteproc_mgr_boot: Network MCU released.
[00:00:00.807,617] <err> os: esf_dump: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000
[00:00:00.807,647] <err> os: esf_dump: fpscr:  0x00000000
[00:00:00.807,678] <err> os: esf_dump: Faulting instruction address (r15/pc): 0x0003cce8
[00:00os: z_fatal_error: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:00.807,769] <err> os: z_fatal_error: Current thread: 0x20001ed8 (unknown)
[00:00:00.975,769] <err> os: k_sys_fatal_error_handler: Halting system

During my investigation into the issue, I managed to find a way to run the project without encountering the kernel error. This involved disabling the CONFIG_BT_SETTINGS. The documentation regarding this config value states,

"When selected, the Bluetooth stack will take care of storing (and restoring) the Bluetooth state (e.g. pairing keys) and configuration persistently in flash"

Here is my question:

If I disable it, will the BT_SETTINGS feature be entirely deactivated? Would I then be responsible for handing the storage and restoration of BT state (including pairing keys)? If so, how should I proceed?

Another unresolved issue is that I want to

a) Define a partition in the 'external_flash' area using pm_static.yml (Currently, it is defined in the 'primary_flash' area as a name of custom_nvs_storage)

b) Utilize it as the backend for Settings in the overlay using 'zephyr, settings-partition'.

c) Ensure that the memory area used by BT_SETTING is separated from the memory area used by regular Settings.

Here I am attaching the project that I combines a project from the devzone and Settings sample. This project shouldn't build because I added a line in the overlay file to link settings' NVS and a custom_nvs_storage, and the system cannot find the custom partition.

devzone.nordicsemi.com/.../bt_5F00_setting_5F00_sample_5F00_from_5F00_devzone.zip

Feel free to let me know if you'd like further clarification or edits.

Thank you,

Sincerely,

Skim.

RE: nRF5340 - Setting Feature with Custom Partition

AHaug — Thu, 19 Oct 2023 12:11:33 GMT

[quote user="skim"]1. Here is a screenshot of a kernel fatal error. [/quote]

What is posted beneath here? What is posted above the line? I need the entire log to be able to cipher anything from it. Please upload it as a text or insert code

[quote user="skim"]2. Here is a screenshot of a memory map[/quote]

This image is also cut off, can you reupload a full picture including all numbers

Kind regards,
Andreas

RE: nRF5340 - Setting Feature with Custom Partition

skim — Wed, 18 Oct 2023 23:18:39 GMT

1. Here is a screenshot of a kernel fatal error.

2. Here is a screenshot of a memory map

3. Here is a pm_static.yml file for each casedevzone.nordicsemi.com/.../pm_5F00_static_5F00_ext_5F00_flash.txt devzone.nordicsemi.com/.../pm_5F00_static_5F00_flash_5F00_prim.txt

Hope this helps.

Sincerely,

Sungji Kim.

RE: nRF5340 - Setting Feature with Custom Partition

AHaug — Wed, 18 Oct 2023 12:35:00 GMT

Hi,

For all three cases, can you also provide the following:

Can you provide the full build errors and/or device logs?
Can you provide the memory map, i.e use VS Code extensions tool or navigate to the build folder and report back what "ninja partition_manager_report' generates?
If you have a static_pm.yml for each of the cases, can you provide that as well?

Kind regards,
Andreas