Hi, Zephyr v1.1.0 was tagged 2 days ago and merge window for the next release is no open. Release notes and other details will be posted on the website. Here is the log of changes since the rc1. Merge

Hi, As per suggestion from Gerrit comment, moving the discussion to mailing list. Background -------------- On Quark (SE and D2000), there are Always On Counter (free running) and Always ON Periodic T

Hi, Im looking to use the zephyr project spi driver for writing to the SD card slot on the FRDM K64f board. So far I have found little to no documentation on how to use the spi driver. For example how

Problem statement: We currently have two separate implementations on how to connect interrupts on all arches: static IRQs and dynamic IRQs. On x86 only we also have static and dynamic APIs for connect

Hi, I'd like to make a proposal for enhancement of driver API callbacks, but before jumping to code I'd like to get some feedback first. Right now, whenever a call to an API is made, we directly jump

Hi list, I've done a PoC port of Zephyr to STM32F103VE MCU on a EB-STM_06 dev board. The port is rather minimal, most of the configuration is hardcoded. The MCU is configured to use internal HSI clock

Folks, Not that big of a change for a lot of people, but I pushed a revision to documentation yesterday that enforces a 8-char tabs/80 column coding style. Basically, this makes our coding style the s

Hi everyone, I have uploaded a new iteration of the sensor API patches to Gerrit, you can find them at [1]. We hope to address some of the concerns regarding memory consumption of sensor drivers. For

Here are the revised RFCs that attempts to state the problems, reasons and solutions more clearly Thanks to Dan for spending a lot of time with me in making it right. (It was a challenge to put things

Problem Statement: Power management Kconfig flags are not consistent and hierarchy is not clear Why this is a problem: ----------------------------- The names include terms like “ADVANCED” which are n

Problem Statement: Zephyr needs to provide an architecture independent method for power management application to invoke a low power state on the CPU. Why this is a problem: --------------------------

Problem Statement: Zephyr needs to provide an architecture independent method for power management application to invoke the SOC Deep Sleep functionality. Why this is a problem: ----------------------

Problem Statement: Add OS infrastructure to enable application-based power management policies, which is architecture independent, supports microkernel and nanokernel and the interface clearly identif

Hi, i just read the source code of zephyr. I have found an error into : drivers/spi/spi_k64.c line 204, baud_rate_prescaler is use instead of baud_rate_scaler (causes an out of bound ) regards, Yves-G

This is the second attempt to define a common system logging API, Original thread can be seen here: https://lists.zephyrproject.org/archives/list/devel(a)lists.zephyrproject .org/thread/A6CROK67VKFKFS

Problem Statement: Not all Zephyr kernel drivers provide the same interfaces. Why this is a problem: ----------------------------- The Zephyr kernel currently has devices that are essential for core O

Why do you need this for the LOAPIC/IOAPIC? All its functions are private to the kernel and do not require a device pointer. Please provide a specific example on where you would need to run device_get

Maybe I was misunderstood in my email about the structure. I was suggesting to move the SoCs directly under soc/ and ski[ the st_stm32 level. If we are to do things the same way across architecture we

Hi, The issue has been reported and being addressed. Still not known what the issue is exactly :( Anas

I have installed gcc,g++,and sdk , the environment shows that : ZEPHYR_SDK_INSTALL_DIR=/opt/zephyr-sdkOLDPWD=/shrd/microkernelZEPHYR_BASE=/shrd/zephyrPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr