NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 2 [ZEP-1429] NXP MCR20A Driver https://jira.zephyrproject.org/browse/ZEP-1429 [ZEP-1498] commit-message.py

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/10107 : kernel: including legacy.h depends on CONFIG_LEGACY_KERNEL - https://gerrit.zephyrproject.org/r/10114 : sensor: remove unused

Hi, Well it seems the address is random: ca:2e:39:48:00:77 (random), should you should pass 2 instead of 1 after the address. -- Luiz Augusto von Dentz

Hello, Current "git describe" for the master gives "v1.5.0-3830-gecd209f". This is a little bit unfortunate, especially that soon after 1.6.0 it was like "v1.6.0-27-gb6fb798". I assume there were

Hi Christer, I agree with the observation that gpio/pinmux configuration is overcomplicated. Your proposal is interesting and look rather easy to use. Maybe you can also have a look to Adam's

Hi Jack If you want to develop driver based on STM32Cube HAL, you could check serial or pwm drivers as example. You can also find other examples of using HAL in Cube SDK that you could download from

https://gerrit.zephyrproject.org/r/#/c/8708/ Thanks Baohong Sent: Monday, January 16, 2017 4:13 AM To: Liu, Baohong <baohong.liu(a)intel.com>; devel(a)lists.zephyrproject.org Cc: Estrada, Giovani

if someone can write some document for how to use hal drivers(eg,stm32 cube) to write drivers or give an example for that ? I really want use Zephyr for new project, but not familiar with the

NEW JIRA items within last 24 hours: 2 [ZEP-1582] How to create a Zephyr ROM library https://jira.zephyrproject.org/browse/ZEP-1582 [ZEP-1581] [nRF52832] Blinky hangs after some minutes

[...] As far as I can see there is no documentation or examples in Zephyr that give a clue as to how DMA can be used with device drivers. So it's very difficult to review a DMA API without some more

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/10083 : tests/context: fix Coverity warning about array overrun - https://gerrit.zephyrproject.org/r/10067 : doc: make build process

Hi Marcus, If you use "select", then the dependencies of that select are not selected by default. This makes "select" a bit cumbersome and error prone to use IMHO.  Cheers, Jukka

Hi Liu We have finalized zephyr 1.6 version for our project there is any patch available for zephyr 1.6 , which I can install and use ARC to directly access GPIO including AON_GPIO and SPI

Hi! I noticed this review fly by: https://gerrit.zephyrproject.org/r/#/c/9982/ Which essentially adjusts a Kconfig to have an SPI driver Kconfig explicitly select a GPIO driver when it needs the

Hi Christer, Thanks in advance for these tasks. For USB support on STM32, it would be great that this work could benefit to the whole STM32 family. STM32Cube SDK could help you in implementing a

Hi Piotr, You should indeed first look at Zephyr documentation, and particularly i2c API. Then, regarding STM32 driver/IP, there are several sources that could help you to develop I2C driver for

Hello, When building, some BOARDs will generate both .bin and .hex, but others only .bin. Is there a build switch to control this ? My current stupid method is that, enter the directory where

Hi Christer, We have a bunch of USB device stuff under "subsys/usb/*". In brief we have support for the following device classes : CDC ACM - uart over usb Mass storage Webusb You can exercise

Hi all, BTW, for RFC patches like this that break the build, should I submit them to Gerrit instead or do you prefer to see them on the list? I've just managed to port Zephyr to my STM32F405 based

Hi all, I have a bunch of STM32F042/072/405 based boards that I'm currently running ChibiOS on. I'm thinking about porting Zephyr to these boards and also try to add support for the USB device in