Hi Carles, I though k_timer wouldn't be that useful after k_work/k_delayed_work was introduced, especially given its blocking nature it usually much easier to just use the system work queue, though

Hi Carles, As you describe the behavior it sounds like a bug to me that, indeed, needs a fix. Tomasz

Hi,

Hi all, We've had 2 different issues recently coming from the fact that K_NO_WAIT and K_FOREVER do not seem to work with all of the kernel APIs. They are the following: 1) Calling k_timer_start()

Hello Andrzej, Andrzej Kaczmarek <andrzej.kaczmarek@...> wrote: Well, NFFS is a *flash* filesystem, it's expected that it would require more specific underlying device type than a generic FS

Hi all, I'm porting NFFS (Newtron Flash File System) from Mynewt to Zephyr. The original fs implementation has direct access to flash, i.e. it will read, write and erase data to/from flash directly

By the way, is ADC API going to be revised soon or is it actual and sufficient? Michał Kruszewski Sent with ProtonMail Secure Email.

Hi I am just working on ARC em starter_kit. There are several configurations for em_starter_kit, em7d, em9d, em11d. Different configurations have different parameters, i.e. the default value

Hi all, We have just tagged Zephyr 1.9.0 RC1 which mean we are feature frozen for the 1.9 release planned for the end of August. Starting with RC1 we will only accept changes introducing bug

Hi all, I am resending this email, slightly modified from its original version, since the work on the build system has resumed and we would like to fish for early feedback regarding the work that

Hi Piotr, Good point. ADC API was designed some months before PM one, and was not revised once the later came in. Sounds like you can throw a PR to remove these.

Hi all, The ADC driver API specifies adc_enable / adc_disable functions. The doxygen documentation of adc_enable function states: "This routine enables the ADC hardware block for data

The deeper context here is that we have a number of timing-sensitive tests which sometimes fall over if the server running sanitycheck is heavily loaded. AFAICT, this is due to QEMU trying to

Hi, There was an issue in how we re-run sanitycheck on failed tests (retry) to eliminate false positive due to heavy load and Qemu not being able to deal with that. This is now fixed. Anas

Hello Maciej, Maciej Dębski <maciej.debski@...> wrote: *All* tests fail sooner or later, with or without a reason. (As Murphy would add, non-tests fail sooner or later too.) If you're sure

Hello, I just posted a pull request for my nucleo f030r8 support. Here it is: https://github.com/zephyrproject-rtos/zephyr/pull/1103 The shippable ran all the tests correctly, just one with a failure,

Hello, I just posted a pull request for my nucleo f030r8 support. Here it is: https://github.com/zephyrproject-rtos/zephyr/pull/1103 The shippable ran all the tests correctly, just one with a failure,

Hi Jehudi, The Client models would typically be operated by a device with a rich & interactive user interface. As something like that is rarely found on Zephyr-based device only the Server models are

Hi, In the bluetooth mesh samples it is shown how to set-up and use the configuration server and health server root models. Is there also an example on how to use the configuration client and health

Great! Thank you, Mike and Andrew! From: Michael Rosen <michael.r.rosen@...> Date: Thursday, August 10, 2017 at 11:41 To: "Li, Jun R" <jun.r.li@...>, "zephyr-devel@..." <zephyr-devel@...> Subject: