nRF Matter development releases track against original chip repo

[stlevkov]

Hi,
I'm developing Matter Controller using the Chip-Tool as example from the original chip repo: https://github.com/project-chip/connectedhomeip

I am not using releases/branches, but using concrete checkouts periodically of the master branch.

For my developing branch, i am using the latest commit ID from the master branch.

My Controller works well and i am using the chip-all-clusters-app for testing the cluster implementations.

Recently i wanted to test the pairing/commissioning of thread devices, for which, i took nRF 52840 DK, as well as dongle to build OpenThread border router setup.

I followed the YouTube tutorial, which is build on top of v1.7.0 version of nRF Connect SDK. The ble-thread test was successfull using the python chip-tool.

Since, this is old version of the stack, i tried the latest v2.0.2 which is from July. The ble-thread test was successfull using the linux chip-tool.

The problem is that, when i try to use my Controller sample, the pairing fails, which is reasonable, because it is not aligned against the nRF repo version.

Question:

What is the commit sha (commit ID) used for the nRF sdk-connectedhomeip repo, against the project-chip repo,

for example, which commit ID from the original repo is used to checkout the v2.0.2 branch on the nRF side?

Thanks in advance

[Elfving]

Hello Stoycho,

I will have to get back to you on this.

Regards,

Elfving

[Elfving]

Hello,

We post the reference commit SHA of the origin repo in every NCS release note that changed something for the Matter protocol. Here you can see the example for NCS 2.0.0. For NCS 2.0.1 and NCS 2.0.2 there wasn't record for Matter protocol in the release notes, as we didn't change the version.

Regards,

Elfving

[stlevkov]

Thanks,

somehow i missed it.

One more question regarding this:
Currently, there is a new development tag for a unreleased version - 2.1.0 which is on stage release candidate. Can you post the commit sha for this tag, or it is unchanged for the 2.X.X major versions?

My goal is to have my Controller ready with the new changes from the chip repo aligned with NCS version, before the 2.1.0 NCS release.

Best Regards,
Stoycho

[Elfving]

stlevkov said:

Currently, there is a new development tag for a unreleased version - 2.1.0 which is on stage release candidate. Can you post the commit sha for this tag, or it is unchanged for the 2.X.X major versions?

As you can see here in the documentation for the 2.1.0 RC, it will be changed to 708685f4821df2aa0304f02db2773c429ad25eb8.

Regards,

Elfving