Nordic Connect SDK v.1.5.0 / still Zephyr 2.4.99???

[krbvroc1]

I was using Nordic Connect SDK v1.4.0, but put development on hold for a few weeks waiting for v.1.5.0. In particular I was waiting for openthread to be updated (which requires Zephyr to be updated).

I was excited to see a Nordic Connect SDK v1.5.0 be released a few days ago. But after fetching, it still uses the older v2.4.99 version of Zephyr. How long must I wait until Zephyr is updated to 2.5.x branch? 2.5.0 was released 2 weeks ago.

What is the release cadence on this stuff? It makes planning very difficult... I cannot even tell if v2.5.99 includes the openthread changes yet.

[Didrik Rokhaug]

Hi,

In general, the NCS releases aren't necessarily tied to Zephyr's releases.

In this case, the Zephyr 2.5.0 release got delayed, which meant that it came after the NCS 1.5.0 code freeze.

 

How long must I wait until Zephyr is updated to 2.5.x branch?

 As it has been released, I would expect it to be included in NCS the next time the sdk-zephyr repo is synchronized with the upstream repo.

 

What is the release cadence on this stuff? It makes planning very difficult...

 There is generally a minor (e.g. 1.x.0) release every 3 months. In addition, there might be patch releases in between if necessary. These will often be due to certifications. E.g. 1.4.1 had a qualified BLE stack and some LTE carrier certifications.

 

I cannot even tell if v2.5.99 includes the openthread changes yet.

 Which changes are you waiting for?

You can find the NCS release notes here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/releases/release-notes-1.5.0.html

And Zephyr's release notes here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/zephyr/releases/release-notes-2.5.html (Zephyr 2.4.99, included in NCS 1.5.0)

https://docs.zephyrproject.org/latest/releases/release-notes-2.5.html (Zephyr's 2.5.0 release notes, not yet included in NCS master branch)

Or, you could ask the Zephyr community: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/introduction/index.html#community-support

Best regards,

Didrik

[krbvroc1]

Didrik Rokhaug said:

 Which changes are you waiting for?

https://github.com/openthread/openthread/pull/4247 (Jan 26) - add CoAP(s) block-wise transfer support to CoAP(s) client and server

Didrik Rokhaug said:

 As it has been released, I would expect it to be included in NCS the next time the sdk-zephyr repo is synchronized with the upstream repo.

EDIT: I think zephyr-v2.5.0-148-g4ee876b797b1 includes this code. So when would the 'next time sdk-zephyr' is synced be?

[Didrik Rokhaug]

This is the latest commit form Zephyr's openthread fork included in NCS 1.5.0: aad6518ee30d3840411b21437d396f0405e947c3

It includes everything up to commit f7825b96 in the original openthread repo.

Looking at the openthread commit history, that commit came the day before the PR you are waiting for was merged.

The PR was included in Zephyr's fork later the same day.

Zephyr 2.5.0 uses 1d668284a0b897bd6d539e7c3ed8009f0028099d, which is from February 8th.

This means that Zephyr 2.5.0 includes your PR.

 

krbvroc1 said:

So when would the 'next time sdk-zephyr' is synced be?

 I don't know for certain, but I would expect it to happen fairly quickly, as it has been a while since the last time.

[Didrik Rokhaug]

Hi,

I just wanted to let you know that we are currently in the process of syncing up with Zephyr 2.5.

You can track the progress in this PR: https://github.com/nrfconnect/sdk-zephyr/pull/479

Best regards,

Didrik