Feedback

Exercise 1 – Enabling Matter ICD and measuring its power consumption

The nRF Connect SDK provides multiple Matter samples that are power-optimized and use Matter ICDs by default. However, in this exercise you will use the Matter Template sample from the nRF Connect SDK as a starting point. That sample is not power-optimized and does not use Matter ICD by default. Your goal will be to optimize it, test various ICD configurations and measure the device’s power consumption using Nordic Power Profiler Kit II (PPK II).

To see the full list of power-optimized Matter samples and applications see the following Reducing power consumption in Matter documentation.

Important

This exercise requires the Nordic Power Profiler Kit II (PPK2) to complete some of the steps. If you don’t have the PPK2, you can still go through the exercise, but you won’t be able to perform the power consumption measurement steps.

Exercise steps

1. Get the base code for this exercise.

In Visual Studio Code, in the WELCOME panel, select Open an existing application, navigate to the GitHub repository for the course and open the l4/l4_e1 directory. The application should appear under the APPLICATIONS panel.

This application is a copy of the Matter Template sample, with added instructions for where to input the code snippets from this exercise.

2. Enable ICD SIT using the ZAP Tool.

2.1 In Visual Studio Code, in the APPLICATIONS panel, right click on the application and select “Start New Terminal”, select the nRF Connect SDK version and corresponding toolchain version. This will open a terminal in your sample directory.

Run the ZAP Tool using the following command:

west zap-gui

Copy

west zap-gui

Terminal command

2.2 Click on the Endpoint 0 listed in the side panel on the left side of the window.

2.3 In the search field, type in ICD to find the ICD Management cluster. Once found enable the Server role, using the check box.

2.4 Click on the gear icon to see the ICD Management details, and make sure the mandatory attributes presented in the following picture are enabled:

2.5 Save the configuration by clicking File->Save on the top bar and exit the application.

2.6 Generate the code based on the .zap file by invoking the following command in the VS Code terminal:

west zap-generate

Copy

west zap-generate

Terminal command

3. Enable ICD SIT and power-optimizations in the application

All the required modifications in this step will be done in the prj_release.conf file. That is the variant of a typical sample’s prj.conf file that has debug features and logs disabled to reduce the power consumption.

3.1 Disable LEDs and watchdog to reduce the power consumption.

Add the following configurations to the prj_release.conf file:

CONFIG_NCS_SAMPLE_MATTER_LEDS=n
CONFIG_NCS_SAMPLE_MATTER_WATCHDOG=n

Copy

CONFIG_NCS_SAMPLE_MATTER_LEDS=n
CONFIG_NCS_SAMPLE_MATTER_WATCHDOG=n

Kconfig

3.2 Enable RAM Power Down library to disable unused RAM blocks and reduce the power consumption.

Add the following configurations to the prj_release.conf file:

CONFIG_RAM_POWER_DOWN_LIBRARY=y

Copy

CONFIG_RAM_POWER_DOWN_LIBRARY=y

Kconfig

3.3 Reduce the default TX power of the radio transceiver from 8 dBm to 0 dBm, by adding the following configuration to the prj_release.conf file:

CONFIG_OPENTHREAD_DEFAULT_TX_POWER=0

Copy

CONFIG_OPENTHREAD_DEFAULT_TX_POWER=0

Kconfig

3.4 Enable ICD support, by adding the following configuration to the prj_release.conf file:

CONFIG_CHIP_ENABLE_ICD_SUPPORT=y

Copy

CONFIG_CHIP_ENABLE_ICD_SUPPORT=y

Kconfig

3.5 Configure device to be minimal thread device, by adding the following lines to the prj_release.conf file:

CONFIG_OPENTHREAD_MTD=y
CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y

Copy

CONFIG_OPENTHREAD_MTD=y
CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y

Kconfig

The required configuration of the OpenThread device role is MTD. This is configured by setting the CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y and CONFIG_OPENTHREAD_MTD=y Kconfigs in the prj_release.conf file.

3.6 Change the default configuration of the ICD parameters.

By default the ICD SIT uses the following values:

Slow Polling Interval – 2.5 s
Fast Polling Interval – 500 ms
Idle Mode Duration – 120 s
Active Mode Duration – 300 ms
Active Mode Threshold – 0 s

Change the configuration, by setting the Slow Polling Interval to 1 s, Fast Polling Interval to 200 ms and Idle Mode Duration to 30 s. Add the following configuration to the prj_release.conf file:

CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=1000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=200
CONFIG_CHIP_ICD_IDLE_MODE_DURATION=30

Copy

CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=1000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=200
CONFIG_CHIP_ICD_IDLE_MODE_DURATION=30

Kconfig

4. Build and flash the application to your DK

Add a build configuration and select your board target as usual.

Then under Extra CMake arguments, click Add Argument and add the following line to use prj_release.conf instead of the default prj.conf

-DFILE_SUFFIX=release

5. Set up Thread Border Router

Matter over Thread
Matter over Wi-FI

5.1 Ensure the Thread Border Router is still running. If not:

5.1.1 Open a new command-line terminal and run the following command to run the OpenThread Border Router:

Replace the /dev/ttyACM0 with the serial port number that is used by your Thread Coprocessor.

sudo docker run -it --rm --privileged --name otbr --network otbr -p 8080:80 \
--sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1" \
--volume /dev/ttyACM0:/dev/radio nrfconnect/otbr:fbde28a --radio-url spinel+hdlc+uart:///dev/radio?uart-baudrate=1000000

Copy

sudo docker run -it --rm --privileged --name otbr --network otbr -p 8080:80 \
--sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1" \
--volume /dev/ttyACM0:/dev/radio nrfconnect/otbr:fbde28a --radio-url spinel+hdlc+uart:///dev/radio?uart-baudrate=1000000

Terminal command

Important

If you get an error like “The container name “/otbr” is already in use by container…, run the following commands

- sudo docker kill otbr

- sudo ip -6 route del "fd11:22::/64" dev otbr0 via "fd11:db8:1::2"

- sudo ip link set dev otbr0 down

- sudo docker network rm otbr

5.1.2 Open the http://localhost:8080/ address in a web browser to get access to the OpenThread Border Router graphical user interface.

5.1.3 Navigate to the Form tab from the side panel and make sure that all the inserted data is the same as in the following picture. Then press the FORM button to request from the OpenThread Border Router to form a Thread network and become a Thread leader.

5.1.4 Open a new command-line terminal and check the status of the Thread node running inside the Docker:

sudo docker exec -it otbr sh -c "sudo ot-ctl state"

Copy

sudo docker exec -it otbr sh -c "sudo ot-ctl state"

Terminal command

The output should be the following:

leader
Done

Terminal

Proceed to step 6.

6. Create power consumption measurement setup using the PPK II.

6.1 Connect the Power Profiler Kit II to the computer using a micro-USB cable using the USB DATA/POWER port on the device.

6.2 Connect the pins of the Power Profiler Kit II to the VDD nRF CURRENT MEASURE set of pins on the DK:

Connect the GND pin to the GND pin of the set on the DK.
Connect the VOUT pin to the middle pin of the set. The pin is marked with ↓ on the DK.
Connect the VIN pin to the leftmost pin of the set. The pin is marked with ↑ on the DK.

6.3 Open nRF Connect for Desktop and launch the Power Profiler application.

6.4 Select the PPK2 in the drop-down menu under Select Device.

6.5 Select source meter mode, set the supply voltage to 3000 mV, and enable power output.

6.6 Click the Start button to start the measurements.

7. Measure the power consumption after joining the Matter fabric

Matter over Thread
Matter over Wi-FI

Ensure CHIP Tool is still running. If not:

7.1 Open a new command-line terminal and run the downloaded binary file you obtained in the previous exercise using the following command:

With PC:

./chip-tool_x64 interactive start

With Raspberry Pi:

./chip-tool_arm64 interactive start

7.2 Commission the device to the network.

7.2.1 Make sure that Matter advertising over Bluetooth LE is running.

The following logs should be visible in the device serial port:

I: 730208 [DL]CHIPoBLE advertising started
I: 730212 [DL]NFC Tag emulation started

Terminal

Note that the Matter advertising over Bluetooth LE is automatically started for the Matter Template sample, but it timeouts after 1 hour. If the advertising timed out, press BUTTON0 on the Matter device to start it again.

7.2.2 Return to the terminal window running the CHIP Tool application.

Start the commissioning process by running the following command and fill the <thread dataset> argument with your Thread dataset that was obtained in Lesson 2 Exercise 1 and stored on your computer. Replace <your_selected_node_id> with a random node ID that has not been used in other exercises, e.g 5. This same number will be used when sending commands to the device via CHIP Tool.

pairing ble-thread <your_selected_node_id> hex:<thread dataset> 20202021 3840

Copy

pairing ble-thread <your_selected_node_id> hex:<thread dataset> 20202021 3840

Terminal command

Ensure CHIP Tool is still running. If not:

7.1 Open a new command line terminal and run the downloaded binary file obtained in the previous exercise using the following command:

With PC:

./chip-tool_x64 interactive start

With Raspberry Pi:

./chip-tool_arm64 interactive start

7.2 Commission the device to the network.

7.2.1 Press BUTTON0 on the Matter device to start Matter advertising over Bluetooth LE.

The following logs should be visible in the device serial port:

I: 730208 [DL]CHIPoBLE advertising started
I: 730212 [DL]NFC Tag emulation started

Terminal

7.2.2 Return to the terminal window running the CHIP Tool application.

Run the following command and fill the <wifi_ssid> and <wifi_password> arguments with your Wi-Fi network data.

Replace <your_selected_node_id> with a random node ID that has not been used in other exercises, e.g 5. This same number will be used when sending commands to the device via CHIP Tool.

pairing ble-wifi <your_selected_node_id> <wifi_ssid> <wifi_password> 20202021 3840

Copy

pairing ble-wifi <your_selected_node_id> <wifi_ssid> <wifi_password> 20202021 3840

Terminal command

In the Power Profiler application’s window the commissioning process should be visible and similar to what is presented in the following image:

7.3 Measure the power consumed during a single Slow Polling period.

7.3.1 Get measurement values using markers in Power Profiler tool.

Wait some time after the commissioning ends for the power consumption chart to stabilize. Stop the capture and use markers to measure the time between two regular current peaks. The time between them should be equal to 1 s, as configured in step 3.4.

The sleep current between the current peaks is expected to be around 2.37 uA and the charge consumed during the single polling period is expected to be around 12 uC, what was presented in the following picture:

7.3.2 Go to the Online Power Profiler for Matter over Thread to confirm that the measured value is expected.

7.3.3 Configure the Matter ICD settings in a way consistent with the values used in step 3.4, as presented in the following picture:

7.3.4 Hover with your mouse’s cursor on the Data Poll in a displayed chart to read the charge of it, as presented in the following picture:

7.3.5 Hover with your mouse’s cursor on the Sleep area in a displayed chart to read the charge of it, as presented in the following picture:

7.3.6 Sum the two values read in steps 7.3.5 and 7.3.4. The summarized consumed charge during a single poll period is around 12.2 uC, which is a very close value to the 11.93 uC measured using Power Profiler tool.

7.4 Subscribe to the NodeLabel attribute from the BasicInformation cluster to trigger sending regular Matter data reports.

7.4.1 Open the terminal window running the CHIP Tool application

7.4.2 Learn the command usage, by invoking the following commands:

basicinformation subscribe

Copy

basicinformation subscribe

Terminal command

and

basicinformation subscribe node-label

Copy

basicinformation subscribe node-label

Terminal command

7.4.2 Subscribe to the NodeLabel attribute value, by invoking the following command:

basicinformation subscribe node-label 0 30 <your_selected_node_id> 0

Copy

basicinformation subscribe node-label 0 30 <your_selected_node_id> 0

Terminal command

The selected max-interval value is equal to 30 seconds, as was configured in step 3.4

7.5 Measure the power consumed during a single Idle Mode Duration period.

7.5.1 Get measurement values using markers in Power Profiler tool.

Wait more than 30 s to capture at least two Matter data reports. Stop the capture and use markers to measure the time between two wider current peaks, visible among smaller ones that are Thread data pools. The time between them should be equal to 30 s, as configured in step 3.4.

The charge consumed during the single subscription period is expected to be around 450 uC, what was presented in the following picture:

7.5.2 In the Online Power Profiler for Matter over Thread configure the Operating Time to be equal to 30 s:

7.5.3 Read the Total consumption over time listed in the General section. The value is equal to 459.5 uCwhich is a very close value to the 450 uC measured using Power Profiler tool.

8. Enable ICD LIT using the ZAP Tool

8.1 In Visual Studio Code, in the WELCOME panel, select “Open terminal”. This should open a terminal in your sample directory. If not, navigate to your sample directory before proceeding.

Run the ZAP Tool using the following command:

west zap-gui

Copy

west zap-gui

Terminal command

8.2 Click on the Endpoint 0 listed in the side panel on the left side of the window.

8.3 In the search field type in ICD to find ICD Management cluster. Once found, click on the gear icon to see the ICD Management details.

8.4 In the Features tab enable the CIP, UAT and LITS features that are mandatory for the ICD LIT device type, as presented in the following picture:

8.5 Make sure that all required commands are enabled, as presented in the following picture:

8.6 Make sure that all required attributes are enabled, as presented in the following picture:

8.7 Save the configuration by clicking File->Save on the top bar and exit the application.

8.8 Generate the code based on the .zap file by invoking the following command in the VS Code terminal:

west zap-generate

Copy

west zap-generate

Terminal command

9. Enable ICD LIT in the application

All the required modifications in this point will be applicable to the prj_release.conf file.

9.1 Enable ICD LIT support, by adding the following configuration to the prj_release.conf file:

CONFIG_CHIP_ICD_LIT_SUPPORT=y
CONFIG_CHIP_ICD_REPORT_ON_ACTIVE_MODE=y

Copy

CONFIG_CHIP_ICD_LIT_SUPPORT=y
CONFIG_CHIP_ICD_REPORT_ON_ACTIVE_MODE=y

Kconfig

9.2 Change the default configuration of ICD parameters. By default the ICD LIT uses the following values:

Slow Polling Interval – 300 s
Fast Polling Interval – 500 ms
Idle Mode Duration – 300 s
Active Mode Duration – 300 ms
Active Mode Threshold – 5 s

To learn how to change the configuration, let’s set the Slow Polling Interval to 60 s, Fast Polling Interval to 500 ms, Idle Mode Duration to 60 s and Active Mode Threshold to 5 s.

Comment out the lines added in step 3.5, and add the following lines in the prj_release.conf file:

CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=60000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=500
CONFIG_CHIP_ICD_IDLE_MODE_DURATION=60
CONFIG_CHIP_ICD_ACTIVE_MODE_THRESHOLD=5000

Copy

CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=60000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=500
CONFIG_CHIP_ICD_IDLE_MODE_DURATION=60
CONFIG_CHIP_ICD_ACTIVE_MODE_THRESHOLD=5000

Kconfig

10. Build and flash the application to your DK.

Add a build configuration and select your board target as usual.

Then under Extra CMake arguments, click Add Argument and add the following line to use prj_release.conf instead of the default prj.conf

-DFILE_SUFFIX=release

11. Measure the power consumption after joining the Matter fabric.

Matter over Thread
Matter over Wi-FI

Ensure CHIP Tool is still running. If not:

11.1 Open a new command-line terminal and run the downloaded binary file you obtained in the previous exercise using the following command:

With PC:

./chip-tool_x64 interactive start

With Raspberry Pi:

./chip-tool_arm64 interactive start

11.2 Commission the device to the network.

11.2.1 Make sure that Matter advertising over Bluetooth LE is running.

The following logs should be visible in the device serial port:

I: 730208 [DL]CHIPoBLE advertising started
I: 730212 [DL]NFC Tag emulation started

Terminal

11.2.2 Return to the terminal window running the CHIP Tool application.

Start the commissioning process by running the following command and fill the <thread dataset> argument with your Thread dataset that was obtained in Lesson 2 Exercise 1 and stored on your computer. Replace <your_selected_node_id> with a random node ID that has not been used in other exercises, e.g 6. This same number will be used when sending commands to the device via CHIP Tool.

pairing ble-thread <your_selected_node_id> hex:<thread dataset> 20202021 3840 --icd-registration true

Copy

pairing ble-thread <your_selected_node_id> hex:<thread dataset> 20202021 3840 --icd-registration true

Terminal command

Note that the command is different than it was in the previous steps and exercises, as it includes an additional icd-registration true flag. This makes the CHIP Tool automatically register as an ICD client of the nRF Matter device that is required for testing ICD LIT.

Ensure CHIP Tool is still running. If not:

11.1 Open a new command line terminal and run the downloaded binary file obtained in the previous exercise using the following command:

With PC:

./chip-tool_x64 interactive start

With Raspberry Pi:

./chip-tool_arm64 interactive start

11.2 Commission the device to the network.

11.2.1 Press BUTTON0 on the Matter device to start Matter advertising over Bluetooth LE.

The following logs should be visible in the device serial port:

I: 730208 [DL]CHIPoBLE advertising started
I: 730212 [DL]NFC Tag emulation started

Terminal

11.2.2 Return to the terminal window running the CHIP Tool application.

Run the following command and fill the <wifi_ssid> and <wifi_password> arguments with your Wi-Fi network data.

Replace <your_selected_node_id> with a random node ID that has not been used in other exercises, e.g 6. This same number will be used when sending commands to the device via CHIP Tool.

pairing ble-wifi <your_selected_node_id> <wifi_ssid> <wifi_password> 20202021 3840 --icd-registration true

Copy

pairing ble-wifi <your_selected_node_id> <wifi_ssid> <wifi_password> 20202021 3840 --icd-registration true

Terminal command

11.2.3 Subscribe to the NodeLabel attribute value, by invoking the following command:

basicinformation subscribe node-label 0 60 <your_selected_node_id> 0

Copy

basicinformation subscribe node-label 0 60 <your_selected_node_id> 0

Terminal command

The selected max-interval value is equal to 60 seconds, as was configured in step 9.2

11.3 Measure the power consumed during a single Idle Mode Duration period.

11.3.1 Get measurement values using markers in Power Profiler tool.

Wait more than 60 s after commissioning is completed to capture at least two Matter data reports. Stop the capture and use markers to measure the time between two group of current peaks. The time between them should be equal to 60 s, as it was configured in the step 9.2.

The charge consumed during the single subscription period is expected to be around 350 uC, what was presented in the following picture:

Note that there is a group of current peaks visible while sending a Matter data report, not a single peak, as it was for ICD SIT. This is a result of using a non-zero Active Mode Threshold value. The Matter device keeps using Fast Polling for 5 s after sending the Matter data report, which is visible as a group of several short current peaks.

11.3.2 In the Online Power Profiler for Matter over Thread configure the Matter ICD settings in a way consistent with the values used in step 9.2, as presented in the following picture:

11.3.3 In the Online Power Profiler for Matter over Thread configure the Operating Time to be equal to 70 s.

11.3.4 Read the Total consumption over time listed in the General section. The value is equal to 380.8 uC which is a close value to the 346 uC measured using Power Profiler tool.

Nordic Developer Academy Terms of Service

1. Introduction

‍These terms and conditions (“Terms of Use”) apply to the use of the Nordic Developer Academy, provided by Nordic Semiconductor ASA, org. nr. 966 011 726, a public limited liability company registered in Norway (“Nordic Semiconductor”). ‍

Nordic Developer Academy allows the user to take technical courses related to Nordic Semiconductor products, software and services, and obtain a certificate certifying completion of these courses. By completing the registration process for the Nordic Developer Academy, you are agreeing to be bound by these Terms of Use.

These Terms of Use are applicable as long as you have a user account giving you access to Nordic Developer Academy.‍

‍2. Access to and use of Nordic Developer Academy

‍‍Upon acceptance of these Terms of Use you are granted a non-exclusive right of access to, and use of Nordic Developer Academy, as it is provided to you at any time. Nordic Semiconductor provides Nordic Developer Academy to you free of charge, subject to the provisions of these Terms of Use and the Nordic Developer Academy Privacy Policy.

To access select features of Nordic Developer Academy, you need to create a user account. You are solely responsible for the security associated with your user account, including always keeping your login details safe.

You will able to receive an electronic certificate from Nordic Developer Academy upon completion of courses. By issuing you such a certificate, Nordic Semiconductor certifies that you have completed the applicable course, but does not provide any further warrants or endorsements for any particular skills or professional qualifications.

Nordic Semiconductor will continuously develop Nordic Developer Academy with new features and functionality, but reserves the right to remove or alter any existing functions without notice.

‍3. Acceptable use

You undertake that you will use Nordic Developer Academy in accordance with applicable law and regulations, and in accordance with these Terms of Use.‍ You must not modify, adapt, or hack Nordic Developer Academy or modify another website so as to falsely imply that it is associated with Nordic Developer Academy, Nordic Semiconductor, or any other Nordic Semiconductor product, software or service.

You agree not to reproduce, duplicate, copy, sell, resell or in any other way exploit any portion of Nordic Developer Academy, use of Nordic Developer Academy, or access to Nordic Developer Academy without the express written permission by Nordic Semiconductor. You must not upload, post, host, or transmit unsolicited email, SMS, or \”spam\” messages.

You are responsible for ensuring that the information you post and the content you share does not;

contain false, misleading or otherwise erroneous information
infringe someone else’s copyrights or other intellectual property rights
contain sensitive personal data or
contain information that might be received as offensive or insulting.
Such information may be removed without prior notice.

‍Nordic Semiconductor reserves the right to at any time determine whether a use of Nordic Developer Academy is in violation of its requirements for acceptable use.

Violation of the at any time applicable requirements for acceptable use may result in termination of your account. We will take reasonable steps to notify you and state the reason for termination in such cases.

‍4. Routines for planned maintenance

‍Certain types of maintenance may imply a stop or reduction in availability of Nordic Developer Academy. Nordic Semiconductor does not warrant any level of service availability but will provide its best effort to limit the impact of any planned maintenance on the availability of Nordic Developer Academy.

5. Intellectual property rights

‍Nordic Semiconductor retains all rights to all elements of Nordic Developer Academy. This includes, but is not limited to, the concept, design, trademarks, know-how, trade secrets, copyrights and all other intellectual property rights.

Nordic Semiconductor receives all rights to all content uploaded or created in Nordic Developer Academy. You do not receive any license or usage rights to Nordic Developer Academy beyond what is explicitly stated in this Agreement.

‍6. Liability and damages

‍Nothing within these Terms of Use is intended to limit your statutory data privacy rights as a data subject, as described in the Nordic Developer Academy Privacy Policy. ‍You acknowledge that errors might occur from time to time and waive any right to claim for compensation as a result of errors in Nordic Developer Academy. When an error occurs, you shall notify Nordic Semiconductor of the error and provide a description of the error situation.

You agree to indemnify Nordic Semiconductor for any loss, including indirect loss, arising out of or in connection with your use of Nordic Developer Academy or violations of these Terms of Use. ‍Nordic Semiconductor shall not be held liable for, and does not warrant that (i) Nordic Developer Academy will meet your specific requirements, (ii) Nordic Developer Academy will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of Nordic Developer Academy will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through Nordic Developer Academy will meet your expectations, or that (v) any errors in Nordic Developer Academy will be corrected.

You accept that this is a service provided to you without any payment and hence you accept that Nordic Semiconductor will not be held responsible, or liable, for any breaches of these Terms of Use or any loss connected to your use of Nordic Developer Academy. Unless otherwise follows from mandatory law, Nordic Semiconductor will not accept any such responsibility or liability.

‍7. Change of terms

‍Nordic Semiconductor may update and change the Terms of Use from time to time. Nordic Semiconductor will seek to notify you about significant changes before such changes come into force and give you a possibility to evaluate the effects of proposed changes. Continued use of Nordic Developer Academy after any such changes shall constitute your acceptance of such changes. You can review the current version of the Terms of Use at any time at https://academy.nordicsemi.com/terms-of-service/

‍8. Transfer of rights

‍Nordic Semiconductor is entitled to transfer its rights and obligation pursuant to these Terms of Use to a third party as part of a merger or acquisition process, or as a result of other organizational changes.

‍9. Third Party Services

‍‍To the extent Nordic Developer Academy facilitates access to services provided by a third party, you agree to comply with the terms governing such third party services. Nordic Semiconductor shall not be held liable for any errors, omissions, inaccuracies, etc. related to such third party services.

‍10. Dispute resolution

‍‍The Terms of Use and any other legally binding agreement between yourself and Nordic Semiconductor shall be subject to Norwegian law and Norwegian courts’ exclusive jurisdiction.

Matter Fundamentals

Exercise 1 – Enabling Matter ICD and measuring its power consumption

Important

Exercise steps

Important

Switch language?

Change summary

What's new in the latest version

Matter

MCUboot & Partition Manager