Hi, We are excited to announce the release of Zephyr RTOS version 2.1.0! Major enhancements with this release include (but are not limited to): Normalized APIs across all architectures. Expanded suppo

Hi Zephyr developers, Zephyr 2.1.0-rc3 release candidate has been tagged. Current issue status: Priority Count Has PR High 0 - Medium 17 1 Testing Zephyr release candidate is requested; please, test t

The v2.1.0 release notes are lacking any updates for the following sections: Kernel Bluetooth Libraries/Subsystems HALs Documentation Tests and Samples Please help fill in these details. David David L

The problem has been addressed and the release candidate is now live. David Leach

There was a problem with how I attempted to create this release. In the process of fixing it and will send an update when ready. Sorry for any inconvenience. David Leach

Hi Zephyr developers, Zephyr 2.1.0-rc2 release candidate has been tagged. Current issue status: Priority Count Has PR High 0 - Medium 30 11 To get to an RC3 tag and eventual final release, we need get

Let me add a bit of emphasis. If you are working on a bug fix for a bug marked as “low priority” you should stop and move to one marked “medium” or “high” priority. We can pick up the low priority bug

The v2.1.0-rc1 is under test. The release schedule was to have a RC3 tagged by this weekend but we have not achieved RC2 level of quality yet. Current tradition is to have zero high priority bugs befo

Folks, As we get closer to completing release v2.1.0 we need the release notes updated with the major accomplishes and changes made to the various subsystems. Please start providing updates for us to

Hi Zephyr developers, Zephyr 2.1.0-rc1 release candidate has been tagged. All required features scheduled for 2.1 release are now merged into master. As of now we are in the stabilization phase for 2.

It looks like we need a PR to master to change doc/config.py to reference 1.14.1

For historical tracking, the error is because I have ZEPHYR_BASE environment variable set. Carles and I agree that the error message is not very helpful. David

Carles, See the following: dleach@dleach-test:~/work$ west init zephyrproject2 FATAL ERROR: already in an installation (/home/dleach/work/zephyrproject), aborting

I want to be able to have multiple installations on my system. To expand out my example: /home/dleach/work/zephyrproject modules zephyr net-tools tools .west /home/dleach/work/mytestzephyrproject modu

Yeah, I'm trying to do some work to add a module when requires 1) adding the module, 2) updating west.yaml, and 3) making changes to the zephyr CMakeLists.txt tree to build the module. But I didn't wa

no. I want to initialize a second Zephyr project area in parallel. So for example: /home/dleach/work/zephyrproject /home/dleach/work/zephyrproject2 David

Can I use west to initialize multiple working directories? I’m experimenting with adding a module and I wanted to a setup so I created a ‘zephyrproject_2’ directory and ran a ‘west init’ command with

Are there any tricks to get the nrf52 board to be able to use the Zephyr build chain from within a VirtualBox Linux machine? When ever I run ‘ninja -Cbuild flash’ the Jlink usb device disconnects from

With west merged in does that mean we can no longer use the cmake/ninja debug type of flow (I'm seeing a problem). If not, will the west setup instructions work on an existing working directory or do

I have run across a build problem that appears to impact Arm platforms. The problem involves improper discarding of ‘const’ defined variables that are only referenced within a single file getting part