Date   

SDK 0.11.4 Release

Kumar Gala
 

Hi,

Some minor fixes related to newlib and a packaging related fix for the individual arch toolchain packages (missing the cmake files)

The SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.4

Please download and try things out and report any issues.

- General:
* Fixed issue with cmake files not being installed in arch specific
toolchan packages

- newlib:
* Fix setting of -DMISSING_SYSCALL_NAMES consistent on all builds
* Set march=pentium for 32-bit x86 build

- k


Zephyr v2.3.0 released

Carles Cufi
 

Hi all,

We are pleased to announce the release of Zephyr RTOS version 2.3.0.

Major enhancements with this release include:

* A new Zephyr CMake package has been introduced, reducing the need for
environment variables

* A new Devicetree API, based on hierarchical macros, has been introduced. This
new API allows the C code to access virtually all nodes and properties in a
clean, organized fashion

* The kernel timeout API has been overhauled to be flexible and configurable,
with future support for features like 64-bit and absolute timeouts in mind

* A new k_heap/sys_heap heap allocator has been introduced, with much better
performance than the existing k_mem_pool/sys_mem_pool
Zephyr now integrates with the TF-M (Trusted Firmware M) PSA-compliant
framework

* The Bluetooth Low Energy Host now supports LE Advertising Extensions

* The CMSIS-DSP library is now included and integrated

The detailed release notes can be found here:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.3.0

The next release, v2.4.0, is tentatively scheduled for September 25th 2020.

I would like to thank everybody who contributed to this release, be it with code, feedback or documentation.

Thanks,

Carles


Zephyr 2.3.0-rc2 tagged

Carles Cufi
 

Hi all,

The second release candidate for Zephyr 2.3.0 has now been tagged (v2.3.0-rc2).

The current issue counts are:

- 1 high-priority bug
- 16 medium-priority bugs

The high-priority bug (#23364) has a PR (#25954), but a waiver to release without a fix for this particular issue has been requested, due to the invasiveness of the Pull Request and the risk of merging it this late in the release cycle. A note would be added to the release notes and a subsequent 2.3.1 would be released to address this issue.

During the days left until the release, I would encourage everybody to test thoroughly and file any issues found so that they can be fixed as quickly as possible. Additionally, there are still sections in the release notes that need filling, those can be tracked here:
https://github.com/zephyrproject-rtos/zephyr/issues/25869

The full release log can be found here:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.3.0-rc2

More details about Zephyr releases can found on the pages below:
https://docs.zephyrproject.org/latest/development_process/release_process.html
https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

The final release remains scheduled for June 5th.

Thank you to everybody who contributed to this release so far!

Carles


Zephyr 2.2.1 released

Johan Hedberg
 

Hi,

We are excited to announce the release of Zephyr 2.2.1, the first maintenance release of Zephyr 2.2.

This is primarily a bug fix release, concentrating on security vulnerabilities and issues affecting Bluetooth qualification.

The following security vulnerabilities (CVEs) have been addressed:

- CVE-2020-10028
- CVE-2020-10060
- CVE-2020-10063
- CVE-2020-10066

More details on these can be found in https://docs.zephyrproject.org/latest/security/vulnerabilities.html

A list of all issues fixed or addressed can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.2.1

Thank you to everyone who contributed to this release!

Johan


SDK 0.11.3 Release

Kumar Gala
 

Hi,

Some fixes based on usage of SDK v0.11.x and addition of QEMU for ARC, cmake package support, and some changes to how we build GDB. Please take NOTE of the changes w/regards to GDB.

The SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.3

Please download and try things out and report any issues.

- General:
* Added cmake package support to make it easier to find toolchain
* Add a -[no]rc argument to install script to allow skipping update
query for .zephyrrc

- QEMU:
* Add support for ARC
* xilinx_qemu: Fix WFI instruction for icount mode
* SPARC: fix issue with timer in QEMU machine AT697
* Add support for changing CPU type in sifive_e machine.

- GDB:
- Added a gdb build that doesn't support python (TARGET-gdb-no-py)

NOTE: The name of the gdb executable will change in the next major
release. To maintain compatibility with previous 0.11.x we left the
TARGET-gdb as the version that supports python. In 0.12.x we will change
it such that TARGET-gdb will NOT support python and thus work everywhere
and TARGET-gdb-py will be the version that supports python.

- Changed python support to build against python3.8. This is an attempt to
have the python support work on a larger number of distributions.

NOTE: This may require install a python3.8 package on your system if
python3.8 is not available. On fedora systems that can be accomplished by:

`sudo dnf install python38`

On ubuntu systems that can be accomplished by:

`sudo apt get install python3.8-dev`

- OpenOCD:
* Pull in a fix for ARC SMP support

- GCC:
- Fix build issue with CRC32 intrinsics included from arm_acle.h on ARM
compiler.Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k


Zephyr 2.3.0-rc1 tagged

Carles Cufi
 

Hi all,

The first release candidate for Zephyr 2.3.0 has now been tagged (v2.3.0-rc1).

The merge window for features and enhancements is now closed for this release, and it will remain closed until 2.3.0 is released; the stabilization period is now open.
During said stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master.
Additional features or enhancements for the 2.3 release will require approval by the TSC.
As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers.
Testing Zephyr master branch during the stabilization period is also requested; please test the code base and file bug reports so they can be addressed before the release deadline.

The full release log can be found here:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.3.0-rc1

More details about Zephyr releases can found on the pages below:
https://docs.zephyrproject.org/latest/development_process/release_process.html
https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

The final release is tentatively scheduled for May 29th.

Note 1: You are of course free to send Pull Requests for new features in order to gather feedback early or collaborate with others, but the release team would like to encourage everyone to focus on bugfixes and documentation improvements to the larges extent possible, so that we can release 2.3.0 on time and in the best shape possible.
Note 2: If you have a feature or enhancement you would like to submit to the TSC, please tag the Pull Request in question with the "TSC" label, make sure it is approved and passing CI, and attend the next TSC meeting.

A big Thank You to everyone that contributed to this release so far, be it with code, reviews, documentation or any other type of contribution.

Thanks,

Carles


[2.3 release] Feature merge window close (M2) tomorrow

Carles Cufi
 

Hi all,

This is just a reminder that the feature merge window closes tomorrow, the 8th of May.
This means that any changes that are not bugfixes or documentation changes must be merged by then.

Since I doubt I will be able to go through all GitHub emails in time for tomorrow, please make sure that your PR shows in the following filter if you want it merged:

https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+base%3Amaster+review%3Aapproved+status%3Asuccess+-label%3ADNM+draft%3Afalse++milestone%3Av2.3.0

This means that your PR must be approved, must pass CI and its milestone must be set to v2.3.0.

If you have additional requests or need help, please email me or ping me on Slack.

Regards,

Carles


[2.3 release] Feature merge window close (M2) next week

Carles Cufi
 

Hi all,

This is just a reminder that the feature merge window close is on the 8th of May.
This means that any changes that are not bugfixes or documentation changes must be merged by then.

See the full timeline for the 2.3 release here:
https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management#actual-and-planned-milestone-dates

Thanks,

Carles


Zephyr 1.14.2 Released

Nashif, Anas
 

Hi,

We are excited to announce the release of Zephyr 1.14.2, the second maintenance release of Zephyr 1.14 (LTS). This release comes 1 year after 1.14.0 was released.

 

This is primarily a bug fix release with the following security vulnerabilities (CVEs) addressed:

  • CVE-2020-10019
  • CVE-2020-10021
  • CVE-2020-10022
  • CVE-2020-10023
  • CVE-2020-10024
  • CVE-2020-10027
  • CVE-2020-10028

 

A list of all issues fixes or addressed can be found here:

 

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v1.14.2

 

 

Thank you everyone for making this happen.

 

Anas


Re: Zephyr CMake package / find_package(Zephyr)

Kumar Gala
 

What version of west has 'zephyr-export’??

[galak@spiff zephyr]$ west -V
West version: v0.7.2
[galak@spiff zephyr]$ west zephyr-export
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'zephyr-export' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate', 'completion', 'boards', 'build', 'sign', 'flash', 'debug', 'debugserver', 'attach’)- k

- k

On Mar 30, 2020, at 8:31 AM, Rasmussen, Torsten <Torsten.Rasmussen@nordicsemi.no> wrote:

Hi All,

A new way of including boilerplate code has been introduced with this PR https://github.com/zephyrproject-rtos/zephyr/pull/23054

This means a simple Zephyr application now looks as:
# Find Zephyr. This also loads Zephyr's build system.
cmake_minimum_required(VERSION 3.13.1)
find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})
project(my_zephyr_app)

This means that developers no longer need to set ZEPHYR_BASE in their environment, but can let CMake find the Zephyr base using find_package().

For this to work, it is necessary to execute a new west command: `west zephyr-export`
This command only needs to be executed once, for example after a `west init`

All samples in Zephyr repository has been updated to use: find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})

To all downstream user having own Zephyr-based applications, you may switch to the new find_package() method.

Note: this new feature is fully compatible with the old `include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake)` design,
but if you keep using the old design, then it is still required to `source zephyr-env.sh` or execute `zephyr-env.cmd`.

Using the new `find_package()` remove the need to `source zephyr-env.sh`.

It is still possible to set the environment variable ZEPHYR_BASE, and doing so will overwrite the CMake package search functionality in Zephyr.

For more information on the new desgin, re-read the getting started guide (as the latest docs has not yet been build, this is a ):
https://docs.zephyrproject.org/latest/getting_started/index.html
https://docs.zephyrproject.org/latest/guides/zephyr_cmake_package.html


Best regards

Torsten


Zephyr CMake package / find_package(Zephyr)

Rasmussen, Torsten <Torsten.Rasmussen@...>
 

Hi All,

 

A new way of including boilerplate code has been introduced with this PR https://github.com/zephyrproject-rtos/zephyr/pull/23054

 

This means a simple Zephyr application now looks as:

# Find Zephyr. This also loads Zephyr's build system.

cmake_minimum_required(VERSION 3.13.1)

find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})

project(my_zephyr_app)

 

This means that developers no longer need to set ZEPHYR_BASE in their environment, but can let CMake find the Zephyr base using find_package().

 

For this to work, it is necessary to execute a new west command: `west zephyr-export`

This command only needs to be executed once, for example after a `west init`

 

All samples in Zephyr repository has been updated to use: find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})

 

To all downstream user having own Zephyr-based applications, you may switch to the new find_package() method.

 

Note: this new feature is fully compatible with the old `include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake)` design,

but if you keep using the old design, then it is still required to `source zephyr-env.sh` or execute `zephyr-env.cmd`.

 

Using the new `find_package()` remove the need to `source zephyr-env.sh`.

 

It is still possible to set the environment variable ZEPHYR_BASE, and doing so will overwrite the CMake package search functionality in Zephyr.

 

For more information on the new desgin, re-read the getting started guide (as the latest docs has not yet been build, this is a ):

https://docs.zephyrproject.org/latest/getting_started/index.html

https://docs.zephyrproject.org/latest/guides/zephyr_cmake_package.html

 

 

Best regards

 

Torsten

 


Zephyr 2.2 released

Johan Hedberg
 

Hi,

We are excited to announce the release of Zephyr RTOS version 2.2.0!

Major enhancements with this release include (but are not limited to):

* We added initial support for 64-bit ARMv8-A architecture (Experimental).
* CANopen protocol support through 3rd party CANopenNode stack
* LoRa support was added through integration of the Semtech LoRaWAN endpoint
stack and addition of a new SX1276 LoRa modem driver.

The detailed release notes can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.2.0

I would like to thank the community members who contributed to this release. There were a total of 2642 commits from 205 contributors in the development of 2.2. It has taken a lot of hard work from everyone in the Zephyr community!

Starting now, the tree is open for new features targeting the 2.3 release, which is tentatively scheduled for May 29th 2020.

Thanks again,

Johan


Zephyr 2.2.0-rc3 tagged

Johan Hedberg
 

Hi Zephyr developers,

We have now tagged Zephyr 2.2.0-rc3, i.e. we’re getting close to the final release. We’re currently at 15 medium priority bugs and no high priority bugs, so the release criteria are met (at least for now).

From now on I’ll handle all merges until the release. The focus should now be on testing, documentation updates and release notes. If all goes well the final release will be done later in the coming week.

The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.2.0-rc3

More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

Thanks to everybody who has contributed to this release!

Johan


Zephyr 2.2.0-rc2 tagged

Johan Hedberg
 

Hi Zephyr developers,

We have now tagged the second release candidate for Zephyr 2.2: 2.2.0-rc2.

We’re currently at 0 high priority bugs and 21 medium priority bugs. This is already close to the requirements for rc3 and the final release, which are 0 and 20 respectively.

Developers are requested to continue testing the release, filing bugs, and addressing any remaining bugs that are assigned to you. I would also encourage subsystem owners to take a look at their respective sections in doc/releases/release-notes-2.2.rst and submit updates in case your subsystem is still missing a change summary since the last release.

Looking at the original release schedule, it seems likely that we’ll need to push the final release from the end of this week to some time next week - we will discuss this in this week’s TSC call.

The full release log for 2.2.0-rc2 can be found here:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.2.0-rc2

More details about Zephyr releases is found here:
https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

Thanks to everybody who has contributed to this release!

Johan


SDK 0.11.2 Release

Kumar Gala
 

Hi,

Some fixes based on usage of SDK v0.11.x and addition of some new xtensa variants to enable work from the Sound Open Firmware Project (https://www.sofproject.org).

The SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.2

Please download and try things out and report any issues.

• Fixed issue with setjmp/longjmp not existing on x86 32-bit build

• Fixed python support on GDB:
NOTE: Since python support is enabled in GDB the host system needs
python3.6 installed. Otherwise you might get an error like:

arm-zephyr-eabi-gdb: error while loading shared libraries: libpython3.6m.so.1.0: cannot open shared object file: No such file or directory

On newer fedora systems this can show up and be fixed by:

sudo dnf install python36

• Added support for Intel BDW and BDW Audio DSP xtensa toolchains.

• Added support for NXP IMX8 and IMX8M Audio DSP xtensa toolchains.

• Updated xtensa targets to GDB 8.3.1 (except S1000)

Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k


West 0.7.1 released

Bolivar, Marti
 

Hi,

Hot on the heels of west 0.7.0, we've released 0.7.1. This includes a
workaround for an issue reported with the "west build" Zephyr extension
command on Windows [1] [2].

You can install it in the usual ways:

pip3 install west==0.7.1 # macOS, Windows
pip3 install --user west==0.7.1 # Linux

Thanks,
Marti

[1] https://github.com/zephyrproject-rtos/west/pull/375
https://github.com/zephyrproject-rtos/west/issues/374
[2] Windows users can also apply this Zephyr PR:
https://github.com/zephyrproject-rtos/zephyr/pull/22688/


Zephyr 2.2.0-rc1 has been tagged

Johan Hedberg
 

Hi Zephyr developers,

The the first Zephyr 2.2 release candidate (v2.2.0-rc1) has been tagged.

All required features scheduled for the 2.2 release are now merged into master. As of now we are in the stabilization phase for the 2.2 release; the merge window is closed for new features and enhancements, and will remain closed until the release date. We will also start working on filling in the existing skeleton for the release notes.

During the stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for the 2.2 release will require approval by TSC.

As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers.

Testing Zephyr master branch during the stabilisation phase is also requested; please, test the code base and file bug reports so they can be addressed before the release deadline.

The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.2.0-rc1

More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

The final release is tentatively scheduled for February 28th.

Thank you to everybody who contributed to this release!

Johan


West 0.7.0 released, requires manual intervention on Ubuntu

Bolivar, Marti
 

Hello,

West 0.7.0 has been released. The main new feature since 0.6.x is the
addition of "manifest imports", which let you pull in west.yml files
from elsewhere into your own manifest file.

You can upgrade in the usual ways:

pip3 install west==0.7.0 # Windows and macOS
pip3 install --user west==0.7.0 # Linux

Please note that there is a problem with the upgrade on the version of
pip3 which ships with Ubuntu 18.04. Other Linux distributions, macOS,
and Windows are all upgrading successfully.

On Ubuntu only, you will need to choose from one of the following
workarounds to upgrade west:

1. Remove the old west before upgrading, like this:

$ pip3 show west | grep Location: | cut -f 2 -d ' '
/home/foo/.local/lib/python3.6/site-packages
$ rm -r /home/foo/.local/lib/python3.6/site-packages/west
$ pip3 install --user west==0.7.0

2. Install west in a virtual environment using a more recent
version of pip3, e.g. using the venv module:

https://docs.python.org/3/library/venv.html

Further details in this issue:

https://github.com/zephyrproject-rtos/west/issues/373

And in particular, this comment:

https://github.com/zephyrproject-rtos/west/issues/373#issuecomment-583489272

Thanks,
Marti


The topic-gpio branch has been merged to master

Carles Cufi
 

Hi all,

As of this morning the 313 commits in the topic-gpio branch have been merged into Zephyr's master branch.

What this means for you if:

a) You are a GPIO API user:

- Big chunks of the existing API have been deprecated, leading to deprecation build warnings. You should port your application to the new GPIO API as soon as possible, although you have 2 full Zephyr releases until the deprecated API is finally removed. Please refer to Peter Bigot's "porting guide" in this GitHub comment for additional information:
https://github.com/zephyrproject-rtos/zephyr/issues/20017#issuecomment-549315497

b) You have outstanding, unmerged Pull Requests:

- The Pull Requests may show green CI, but that is misleading. We encourage you to rebase your Pull Request as soon as possible against the current master and push.

- If your Pull Request makes use of the GPIO API, it will not pass CI due to deprecation warnings. There is no solution but to port your code to the new GPIO API. If you are on a deadline for 2.2 feature freeze ping us on the #gpio channel on Slack to see if we can help.

c) You are a maintainer with merge rights:

- You need to make sure that CI has been rerun after the topic-gpio merge happened and *before* you merge any Pull Request to master

Additional information about the merge process can be found here:

https://github.com/zephyrproject-rtos/zephyr/issues/21789

Finally I want to thank everybody who contributed to this effort, which has spanned many months and several hundred commits.
Special mention to Piotr Mienkowski and Peter Bigot, whose dedication to getting this done has made it possible to merge this branch in time for the 2.2 release.

Regards,

Carles


Re: [Zephyr-users] SDK 0.11.1 Release

Nashif, Anas
 

Hi,
Thanks Kumar.

Please note that this version of the SDK is now required for development on master and is enabled in CI.


Anas

On 03/02/2020, 05:56, "users@lists.zephyrproject.org on behalf of Kumar Gala" <users@lists.zephyrproject.org on behalf of kumar.gala@linaro.org> wrote:

Hi,

Some minor fixes that got missed for the v0.11.0 release. Mostly impacts OpenOCD and newlib usage.

The SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.1

Please download and try things out and report any issues.

OpenOCD:

• Fixed missing commits from rebase - related to ARC and Zephyr RTOS awareness

Newlib:

• Removed setting -DMISSING_SYSCALL_NAMES on builds. Make syscall function names consistent and naming compatible with 3rd party GNU toolchains.

Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k

21 - 40 of 123