Hi Akash, I think you better have a look at these links (as

Hi all, Vikrant, Thanks for your feedback. However the issue if you can call it an issue, is that the BL Mesh OnOff sample applic sets by default a minimum 1 second delay before publishing the state

Hi Thanks for answer, Andrzej. Find that I lock value after first key find in flash. I did not know that FBC scan all keys in flash. The problem is that some keys are writen more times and after long

So while loading settings subsystem loads all available in storage kay-value pairs. Guaranteed are that it will load the most recently values as the last and then h_commit handler will be

I'm using settings to save application data. But after one setting was writen more than once and application is restarted I get after call settings_load() first value and not last one. For writing I

Hi Jun, Based on bisecting it seems commit 4d94257162b22f37104e9f85238ed7c3486c5a1c is introducing the issue. Reverting it made the delay and log_strdup failure go away for me. It also fixed the

Thanks you for the reponse.I took the time to extract the modified opus library code from the Smart Ready project (from the .exe to linux) and compared it to the origin opus lib.Now i will try to use

Hi Johan, Thanks for the quick reply! Is there an issue addressing the 9 second delay problem during the booting process? It seems the issue #11780

Hi, This is normal when CONFIG_BT_SETTINGS=y is enabled. In such a case the identity address isn’t initialised until the app calls settings_load(), since the identity may be stored in flash. This

Hi there, I’m trying to rebase my project which is based on NRF51822 SoC from V1.13 to the latest version but found the application doesn’t work anymore. It seems the application suffers from

Hi All, Currently i am working on IPV6 over BLE mesh, For that i have chosen reference of RPL Border and RPL Node of zephyr RTOS.I have seen examples of rpl node and border router, but those were

Hi Johan, Thanks a lot for the useful reply. I noticed your reply in github as well. Thanks a lot! Thanks, Vincent From: Hedberg, Johan <johan.hedberg@...> Sent: Saturday, December 1, 2018 9:35 PM To:

Hi, I’ve tried to answer your questions in the GitHub issue (#11789) that you opened before sending this email. In the future, please use either to GitHub *or* the mailing list, but not both,

Hi, Recently I am investigating on adopting a possible BLE Mesh solution in my project. Just found there is BLE mesh support in zephyr now. I am wondering how many nodes can zephyr mesh support? And

Hi, It is because of new logging sub-system. And If you disable CONFIG_BT_DEBUG_LOG to avoid that then provisioned NODE takes 10+ seconds to initialized the Mesh. I've already raised issue for that

Hi Zephyr community, bluetooth Mesh fans, I played around with the Zephyr Mesh OnOff applic running on a Nordic nRF52 board.

Actually, I think I'm mistaken, the k_wakeup() calls will ensure that it doesn't sleep for the full amount each iteration. We're probably fine. It only wakes up on its own by default every 1000ms, not

Hi. Since Krzysztof already left the office, I will try to answer that. When logs are deffered, you need to call LOG_PROCESS() periodically to format log messages and push them to the backends. If

Hi Krzystof, For some reason I did not get your email, Carles had to forward to me. Krch:  Intention was to set it to the lowest possible value - K_LOWEST_APPLICATION_THREAD_PRIO. Now I've noticed

Re-sending since apparently this email never reached its destination. From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...> Sent: 29 November 2018 07:54 To: Cufi, Carles <Carles.Cufi@...>;