Request for Guidance on Using Nordic nRF DK IDE and Matter Development

[Adarsh_N]

Hi Team, 

I am currently working on a project involving the Nordic nRF DK IDE and the Matter protocol. As part of my learning process, I watched your YouTube video and followed the steps to install the nRF Desktop and toolchain. However, when I attempted to access the nRF Command Line Tool download page, it indicated that I should use the nRF Util. Unfortunately, I was unable to install it successfully on both my Windows and Linux systems.

Additionally, I would appreciate your guidance on using the Device Tree. I am working with the Matter sample code in Visual Studio Code and testing the On/Off Toggle cluster. I would like to modify the GPIO pins and implement additional logic and clusters as part of the development process.

Could you also advise on how to integrate the ZAP tool-generated files into my Matter sample code?

In your video, I observed three different methods of modifying the Device Tree:

1. Using the GUI view of the Device Tree,

2. Editing the Device Tree source (.dts) files directly,

3. Using API calls and bitwise operations in the source code.

I would be grateful if you could recommend the best approach among these and explain the reasoning behind it.

Thank you in advance for your support and guidance.

Best regards,
Adarsh Narayan N

[Maria Gilje]

Hello,

I am currently working on a project involving the Nordic nRF DK IDE and the Matter protocol. As part of my learning process, I watched your YouTube video and followed the steps to install the nRF Desktop and toolchain. However, when I attempted to access the nRF Command Line Tool download page, it indicated that I should use the nRF Util. Unfortunately, I was unable to install it successfully on both my Windows and Linux systems.

For recommended practices when developing Nordic products, please refer to the courses available on the Nordic Developer Academy. The recommended starting point is nRF Connect SDK Fundamentals which covers the basics of developing with nRF Connect SDK. More in-depth topics are covered in the Intermediate course. Our DevAcademy courses are updated after each release of nRF Connect SDK, so you will not get very outdated information from there. In addition, our documentation database TechDocs has step-by-step installation instructions for releases of nRF Connect SDK. The latest tagged release as I write is v3.0.1 and the launch page for the installation instructions for that release can be found here.

Specific installation instructions for nRF Util are included in the installation guide sources above and can also be found here.

I don't know what you mean with "nRF DK IDE", can you elaborate? Perhaps you can share a link to the YouTube video you saw or a documentation page.

Could you also advise on how to integrate the ZAP tool-generated files into my Matter sample code?

When using the west zap-gui command, the ZAP tool genereated files will be saved to the project directory. If your project is out-of-tree, make sure to call west zap-gui from a directory with the correct environment (i.e. a west workspace with the same nRF Connect SDK version as your project). It is important that the nRF Connect SDK version is compatible with the ZAP tool version. More details are found in the Matter tools documentation, especially the ZAP tool and Matter west commands sections.

In your video, I observed three different methods of modifying the Device Tree:

1. Using the GUI view of the Device Tree,

2. Editing the Device Tree source (.dts) files directly,

3. Using API calls and bitwise operations in the source code.

I would be grateful if you could recommend the best approach among these and explain the reasoning behind it.

We provide different options of editing the device tree to cater to different preferences. It is up to you as the user which method you want to use. I am not familiar with method 3, so I don't have any details on this now. Let me know if you need it and I'll do some research. Regarding method 1 and 2, both edits the .dts files, but with method 1 the GUI handles the syntax for you. The two methods are in other words equivalent, and you as the user can choose which way you prefer.

Best regards,

Maria