Skip to content

Commit

Permalink
applications: nrf_desktop: Update nRF54L15 DK doc
Browse files Browse the repository at this point in the history
The nRF54L15 PDK board is going to be replaced by nRF54L15 DK. Change
aligns documentation.

Jira: NCSDK-29114

Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
  • Loading branch information
MarekPieta committed Oct 2, 2024
1 parent 7dabcae commit 65891a7
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
8 changes: 4 additions & 4 deletions applications/nrf_desktop/board_configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -103,18 +103,18 @@ Sample dongle (``nrf5340dk/nrf5340``)
Input data comes from Bluetooth and is retransmitted to USB.
* The configuration with the B0 bootloader is set as default.

Sample mouse or keyboard (``nrf54l15pdk/nrf54l15/cpuapp``)
* The configuration uses the nRF54L15 Preview Development Kit (PDK).
Sample mouse or keyboard (``nrf54l15dk/nrf54l15/cpuapp``)
* The configuration uses the nRF54L15 Development Kit (DK).
* The build types allow to build the application as a mouse or a keyboard.
* Inputs are simulated based on the hardware button presses.
* On the nRF54L15 SoC, you can only use the **GPIO1** port for PWM hardware peripheral output.
Because of that, on the PDK PCA10156 revision v0.3.0, **LED 0** and **LED 2** cannot be used for PWM output.
Because of that, on the DK PCA10156 revision v0.8.1, **LED 0** and **LED 2** cannot be used for PWM output.
You can still use these LEDs with the PWM LED driver, but you must set the LED color to ``LED_COLOR(255, 255, 255)`` or ``LED_COLOR(0, 0, 0)``.
This ensures the PWM peripheral is not used for the mentioned LEDs.
* Only Bluetooth LE transport is enabled.
Bluetooth LE is configured to use Nordic Semiconductor's SoftDevice Link Layer and Low Latency Packet Mode (LLPM).
* In debug configurations, logs are provided through the UART.
For detailed information on working with the nRF54L15 PDK, see the :ref:`ug_nrf54l15_gs` documentation.
For detailed information on working with the nRF54L15 DK, see the :ref:`ug_nrf54l15_gs` documentation.
* The configurations use the MCUboot bootloader built in the direct-xip mode (``MCUBOOT+XIP``) and support firmware updates using the :ref:`nrf_desktop_dfu`.
* The board supports the ``debug`` :ref:`nrf_desktop_bluetooth_guide_fast_pair` configuration that acts as a mouse (``fast_pair`` file suffix).
The configuration uses the MCUboot bootloader built in the direct-xip mode (``MCUBOOT+XIP``), and supports firmware updates using the :ref:`nrf_desktop_dfu` and :ref:`nrf_desktop_dfu_mcumgr`.
Expand Down
2 changes: 1 addition & 1 deletion applications/nrf_desktop/description.rst
Original file line number Diff line number Diff line change
Expand Up @@ -366,7 +366,7 @@ Depending on the development kit you use, you need to select the respective conf

.. table-from-rows:: /includes/sample_board_rows.txt
:header: heading
:rows: nrf52840dk_nrf52840, nrf52833dk_nrf52833, nrf52833dk_nrf52820, nrf5340dk_nrf5340_cpuapp, nrf54l15pdk_nrf54l15_cpuapp, nrf54h20dk_nrf54h20_cpuapp
:rows: nrf52840dk_nrf52840, nrf52833dk_nrf52833, nrf52833dk_nrf52820, nrf5340dk_nrf5340_cpuapp, nrf54l15dk_nrf54l15_cpuapp, nrf54h20dk_nrf54h20_cpuapp

Depending on the configuration, a DK may act either as mouse, keyboard or dongle.
For information about supported configurations for each board, see the :ref:`nrf_desktop_board_configuration_files` section.
Expand Down
2 changes: 1 addition & 1 deletion applications/nrf_desktop/doc/wheel.rst
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Enable the module with the :ref:`CONFIG_DESKTOP_WHEEL_ENABLE <config_desktop_app

For detecting rotation, the wheel module uses Zephyr's QDEC driver.
You can enable the module only when QDEC is configured in DTS and the Zephyr's QDEC driver is enabled with the :kconfig:option:`CONFIG_QDEC_NRFX` Kconfig option.
If your board supports multiple QDEC instances (for example ``nrf54l15pdk/nrf54l15/cpuapp``), you also need to specify the used QDEC instance with the ``nrfdesktop-wheel-qdec`` DT alias.
If your board supports multiple QDEC instances (for example ``nrf54l15dk/nrf54l15/cpuapp``), you also need to specify the used QDEC instance with the ``nrfdesktop-wheel-qdec`` DT alias.
If your board supports only one QDEC instance, the module relies on the ``qdec`` DT label and you need not define the DT alias.

The QDEC DTS configuration specifies how many steps are done during one full angle.
Expand Down

0 comments on commit 65891a7

Please sign in to comment.