NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 0 CLOSED JIRA items within last 24 hours: 3 [ZEP-538] (Fixed) doc: missing steps to boot up Galileo Gen 2 with a USB

NEW within last 24 hours: UPDATED within last 24 hours: - https://gerrit.zephyrproject.org/r/4081 : fix doxygen error doc: Update Power Management device driver API 1. Have one function that can be

Hi all, I did Abandon to all the below patches and will deliver again as one big change (please note: all the drivers changes are quite similar) . Thanks, Amir Kaplan

NEW JIRA items within last 24 hours: 2 [ZEP-724] build on windows failed: 'make: execvp: uname: File or path name too long' https://jira.zephyrproject.org/browse/ZEP-724 [ZEP-725] CI tag build

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4205 : recipes-devtools/gcc: newlib-stdint.h: Remove 32 bit longs - https://gerrit.zephyrproject.org/r/4210 : grub: Tweak

Hello Jukka,

Hello All, New RC tagged. Thanks to everyone for your contributions! Anas Nashif (1): MAINTAINERS: add ARM and ARC architecture maintainers Andrew Boie (19): samples: hello_world: build

NEW JIRA items within last 24 hours: 2 [ZEP-723] Sanity Crashes with "FileNotFound" exception when running samples/static_lib/test https://jira.zephyrproject.org/browse/ZEP-723 [ZEP-722]

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4165 : net: drivers: Add a fake ieee802154 radio driver for qemu - https://gerrit.zephyrproject.org/r/4203 : net: samples: Fix the

Patches for these items can be now found in https://gerrit.zephyrproject.org/r/#/c/4199/ Cheers, Jukka

Hi, For testing, simply mocking out the kernel dependencies is enough to run unit tests. See tests/unit/net/buf from my patch for a simple case of removing the dependency to nano_fifo. Similarily,

2016-08-19 4:25 GMT+02:00 Ricardo Salveti <ricardo.salveti(a)linaro.org>: Interesting. Will take a look at your project. An STM32F4 should be more similar to the F3 then mainstream F1 support, which

Hi Paul, Yes, your analysis is correct. The CONFIG_NET_TESTING was setup so that we could automate the qemu-qemu testing. Unfortunately the documentation about this was not very clear as you

Not related to your issue, but we also got a work-in-progress port for STM32F4 last week, in case that is useful for you. Currently working at https://github.com/rsalveti/zephyr/commits/stm32-dev, and

Jaakko, I am trying to understand the usage of your proposed test framework. It is running on host, without dependency on Qemu, HW platform and rest of Zephyr OS, right? From Zephyr

Not at this point. The address of main() will be loaded from the stack of the main thread when the CPU returns from the PendSV exception and the main thread is the next one to run. Actually it will be

Ah, no, this might be OK then. 0xfffffffd gets put by the CPU when taking the SVC exception and entering __svc(). If this is the very first call to _Swap() when the kernel boots, that call will never

2016-08-18 22:55 GMT+02:00 Benjamin Walsh <benjamin.walsh(a)windriver.com>: But if I understand this correctly, shouldn't LR contain the address of main at this stage. The code says: /* context

2016-08-18 22:55 GMT+02:00 Benjamin Walsh <benjamin.walsh(a)windriver.com>: It seems to be corrupted when entering __svc, but once inside the __svc it seems to have a value of what you where

^^^^^^^^^ Contents of lr looks corrupted: it should be something like 0xfffffffd. Is it OK when entering __svc() ? Are you trying to run a stock project or is it your own