Bluetooth: Peripheral HIDS mouse
The Peripheral HIDS mouse sample demonstrates how to use the GATT Human Interface Device (HID) Service to implement a mouse input device that you can connect to your computer. This sample also shows how to perform directed advertising.
The sample supports the following development kits:
When built for an
_ns build target, the sample is configured to compile and run as a non-secure application with Cortex-M Security Extensions enabled.
Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.
If you use nRF5340 DK, the additional configuration of the network core will be taken from the
For more details, see Image-specific variables.
The sample uses the buttons on a development kit to simulate the movement of a mouse. The four buttons simulate movement to the left, upward, to the right, and downward, respectively. Mouse clicks are not simulated.
This sample exposes the HID GATT Service. It uses a report map for a generic mouse.
You can also disable directed advertising feature by clearing the BT_DIRECTED_ADVERTISING flag in the application configuration. This feature is enabled by default and it changes the way in which advertising works in comparison to the other Bluetooth® Low Energy samples. When the device wants to advertise, it starts with high duty cycle directed advertising provided that it has bonding information. If the timeout occurs, then the device starts directed advertising to the next bonded peer. If all bonding information is used and there is still no connection, then the regular advertising starts.
- Button 1:
Simulate moving the mouse pointer 5 pixels to the left.
When pairing, press this button to confirm the passkey value that is printed on the COM listener to pair with the other device.
- Button 2:
Simulate moving the mouse pointer 5 pixels upward.
When pairing, press this button to reject the passkey value that is printed on the COM listener to prevent pairing with the other device.
- Button 3:
Simulate moving the mouse pointer 5 pixels to the right.
- Button 4:
Simulate moving the mouse pointer 5 pixels downward.
See Configuring your application for information about how to permanently or temporarily change the configuration.
The HID service specification does not require encryption (
CONFIG_BT_HIDS_DEFAULT_PERM_RW_ENCRYPT), but some systems disconnect from the HID devices that do not support security.
This sample can be found under
samples/bluetooth/peripheral_hids_mouse in the nRF Connect SDK folder structure.
When built as firmware image for the
_ns build target, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE).
Because of this, it automatically includes the Trusted Firmware-M (TF-M).
To read more about CMSE, see Processing environments.
To build the sample with Visual Studio Code, follow the steps listed on the How to build an application page in the nRF Connect for VS Code extension documentation. See Building and programming an application for other building and programming scenarios and Testing and debugging an application for general information about testing and debugging in the nRF Connect SDK.
After programming the sample to your development kit, you can test it either by connecting the development kit as a mouse device to a Microsoft Windows computer or by connecting to it with nRF Connect for Desktop.
Testing with a Microsoft Windows computer
To test with a Microsoft Windows computer that has a Bluetooth radio, complete the following steps:
Power on your development kit.
On your Windows computer, search for Bluetooth devices and connect to the device named “NCS HIDS mouse”.
Push Button 1 on the kit. Observe that the mouse pointer on the computer moves to the left.
Push Button 2. Observe that the mouse pointer on the computer moves upward.
Push Button 3. Observe that the mouse pointer on the computer moves to the right.
Push Button 4. Observe that the mouse pointer on the computer moves downward.
Disconnect the computer from the device by removing the device from the computer’s devices list.
Testing with nRF Connect for Desktop
To test with nRF Connect for Desktop, complete the following steps:
Power on your development kit.
Start nRF Connect for Desktop.
Open the Bluetooth Low Energy app.
Connect to the device from the app. The device is advertising as “NCS HIDS mouse”
Optionally, bond to the device. Click the settings button for the device in the app, select Pair, check Perform Bonding, and click Pair. Optionally check Enable MITM protection to pair with MITM protection and use a button on the device to confirm or reject passkey value.
Click Match in the app. Wait until the bond is established before you continue.
Observe that the services of the connected device are shown.
Click Play for all HID Report characteristics.
Push Button 1 on the kit. Observe that a notification is received on one of the HID Report characteristics, containing the value
Mouse motion reports contain data with an X-translation and a Y-translation. These are transmitted as 12-bit signed integers. The format used for mouse reports is the following byte array, where LSB/MSB is the least/most significant bit:
[8 LSB (X), 4 LSB (Y) | 4 MSB(X), 8 MSB(Y)].
FB0F00denotes an X-translation of FFB = -5 (two’s complement format), which means a movement of 5 pixels to the left, and a Y-translation of 000 = 0.
Push Button 2. Observe that the value
00B0FFis received on the same HID Report characteristic.
Push Button 3. Observe that the value
050000is received on the same HID Report characteristic.
Push Button 4. Observe that the value
005000is received on the same HID Report characteristic.
Disconnect the device in nRF Connect. Observe that no new notifications are received and the device is advertising.
As bond information is preserved by nRF Connect, you can immediately reconnect to the device by clicking the Connect button again.
This sample uses the following nRF Connect SDK libraries:
In addition, it uses the following Zephyr libraries:
The sample also uses the following secure firmware component: