So, I found out about the linker problem: KFLAGS_*FLAGS go all the way to the assembler, but not the linker. Also, LDFLAGS is for LD, which is still GNU's, so I can't add Clang flags to it. But the

Hi Folks, I've been trying Clang builds with Zephyr and it seems that the Makefile has some support, but scattered all over the place and it doesn't handle the simple case any more. The use case is

Hi, Zephyr v1.4.0-rc2 has been tagged.  Remember that the target date for the 1.4.0 release is end of this week, don't forget to update your JIRAs items. Below is the list of changes since

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 1 [ZEP-424] AON counter driver needs to add driver API reentrancy support

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2349 : samples/task_profiler: remove "dump" logging - https://gerrit.zephyrproject.org/r/2346 : samples/task_profiler: modifications

NEW JIRA items within last 24 hours: 3 [ZEP-421] Application Development Primer Rewrite https://jira.zephyrproject.org/browse/ZEP-421 [ZEP-422] Cannot create Bluetooth firmware for the Arduino

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2335 : Bluetooth: GATT: Remove obsolete flush callback - https://gerrit.zephyrproject.org/r/2334 : drivers/nble: Add buffer pool for

Sure this is true, on a UP system the effect would be to simply disable preemption. I think the semantics are the same regardless of the underlying implementation though, right? Every once in a while

I didn't think zflash was supported any more. I followed https://software.intel.com/en-us/node/605211 and was able to to get my D2000 CRB into a usable state. Henry

Boosting priority of the invoking task may not be what we want to achieve. In case of work_queue (correct me if I am wrong) we have an interrupt handler that offloads the long work to the fiber for

You don't need spinlocks in a 1-CPU system. You're probably thinking of a scheduler lock. Could be done like that too. I introduce a lightweight recursive scheduler lock that is to be used by some

I've always thought this was one of the odder features of the OS. I think we should take a step back and consider whether this API ought to be removed from the OS entirely and replaced with something

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 0 CLOSED JIRA items within last 24 hours: 1 [ZEP-213] (Fixed) net_set_mac() didn't deal wtih NULL

Hi Lukasz, That doesn't sound good, hope you're able to recover. I don't have a datasheet for Arduino 101, but OpenOCD and Zephyr SDK are on the Zephyr project git database like the Zephyr sources.

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2318 : sensor: ak8975: add support for MPU9150 - https://gerrit.zephyrproject.org/r/2317 : sensor: add driver for AK8975

Another thought occurred to me over the weekend. See [AL] below. -- Al

Hi, Zephyr v1.4.0-rc1 has been tagged. The merge window for new features is now closed.  The target date for the 1.4.0 release is end of this week. Below is the list of changes since

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2309 : samples/net/mqtt: Update README file and code cleanup - https://gerrit.zephyrproject.org/r/2295 : drivers/nble: Implement

Hi Vicente, Scripts and guide (README) for setting up zephyr profiling in your application has been added in sample/task_profiler Do not hesitate to come back to me in case of

Thanks Ruud! I will have a look at the link you mentioned, but I think I managed to brick my Arduino. Do you know where I can find any sensible data sheet for it and the sources of OpenOCD used by