I’m guessing this is because the reg should be set to 0 and not 1. So it should be: bmi160@0 { … reg = <0>; ... }; - k

Hi all, I’m trying to add a sensor board to a STM32F4 discovery board for a prototype, i.e., adding a BMI160 sensor to the SPI1 bus. To do that, I’ve modified the

I am responsible for this oversight in the documentation. If you wouldn't mind sending a fix I would be happy to review it. Thanks.

Hi Ryan, I will take a look at the PRs and add reviewers. Feel free to join the TSC call tomorrow to raise awareness and discuss. The release manager for this release is Kumar Gala from

Hello, I have 2 PRs open to add two new development boards to Zephyr. I would like to see if it is possible to get them added before v1.14 is

Some Bug details: 268:bug 124:priority: low 109:priority: medium 6:priority: high 42:Coverity 41:area: Networking 15:area: Bluetooth 14:area: Drivers 13:nRF 12:area: Kernel 11:area:

Thanks Anas! Correct no PR yet, sorry for the confusion. This is still at the early prototype stage however there's already a demo git commit - the one that produced the screenshot - linked from

I think this looks great. 9947 is not a PR, it is an enhancement issue, got me confused for a second. So it is an open enhancement issue with not PR associated with it, if you have something ,

I tried the “moderncmakedomain” sphinx extension to prototype extracting CMake comments into html and it seems to work, see screenshot and PR

All, Wanted to provide some bug stats so we can hopefully drive the total number of bugs down to single digits for the LTS release: Some Bug details: 265:bug 125:priority: low 112:priority:

… including no “toolchain" in some cases thanks to ZEPHYR_TOOLCHAIN_VARIANT=host I noticed ZEPHYR_TOOLCHAIN_VARIANT=host doesn’t seem mentioned in the documentation (I found it in the source).

Hi all, We have just tagged Zephyr 1.14.0-rc1. All required features that have not been pushed out to 1.14 are now merged, and so we begin the stabilization phase that should run for around 4

Hi guys, I'd like to encrypt the advertise packet since some secure fields in the payload. But I did not find any clue yet. So anybody knows how to implement this feature with zephyr? Thank a lot if

Hi Marti, I followed your steps & its works for me. Thank You !!

Hi Vikrant, Thanks for the report. The warnings are a known issue; please see: https://github.com/zephyrproject-rtos/zephyr/issues/13194. The reason mcuboot is not working with mainline zephyr is

Hello, I am getting following warning while building mcuboot : warning: ‘enum power_states’ declared inside parameter list will not be visible outside of this definition or declaration void

No, Zephyr release is not tied to a toolchain. The SDK was always a one stop for everything you need to build and use zephyr, but you should be able to use any toolchain. Anas

That's due to multilib arm and arc both 80% of the SDK if I remember correctly :) Anas

Hello, "Paul Sokolovsky" <paul.sokolovsky@...> wrote: Ping @nashif. Btw, nice upgrade in size comparing to "non-NG" SDK - from 300MB to 700MB. No chance that we just fix up the old SDK?

Hi All, I am looking at implementing a sensor network via BLE Mesh and am looking for any information on the implementation of the SENSOR MESH MODEL. Can anyone point me in the right direction? Many