Hi all, Due to a conflict I have had to cancel the API meeting today. Next week we will have the meeting as usual. Regards, Carles

Hi all, Agenda for tomorrow. - API and component naming conventions - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/29569 - New cbprintf family of functions: - PR: https://github.com/zeph

Hi all, Agenda for tomorrow. Note: the API and component naming conventions (https://github.com/zephyrproject-rtos/zephyr/issues/29569) discussion has been postponed until next week since tomorrow the

Hi all, Agenda for today. - Kernel headers - PR: https://github.com/zephyrproject-rtos/zephyr/pull/29359#issuecomment-713598116 - API and component naming conventions - Issue: https://github.com/zephy

Hi all, Agenda for today. - workqueue: Introduce delayable work - PR: https://github.com/zephyrproject-rtos/zephyr/pull/28891 - Add regulator driver infrastructure - PR: https://github.com/zephyrproje

Hi all, Agenda for today. - Clock control API change - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/27423 - Pinmux and pinctrl path forward: - Issue: https://github.com/zephyrproject-rto

Hi all, An additional item for today: - Cleanup of work queue API doc - PR: https://github.com/zephyrproject-rtos/zephyr/pull/28824

Hi all, Agenda for today, sorry for the short notice. - Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it - Issue: https://github.com/zephyrproject-rtos/ze

Hi Nikos, The Cryptocell requires proprietary software that is not part of Zephyr. If you’d like to use the Cryptocell I recommend you take a look at Nordic’s Zephyr-based SDK, the nRF Connect SDK: ht

#nrf52840 #crypto

Hi all, In order to focus on the release itself I have cancelled the API meeting today. Next week it will take place as usual. Regards, Carles

The reason that Zephyr does not copy the items to the list is that it offers primitives that copy them (message queues) and primitives that do not (FIFOs). Then you can use FIFOs if you have your own

Hi all, Another special agenda for today: - Modbus: https://github.com/zephyrproject-rtos/zephyr/pull/26516 - In order to help with the 2.4 release we will go through bugs labeled API or drivers and t

Hi Harish, Best I can think of for that is to use a filter in GitHub to see all issues (open and closed) that target the next 1.14.3 release: https://github.com/zephyrproject-rtos/zephyr/issues?q=+is%

Hi Harish, You can browse the issues that were addressed in the 1.14.x releases here: https://docs.zephyrproject.org/1.14.1/releases/release-notes-1.14.html https://github.com/zephyrproject-rtos/zephy

Hi all, Special agenda for today: - In order to help with the 2.4 release we will go through bugs labeled API or drivers and try to clean up or assign as many as we can. Teams link: https://teams.micr

Hi Erik, FYI, pyocd is Zephyr-aware and Nordic’s J-Link OBs can be reflashed with pyocd-compatible firmware: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52-DK/Download#infotabs A

#debugging #gdb #nrf52480 #ztest #bluetoothmesh

Hi Deepa, From your question it seems you are using the nRF Connect SDK, and not vanilla Zephyr. You should therefore direct your question to the Nordic DevZone instead: https://devzone.nordicsemi.com

Hi Dominik, >. Is there a reason why Zephyr does not copy the items to the queue like FreeRTOS does it? The Zephyr documentation lacks this kind of information! FIFOs do not copy the contents of the m

Hi Nikos, Maybe you want to look at MCUboot, which supports this out of the box and is integrated with Zephyr? https://mcuboot.com/ https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_BOOTL

#flash #nrf52480

Hi all, Agenda for today, sorry for the short notice. - Stable API change: All hid_ops callbacks get device pointer - https://github.com/zephyrproject-rtos/zephyr/pull/27619 - Add Regulator driver inf