Keeping zephyr up-to-date

Development Platforms
1

I’ve noticed that zephyr seems to be out-of-date. The current pio is 2.5.0 and 2.6.0 is the current zephyr. What’s involved in getting the pio version updated? Is it feasible to avoid having to keep them separate and get the pio package.json and scripts into the main zephyr repo or are there more changes needed?

2

Depending on the PIO priorities, I suspect the PlatformIO Zephyr update to 2.6.0 will happen by the end of this month. I think the last time, it was a few weeks after the Zephyr 2.5.0 release.

3

@valeros,
Any chance for the Zephyr 2.6.0 update by the end of this month.

4

Any chance updating Zephyr to v2.6.0? Thanks!

5

Issue is formally open at Update Zephyr to 2.6.0 · Issue #541 · platformio/platform-ststm32 · GitHub but no change these days.

6

PlatformIO has been updated to support Zephyr 2.6.0.

Use pio platform update to update all platforms

or pio platform update [platform], e.g. pio platform update nordicnrf52.

7

You may get some warnings as some Macros have been deprecated in Zephyr 2.6.0, e.g. DT_PWMS_LABEL in favor of DT_PWMS_CTLR.

Refer to the Zephyr 2.6.0 Release Notes.