Hi Lukasz, Thanks for this - the use of j_s.nd is not required, or even wrong in this case. The nd 'mode' is for conditional branches and indicates to only execute the next instruction (delay slot)

Dear All: We're encountering zephyr image flash issue that we failed to flash the zephyr OS/Bootloader to Quark D2000 CRB with the following

Nice. I was able to flash it on the 101, got the shell and was able to run the test.. Maybe I am missing something, but should I be able to type into JS code into the shell directly? Every time I do

The scheduler starts automatically when the kernel is done with its initialization. Tasks put in the EXE group in the MDEF file are started automatically. The others can be started via task_start().

Hi I have worked on FreeRTOS. Now started to use Zephyr RTOS in a project Please help me on the following 1. Is there any function in Zephyr RTOS to start the scheduler similar

Sergio, that looks awesome. can't wait to give it a try this weekend. thankgregg sergio.martinez.rodriguez(a)intel.com> wrote:

Hi there, I am working on getting an integration with JerryScript and Zephyr for the Arduino 101 without touching any of the two build systems, similar to the other architectures and systems JS

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2238 : ext: Import Nordic MDK header files - https://gerrit.zephyrproject.org/r/2234 : Bluetooth: tester: Add support for indications

Hi there, I have recently started playing with Zephyr and decided to see whether I can build it for Arduino 101 with the mainline toolchain. I compiled the following for both i586-none-elfiamcu and

Hi there, I have recently started playing with Zephyr and decided to see whether I can build it for Arduino 101 with the mainline toolchain. I compiled the following for both i586-none-elfiamcu and

Kumar, I would prefer 1 patch, since it is fixing one issue ☺ Thanks, Anas

Anas, I’ve got a patch that cleans up all the whitespace issues is the Kconfig files. Think we should try and merge this sooner than later, to reduce propagation of this issue going forward. I

Hi there, I subscribe. Leaving it alone and pointing to cmsis/Include is my preference as well. Carles

Don’t have any strong preference here, as long as it is hidden from the users ☺ Anas

Why do we need this change if we intend to point the include path to be cmsis/Include. I don’t think we should be changing this. It should get hidden by something

Great. Will wait for that. Anas

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 2 [ZEP-267] nios2: implement _new_thread() https://jira.zephyrproject.org/browse/ZEP-267 [ZEP-383] spi flash

Should be done now, as long as the path to the new location is provided to the compiler. We now simply include the cmsis file directly assuming it¹s in the include path: #include