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:

Jun, You can use CONFIG_STACK_USAGE to have the build system generate the .su files which summarize the stack usage (if computable at compile time) of all the functions in all the files. You can

Enable CONFIG_INIT_STACKS. Use STACK_ANALYZE() from include/misc/stack.h to see how much of your thread stack has been used, that should help you to tune the size value. HTH, Andrew

Hi there, I’m wondering by which means to figure out the static stack size for a thread? Thank you! Jun Li NTG | Intel Corporation | Santa Clara

Thank you for the patch. The test case tests/kernel/test_build should have caught this in its newlib configuration, but the build passes in that scenario. I'm looking into why this is the case.

Andrew, Thanks for the information. It turns out an typo in the xtensa linker.ld. newlib references "__heap_sentry" but "_heap_sentry" is defined in the linker script. I've created a PR #1072 for

Aska, __heap_sentry is a linker symbol, defined for qemu_xtensa in the linker script, arch/xtensa/soc/sample_controller/linker.ld, near the bottom. It marks the beginning of a RAM area used for

Paul, I might take some time to investigate it. But I think I should exclude qemu_xtensa as a short-term workaround. Regards. Aska

<massimiliano.cialdi@...> wrote: So if there are pin differences between the two, then anything non generic needs to be removed from the .dtsi and put inside a more specific .dtsi file that

Fo the nucleo_f412zg there is the file zephyr/dts/arm/nucleo_f412zg.dts that includes st/stm32f412.dtsi and then #include <st/stm32f412-pinctrl.dtsi> #include <st/stm32f411.dtsi> stm32f411.dtsi

<massimiliano.cialdi@...> wrote: Looking at the drivers/clock_control/stm32_ll_clock.c, they use switch statements to steer the programming for the clock enables. The actual call makes a