-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snippets: Added snippet for Matter power consumption measurements #20072
base: main
Are you sure you want to change the base?
Conversation
0a266fa
to
f697e7b
Compare
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: b1fd34539090a3b3aa65fe6bf0f20b1ff90a74e3 more detailssdk-nrf:
Github labels
List of changed files detected by CI (9)
Outputs:ToolchainVersion: 342151af73 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
f697e7b
to
ac42c61
Compare
# Disable LEDs that lead to the current leakages | ||
CONFIG_NCS_SAMPLE_MATTER_LEDS=n | ||
|
||
# Disable watchdog that increases the sleep current | ||
CONFIG_NCS_SAMPLE_MATTER_WATCHDOG=n | ||
|
||
# Increase MPSL calibration period to prevent too often CPU wake-ups. | ||
CONFIG_MPSL_CALIBRATION_PERIOD=60000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why does this need a specific kconfig fragment for the board, why can't it go in the normal snippet .conf?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because, the nRF54L15 needs few additional tweaks to lower power consumption. On other platforms this is not required (this particular Kconfig option is even not used).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so disabling it isn't a problem then, that way there is a snippet that works for all boards including customer boards, whereas right now this works for no nrf54l* customer boards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not targeted for the customers use, and we also do not mention how to use it in the documentation. This is added for the QA to avoid handling multiple configurations in their Test Automation System.
This works on all boards, but we don't want to use it with all boards, because this is not required. Only nRF54L15 DK (not SoC) has problems with LEDs current leakage, so I don't see a reason to disable it for other/customer boards as well. Similarly, we configure nrf dks in samples' boards directory and this does not apply to the customers' boards, so I think we are not doing anything different here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to be clear, as maybe I haven't put it explicitly. Disabling this modules is not something we would like to do, ideally we would like to keep it enabled. Unfortunately, the nRF54L15 DK requires this sort of "workaround", so we don't want to put workaround, where it is not required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can find the documentation preview for this PR at this link. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
ac42c61
to
6b4c40f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you should add the new snippet to codeowners and assign the ncs-matter to it.
6b4c40f
to
d233134
Compare
@kkasperczyk-no, forgot to mention, can you look at the integration_quarantine.yaml in the scripts dir? |
Matter requires some extra configuration for the power consumption measurements that are automatized. This change introduces snippet that simplifies it and adds dedicated variant in the sample.ymls. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no>
d233134
to
b1fd345
Compare
@doublemis1 done, please re-check |
nrf54l15dk/nrf54l15/cpuapp: | ||
append: | ||
EXTRA_CONF_FILE: boards/nrf54l15dk_nrf54l15_cpuapp.conf | ||
nrf54l15dk/nrf54l10/cpuapp: | ||
append: | ||
EXTRA_CONF_FILE: boards/nrf54l15dk_nrf54l10_cpuapp.conf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, we can merge those two to all DKs dedicated for nRF54L15 and don't have the additional nrf54l15dk_nrf54l10_cpuapp.conf
file to maintain:
nrf54l15dk/nrf54l15/cpuapp: | |
append: | |
EXTRA_CONF_FILE: boards/nrf54l15dk_nrf54l15_cpuapp.conf | |
nrf54l15dk/nrf54l10/cpuapp: | |
append: | |
EXTRA_CONF_FILE: boards/nrf54l15dk_nrf54l10_cpuapp.conf | |
boards: | |
/nrf54l15dk.*/: | |
append: | |
EXTRA_DTC_OVERLAY_FILE: boards/nrf54l15dk_nrf54l15_cpuapp.overlay |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should change the overlay file name then? to something generic for all nrf54l15dk builds?
Matter requires some extra configuration for the power consumption measurements that are automatized. This change introduces snippet that simplifies it and adds dedicated variant in the sample.ymls.