Hi Johan, Which app you used for testing ? Is it samples/boards/nrf52/mesh/onoff-app by adding persistent storage support ? Could you please test it for PR:8296 by removing NVS from it ? Thanks!!

That is true, this way doesn't support adding a driver module into the application since the app doesn't directly call anything from the driver. I'm wondering why driver modules in zephyr directory

"Li, Jun R" <jun.r.li@...> wrote: Well, this way of doing bears a whole of problems in some conditions. While it works in probably most cases, including drivers in such a library won't work.

Hi Patrick, If you still want to keep your library (module), another way you can do is to add your library as the link dependency for the application library (app) by the

Hi Vikrant, I understood what you meant. And those are the steps I followed. I used Nordic's new iOS mesh app and used its "node reset" feature. Then I reprovisioned and after that did a power-cycle.

Hi Johan, I've completely removed NVS from my local project. Even after that facing same issue. If you provision & configure -> reset the board -> then it work as expected. But I'm not talking

Hi Jehudi, The linker section is defined in include/linker/common-rom.ld, and variables are placed there using the __in_section() specifier

Hi, In the settings part of bt there seems to be a cool way to generate a list of settings with their set, commit and export handlers. Items are added to this list by a macro BT_SETTINGS_DEFINE() and

Hi Patrick, König Patrick <Patrick.Koenig@...> wrote: The most convenient way of adding additional sources to your application outside zephyr is using target_sources(app PRIVATE src1.c

Hi Vikrant, I just tried your exact steps with the mesh_shell app, and it works correctly (i.e. after the power cycle the board comes back as provisioned). I used the nRF51 USB dongle, fwiw. Is it

Hello, My name is Patrick König. I am new to zephyr. I just wrote a couple of functions as additions to the zephyr/samples/subsys/usb/cdc_acm Sample Project for the Nordic nRf52840. These are

Hi Johan, It is with default #FCB.

Hi Vikrant, Is this with NFFS or FCB? I remember testing this with FCB and it worked correctly. Johan

Hi, Yes, I confirmed my observation. And happening this every time. I also tried it with #nRFMesh app. In that case too, if I do (provision + configuration) -> ( node-reset ) -> (provision +

Hi, If after complete or partial provisioning, execute node-reset command then in that case I have observe following things : 1) Node get reprovision 2) but after reboot, it boot as unprovisioned

Hi "Patrick Boettcher" <patrick.boettcher@...> wrote: A colleague (thanks Ismael) has bisected zephyr between 1.11 and 1.12 to find that dd5449a77b5c914 is the first commit without the

An GitHub issue was opened to address this requirement: https://github.com/zephyrproject-rtos/zephyr/issues/8350 Thank you! Jun From: <devel@...> on behalf of vikrant8051

Hi Johan, This is not new requirement. I had asked similar question on Jan 25, 2018 This is for your reference, https://lists.zephyrproject.org/g/devel/message/1644 Need was static passkey for

Hi Johan, My requirement is exactly like what you said: every device has a unique passkey stored and labeled on this case. The user needs to check the case to get the right passkey and enter it when

Hi Jun, We don't have such a feature currently (no one has asked for it until now). Do I understand right that you want to have a per-device static random passkey that's e.g. on a sticker on the