Hi Kai, bt_mesh_model_publish() is (like the name suggests) for model publication. bt_mesh_model_send() is for everything else that falls outside of that use case. This could be e.g. a server model's

Hello, I'm trying to know the difference between two APIs, they are: * int bt_mesh_model_publish(struct bt_mesh_model *model) * int bt_mesh_model_send(struct bt_mesh_model *model, struct

Thanks Marc. It took a fairly painful process to produce a list because of how it is spread among several include files. But I was finally able to produce a list using: $ cpp -E -traditional-cpp \

Hi Warren, I'm no expert, but I for the latest master branch at least I think the device names come from the device tree files. Look for the .DTS file in your board folder, then follow the .dtsi

For the call: struct device *device_get_binding(const char *name) How do I determine the name to provide for SPIx for example, for a stm32f407 board? Is there a file constructed in the zephyr

Hello and happy Friday, This is the 4 May 2018 newsletter tracking the latest Zephyr development merged into the mainline tree on GitHub. An HTML version is available

I was informed that the major step towards ARM DS-5 support, full support of LLVM, is on the schedule for Zephyr rev 1.12. It seems that we can expect that around June.

It has not been rebased against latest SPI API changes, thus why it can't be merged. But it's a fine PR besides that. Tomasz

Thx Tomasz, It seems quite old. Why hasn't it been merged yet? Is there something wrong that prevent it?

Hi, Check this PR: https://github.com/zephyrproject-rtos/zephyr/pull/5200 You probably need the first patch, and the second is an example how to do it. Note however the API has changed a bit, you'll

Ciao guys, I'm currently working on ArgonKey, which is a 96 board with a STM32F412 plus a bunch of motion and environmental sensors. I'm exploring the possibility to put in place the communication

Hi, building Zephyr with an LLVM-based compiler (like DS-5) was prototyped but not finished in https://github.com/zephyrproject-rtos/zephyr/pull/5901. Since then there has not been any activity. I'm

Are there any plans for including support in Zephyr for the ARM DS-5 compiler? The getting started guide has some information about how to set up a 3rd party

Hi Diego, Having direct match between generated FLAGS/INT_CONF aliases and application symbols would be a good idea. Though not sure which should converge to the other. INT_CONF (Interrupt

Hi Waren, CONFIG_GPIO_STM32=n in your core407v_stm32f407_defconfig disables the STM32 gpio driver. Yannis https://www.waveshare.com/wiki/Core407V using

Hello, I'd like to know what is the usage of the *_GPIO_FLAGS macro. For example in "dts/bindings/gpio/nxp,kinetis-gpio.yaml" file: And "boards/arm/frdm_k64f/frdm_k64f.dts" file we have This will

HI Aaron, This PDF may help developers who want to go with Zephyr #BluetoothMesh. https://www.zephyrproject.org/wp-content/uploads/sites/38/2018/03/openiot_zephyr_lts_what_and_why.pdf But following

Hi, We all look forward that the zephyr project bluetooth mesh can be used on a real project. Before that, we want to know those question's answer. Thanks. vikrant8051 <vikrant8051@...>

This is in reference to the MCU board https://www.waveshare.com/wiki/Core407V I have been able to build & flash the project in zsrc.tar.gz (below) using the board BOARD olimex_stm32_e407. The LEDs

Hi, What will be status of #BluetoothMesh in #LTS v.1.12.0 release ? Will it be released as #Qualified stack ? As of now, we can't save Provisioning, Configuration & other real time data (eg. message