NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/8997 : samples: net: Add echo_client build test for CC2520 configuration - https://gerrit.zephyrproject.org/r/8998 : scripts: fix

[...] Yes, I had seen sys_kernel_version_get(), but what I was trying to do was get this information at compile time so that some timer code I was using could be supported in both 1.5 and 1.6 versions

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/8968 : samples: added disco_fever app - https://gerrit.zephyrproject.org/r/8967 : toolchain: Add a popcount macro for GCC -

Here is a snippet: uint32_t version = sys_kernel_version_get(); printk("Zephyr version %d.%d.%d\n", SYS_KERNEL_VER_MAJOR(version),

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/8958 : Bluetooth: Kconfig: Fix logging dependency on printk - https://gerrit.zephyrproject.org/r/8961 : drivers: QMSI counter: Update

So I think I misunderstood since "console" is a name can have various meanings. But I think Zephyr's use of console is the one-and-only-one place your printk's go ... True? The notion of a CLI or

We do support the use case of selecting which UART to use for console, for instance on Nios II we used to have the JTAG UART as the default console instead of the 16550. But the way this is configured

Well actually, I guess there are two concepts: * "console" which could be printk's from even kernel code - going to one-and-only-one place * "cli" - command line interface, which might

Actually, it would be more ideal if on any given UART port, you could designate whether or not it should run a console, or be left to be open by the Application for some other purpose. If you had 2

Hi all, One of the points was that the crypto algorithms and cyphers of mbedTLS cover the ones required for secure connection protocols (e.g. Thread). The mbedTLS library is more oriented to use by

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/8945 : sensor: remove SENSOR_VALUE_TYPE_INT - https://gerrit.zephyrproject.org/r/8949 : samples: zperf: Correct the include files

Adding the various maintainers CC... Your thoughts/views on this would be much appreciated... <marcus.shawcroft(a)gmail.com> wrote:

Hi, Have a look at samples/basic/button/src/main.c for instance. Zephyr GPIO API first requires to configure it through gpio_pin_configure() and then to setup a callback and enabled/disable the

Hello Johan, I was thinking on adding an additional parameter to the callbacks as seen in some cb's that receive the "user_data" parameter. So, it seems the best way to solve this is with

Hi Flavio, At least I'm using CONTAINER_OF() to accomplish this. I think that's the main idea of how these APIs are designed (same with k_work as well). So you embed these objects in your "user data"

Hi all, I'm reviewing my new code for Atmel SAM low level Ethernet driver and there is one place where I have a troubling use of k_sem_init() function. Very shortly my situation: As is typically the

Hello, After playing a bit with k_timer and the expiry and stop callbacks, I realize that there is no way to manipulate application specific data inside the callbacks. These routines are implemented

Hi tomasz and mahendra what #define to be used in gpio_pin_configure to mask and unmask gpio interrupt ? can you help me with an example ? tomasz.bursztyka(a)linux.intel.com> wrote:

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/8905 : boards: arm: Refactor the GPIO and UART dependencies - https://gerrit.zephyrproject.org/r/8894 : tests: spi_test: refactor and

Hi, The second one. Always use the Zephyr GPIO API, so include/gpio.h Tomasz