HI all: in the directory zephyr/subsys/debug/, gdb_server.c used for what and what scenario can we use this function? can this be used on arm ? what the difference between it and the

Hello, I am working off of Zephyr 1.5 in the nanokernel configuration on a custom Intel Curie board. We have a number of fibers running on both cores, but seem to be having trouble with fibers on

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/11306 : xtensa_sim_console: fix simcall - https://gerrit.zephyrproject.org/r/11307 : xtensa/soc: drop bss segments from PHDR table -

Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: Congratulations, and thanks for applying the v1.7.99 tag on master, as discussed previously. "git describe" is now happy: $ git

PRI is *the* solution, stop trying to paddle against the current ;-) Cheers /Marcus

So I was looking at moving minimal libc’s typedef of {u}int32_t to match newlib. It looks all platforms except elfiamcu define: #define __INT32_TYPE__ long int #define __UINT32_TYPE__ long

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/11252 : kernel/sched: protect thread sched_lock with compiler barriers - https://gerrit.zephyrproject.org/r/11272 : Bluetooth: HFP HF:

Hi, With a slight delay, we are pleased to announce the first release candidate of Zephyr 1.7 with a large set of new features and additional hardware support. Zephyr 1.7 will introduce 2 new

Hello, The current Zephyr Sensor API assumes that devices have a single channel of a particular type. Although this may be the most common case for most devices, it is not a rule (e.g. SI1153 can

Hi Paul, thanks for the very useful hints und links! /apps_structure.html#support-for-building-third-party-library-code I didn't know about these docs, thanks! This is something i really looked

Alright, I'll follow your advice then. I agree that, ultimately, Device Tree and Kconfig files should be completely separate anyway. Best regards, -- Geoffrey Le Gourriérec

Hello Richard, Richard Peters <mail@...> wrote: This mail crosses its way with one you sent me privately, about doing the same thing with MicroPython, so let me try to answer both

Hi Geoff, While it is probably a good idea to look for good research solutions we actually need to make sense what it does, and what doesn't make sense, for zephyr. Pretty much any layer that

Hi Community, I use these flags to link jerryscript against zephyr in my project makefile: ALL_LIBS += jerry-core export ALL_LIBS LDFLAGS_zephyr += "-L $(JERRYOUT)/lib" export LDFLAGS_zephyr 1.

On Nios II we currently just support the very simple IIC (Internal Interrupt Controller) and nested interrupts aren't possible. Andrew

Should be supported on architectures where the hardware has support for it. It is a feature of the kernel. ARM, ARC, x86 do support it. [ChuckJ] To clarify. On ARC, FIRQ can be nested on top of

While I don't personally have answers to these buffer-management questions, I am certain they are well-studied, because they are intermingled with lots of other well-studied questions and use-cases

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/11230 : RFC drivers/timer: Refined version of nRF RTC driver. - https://gerrit.zephyrproject.org/r/11233 : Bluetooth: SMP: Fix passkey

Hi, Should be supported on architectures where the hardware has support for it. It is a feature of the kernel. ARM, ARC, x86 do support it. Not entirely sure about Nios2 and

<jukka.rissanen@...> wrote: We do however still need to figure out, for udp, how to prevent: - rx path starving tx path to dead lock - multiple tx paths deadlocking (by attempting to