Hi Mohamed, i think #include <drivers/sensor.h> with standard #include <zephyr.h> etc should work. Martin Dne 02.11.2020 v 9:37

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

Hi all, There is a network forum meeting tomorrow Tue 3 Nov at 8AM PST / 17.00 CET. Current agenda: - WiFi L2 API for non-offloaded devices. See related issue at

Hello, I am studying this which mentions that the MCUboot is placed to immutable section of flash. How is this implemented? I can not see anywhere information about immutable MCUboot partition.

Hi, try this, I hope it will work #define TEMP_SENSOR_NAME "TEMP_0" int valid = 0; const struct device *tempSensor

Hi, I would recommend looking at samples\bluetooth\peripheral_ht\src I managed to create my code for nrf52832 based on that sample. If you have problems with

Hello, I am looking for some some nRF5340 example code that reads the nRF5340 die temperature using zephyr APIs. I've looked at previous posts but I could only find this one

Hello, I need to communicate with an SPI device (Semtech LR1110) connected to the nordic SoC nRF5340 via its SPI peripheral. I have the driver source code but I am not sure about the steps I need to

Hi, You should just need to add it to the build system's Kconfig and CMakeLists.txt hierarchy like any other file in your module. There are worked examples

Adding an out of tree board is easy, I just set the variable BOARD_ROOT and the build system happily finds my_custom_board. This is nicely described by following the links from here:

There's a GitHub issue around that: https://github.com/zephyrproject-rtos/zephyr/issues/23076

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

I have a question about heap usage monitoring.  Apologies if this is the wrong place to ask, please feel free to point me elsewhere if that is the case. I'm using Zephyr on a Nordic NRF53 chip and I

I solved the issue. The size should be multiple of 4096 (sector size). An other problem that I am facing is that when I run the lwm2m-client over openthread and the last address of the

Does zephyr only supports PSK for the DTLS (e.g echo client, lwm2m client). I haven't seen anything about RPK using ECC. On 7/20/20 5:48 PM, Stefan Hristozov wrote: --

Hi, Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0-beta-1 Please download and try things out and report any issues. Please report

Ok, found the issue: It was do to pin mapping naming. I was assuming that the pinmaps in Arduino D5, D6, and so on, corresponded to a direct GPIO map, so D5->GPIO_5 and so on... and that's not

Have you done the initialization by running gpio_pin_configure with GPIO_OUTPUT_ACTIVE as third argument ? Just to be clear, you´re trying to set pin p0.05 ? That´s located on chip pin7 (QFN48 pkg)

Hi, No MCUBoot. And yes, the board boots correctly and I can use GDB to debug. I can see the GPIO driver calls, the values that are set and so on. My prj.conf file is as simple as it can get:

Are you sure that your board boots correctly? ( debug through gdb or just simple serial output ) What version of the SDK are you using? Is MCUBoot activated in your prj.conf?