applications: nrf_desktop: add support for the nRF54LM20 DK #23265

kapi-no · 2025-07-11T10:19:47Z

Issues to resolve:

The application does not boot due to the MCUboot issues.
The fix depends on the following PR: manifest: sdk-zephyr: [nrf noup] boards: nordic: nrf54lm20 adjust ROM_START_OFFSET #23285

NordicBuilder · 2025-07-11T10:25:40Z

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 4

Inputs:

Sources:

sdk-nrf: PR head: 762e74e894f6257f99e4bb766f01cb14f4f3a202

more details

sdk-nrf:

PR head: 762e74e894f6257f99e4bb766f01cb14f4f3a202
merge base: 2ad751afa927550a5c93c10110fc427b7ffe442d
target head (main): 2ad751afa927550a5c93c10110fc427b7ffe442d
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (25)

applications
│  ├── nrf_desktop
│  │  ├── configuration
│  │  │  ├── nrf54lm20dk_nrf54lm20a_cpuapp
│  │  │  │  ├── app.overlay
│  │  │  │  ├── app_common.dtsi
│  │  │  │  ├── app_llvm.overlay
│  │  │  │  ├── app_release.overlay
│  │  │  │  ├── buttons_def.h
│  │  │  │  ├── click_detector_def.h
│  │  │  │  ├── hid_keyboard_leds_def.h
│  │  │  │  ├── hid_keymap_def.h
│  │  │  │  ├── images
│  │  │  │  │  ├── mcuboot
│  │  │  │  │  │  ├── app.overlay
│  │  │  │  │  │  ├── mcuboot_private.pem
│  │  │  │  │  │  ├── prj.conf
│  │  │  │  │  │  ├── prj_llvm.conf
│  │  │  │  │  │  │ prj_release.conf
│  │  │  │  ├── led_state_def.h
│  │  │  │  ├── pm_static.yml
│  │  │  │  ├── pm_static_llvm.yml
│  │  │  │  ├── pm_static_release.yml
│  │  │  │  ├── port_state_def.h
│  │  │  │  ├── prj.conf
│  │  │  │  ├── prj_llvm.conf
│  │  │  │  ├── prj_release.conf
│  │  │  │  ├── sysbuild.conf
│  │  │  │  ├── sysbuild_llvm.conf
│  │  │  │  │ sysbuild_release.conf
│  │  │ sample.yaml

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

◻️ Toolchain
◻️ Build twister
◻️ Integration tests
- ◻️ desktop52_verification

Disabled integration tests

- test-fw-nrfconnect-nrf_lrcs_mosh
- test-fw-nrfconnect-nrf_lrcs_positioning
- doc-internal
- test_ble_nrf_config
- test-fw-nrfconnect-apps
- test-fw-nrfconnect-ble_mesh
- test-fw-nrfconnect-ble_samples
- test-fw-nrfconnect-chip
- test-fw-nrfconnect-fem
- test-fw-nrfconnect-nfc
- test-fw-nrfconnect-nrf-iot_cloud
- test-fw-nrfconnect-nrf-iot_libmodem-nrf
- test-fw-nrfconnect-nrf-iot_lwm2m
- test-fw-nrfconnect-nrf-iot_samples
- test-fw-nrfconnect-nrf-iot_serial_lte_modem
- test-fw-nrfconnect-nrf-iot_thingy91
- test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
- test-fw-nrfconnect-nrf_crypto
- test-fw-nrfconnect-ps-main
- test-fw-nrfconnect-rpc
- test-fw-nrfconnect-rs
- test-fw-nrfconnect-tfm
- test-fw-nrfconnect-thread-main
- test-low-level
- test-sdk-audio
- test-sdk-find-my
- test-sdk-mcuboot
- test-sdk-pmic-samples
- test-sdk-wifi
- test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

github-actions · 2025-07-11T11:03:38Z

You can find the documentation preview for this PR here.

MarekPieta · 2025-07-11T12:06:48Z

applications/nrf_desktop/configuration/nrf54lm20dk_nrf54lm20a_cpuapp/boards/app_common.dtsi

Why locating DTS overlays in the boards subdirectory? We no longer need separate DTS overlays per board revision, so we can already move the DTS overlays one directory up (for consistency with other supported boards). It's also no longer needed to repeat board name in file names.

MarekPieta · 2025-07-11T12:12:15Z

applications/nrf_desktop/configuration/nrf54lm20dk_nrf54lm20a_cpuapp/boards/app_common.dtsi

* The configuration needs to match the used board revision. -> no longer needed

This statement is also present in the nrf54l05/10/15 targets. I can delete it, as DTS definitions typically need to match the board revision, and this sentence seems to state the obvious.

NordicBuilder · 2025-07-14T09:15:37Z

Memory footprint analysis revealed the following potential issues

applications.nrf_desktop.zdebug.usb_next[nrf52840dk/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug.usb_next[nrf52840dongle/nrf52840]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug.usb_next[nrf52840gmouse/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52833dk/nrf52833]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52833dongle/nrf52833]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52840dk/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52840dongle/nrf52840]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52840gmouse/nrf52840]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52dmouse/nrf52832]: ROM size increased by 1396[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf52kbd/nrf52832]: ROM size increased by 1888[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug[nrf54l15dk/nrf54l05/cpuapp]: ROM size increased by 516[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_4llpmconn[nrf52840dongle/nrf52840]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_dongle.usb_next[nrf52840dk/nrf52840]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_dongle[nrf52840dk/nrf52840]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_fast_pair.gmouse[nrf52840gmouse/nrf52840]: ROM size increased by 1888[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_keyboard.usb_next[nrf52840dk/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_keyboard[nrf52840dk/nrf52840]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_mcuboot_qspi[nrf52840dk/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_mcuboot_smp[nrf52840dk/nrf52840]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_nrf21540ek[nrf52840dk/nrf52840]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebug_wwcb[nrf52840dk/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zdebugwithshell[nrf52840dk/nrf52840]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zrelease.usb_next[nrf52840dk/nrf52840]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zrelease[nrf52840dongle/nrf52840]: ROM size increased by 1840[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zrelease[nrf52840gmouse/nrf52840]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zrelease[nrf52kbd/nrf52832]: ROM size increased by 1880[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zrelease_fast_pair.keyboard[nrf52kbd/nrf52832]: ROM size increased by 1872[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)
applications.nrf_desktop.zrelease_keyboard[nrf54l15dk/nrf54l05/cpuapp]: ROM size increased by 512[B] in comparison to the main[db745e9] branch. - link (cc: @nrfconnect/ncs-si-bluebagel)

Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-23265/3)

Added initial support for the nRF54LM20 DK in the nRF Desktop application. The new target has been tested with nRF54LM20 DK v0.3.0. The DK target will eventually supersede the PDK target. For now, both targets are maintained in the nRF Desktop application. Ref: NCSDK-33956 Signed-off-by: Kamil Piszczek <[email protected]>

kapi-no · 2025-07-14T12:09:09Z

The last force push is a pure rebase operation to include the fix for the MCUboot bootloader for the nRF54LM20 DK.

kapi-no requested a review from a team as a code owner July 11, 2025 10:19

github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Jul 11, 2025

kapi-no force-pushed the nrf_desktop_nrf54lm20dk_transition branch from 5ffcd69 to 83a60c4 Compare July 11, 2025 10:32

nordic-segl approved these changes Jul 11, 2025

View reviewed changes

kapi-no added the DNM label Jul 11, 2025

MarekPieta approved these changes Jul 11, 2025

View reviewed changes

kapi-no force-pushed the nrf_desktop_nrf54lm20dk_transition branch from 83a60c4 to 8e9524d Compare July 14, 2025 08:41

kapi-no force-pushed the nrf_desktop_nrf54lm20dk_transition branch from 8e9524d to 762e74e Compare July 14, 2025 12:08

kapi-no removed the DNM label Jul 14, 2025

zycz approved these changes Jul 14, 2025

View reviewed changes

kapi-no merged commit e6286fd into nrfconnect:main Jul 14, 2025
13 of 14 checks passed

kapi-no mentioned this pull request Jul 14, 2025

applications: nrf_desktop: Disable advertising when connected via USB #23006

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

applications: nrf_desktop: add support for the nRF54LM20 DK #23265

applications: nrf_desktop: add support for the nRF54LM20 DK #23265

Uh oh!

kapi-no commented Jul 11, 2025 •

edited

Loading

Uh oh!

NordicBuilder commented Jul 11, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Jul 11, 2025

Uh oh!

MarekPieta Jul 11, 2025

Uh oh!

kapi-no Jul 14, 2025

Uh oh!

MarekPieta Jul 11, 2025

Uh oh!

kapi-no Jul 14, 2025

Uh oh!

kapi-no Jul 14, 2025

Uh oh!

NordicBuilder commented Jul 14, 2025

Uh oh!

kapi-no commented Jul 14, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

applications: nrf_desktop: add support for the nRF54LM20 DK #23265

applications: nrf_desktop: add support for the nRF54LM20 DK #23265

Uh oh!

Conversation

kapi-no commented Jul 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NordicBuilder commented Jul 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CI Information

Inputs:

Sources:

Github labels

Outputs:

Toolchain

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

Uh oh!

github-actions bot commented Jul 11, 2025

Uh oh!

MarekPieta Jul 11, 2025

Choose a reason for hiding this comment

Uh oh!

kapi-no Jul 14, 2025

Choose a reason for hiding this comment

Uh oh!

MarekPieta Jul 11, 2025

Choose a reason for hiding this comment

Uh oh!

kapi-no Jul 14, 2025

Choose a reason for hiding this comment

Uh oh!

kapi-no Jul 14, 2025

Choose a reason for hiding this comment

Uh oh!

NordicBuilder commented Jul 14, 2025

Memory footprint analysis revealed the following potential issues

Uh oh!

kapi-no commented Jul 14, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

kapi-no commented Jul 11, 2025 •

edited

Loading

NordicBuilder commented Jul 11, 2025 •

edited

Loading