Changing the k_timer API to work in some other unit than milliseconds is doable, though a little messy from a compatibility standpoint. The underlying unit of ticks is

Hi there, This has been requested several times, but as far as I know has not been completely solved yet. There is an issue here:https://github.com/zephyrproject-rtos/zephyr/issues/6498, please

Hello, My team and I are developing an application that will need the use of timers using the FRDM-K64F board. The application requires a timer to be set using microseconds as the unit. Looking

I’ve created the ‘dev-review’ label for us to mark PRs for review in the meeting. - k

All, If you have a PR or Issue that needs discussion we will use this call to talk about it. The meeting will use the time slot that we had for the bug triage meeting (10a Central US Standard

Hi Tommy, I don’t remember if DTM mode has any RSSI command in the Specification. Could you please elaborate on your requirements? Regards, Vinayak

Hi , We have a product using nRF51824 with zephyr. We use hci_uart sample code and follow below link , and we can get other BT device’s

Hej ho Thanks Erwan for the reply. I checked the "dts/bindings/sensor/" dir to get an idea. If I get it right I need to create the files "xxx,codec1.yaml" and "xxx,codec2.yaml"?

Hi Stefan, To generate #define's from dt, you need to provide the matching yaml binding to indicate how fields should be decided, this should be done under dts/bindings/... Generated #define's will be

Hej, I like to create an user app that uses 2 IC connected via I2C with my MCU.  Doing this is a bit tricky because I am missing some documentation, that is describing how the whole process

Hi, in case anyone else is interested: lemrey has reworked the patch at https://github.com/zephyrproject-rtos/zephyr/pull/11210 today to address some comments. With the update, non-volatile storage

Yeah, forgot that the docs get updated only once a dayL Documentation is now being updated and will be available in the new version shortly. Anas

Uh... those instructions still tell you to get cmake 3.8.2 :) The latest is currently at https://cmake.org/files/LatestRelease/cmake-3.13.2-Linux-x86_64.sh it seems. Andy

s/not/now/ in the title J

Hi, We have changed the minimal requirement version of cmake to 3.13.1 meaning that you are required to update cmake on your system to build Zephyr. Please follow the documentation below to

Thanks Carles. This is what I had in my mind too. This is already done for the generic spi flash driver (drivers/flash/spi_nor.c). I’ll hope that’s all that’s required. Thanks again.

Hi Carles, Manually adding your new code lines to my jlink.py works. Regards, Bo

Thanks. I’ve sent a PR to the west repo to fix this. If you could test it (simply get the file and overwrite your local jlink.py) and approve it it would be most

Hi Carles, Number 2 works fine. Thanks a lot. Regards, Bo

Right, I think I know what is going on, the default value in the constructor is not being used. I believe there are 2 ways to try and fix the issue until we submit a patch: Add a line