> For the complete documentation index, see [llms.txt](https://amobile-solutions.gitbook.io/yocto-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amobile-solutions.gitbook.io/yocto-developer-guide/test-and-use-the-interface/buttons.md).

# Buttons

{% hint style="info" %}
The following instructions utilize the SD510 for demonstration purposes. These procedures are applicable to other development boards.
{% endhint %}

## Testing an Event Device

To test an event device, use the command below to list and number the available devices:

```bash
evtest
```

Select the device event number you wish to test and activate the device by pressing its button.

### Example on the SBC-MB510:

```
root@sd510:~# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      mtk-pmic-keys
/dev/input/event1:      mt8370-evk HDMI Jack
```

Prompt:

```
Select the device event number [0-1]: 0
```

```
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x1
Input device name: "mtk-pmic-keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 102 (KEY_HOME)
    Event code 116 (KEY_POWER)
Properties:
Testing ... (interrupt to exit)
Event: time 1738820852.489592, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1738820852.489592, -------------- SYN_REPORT ------------
```

{% hint style="info" %}
The SBC-MB510's KEY\_HOME is intended for debugging purposes only.
{% endhint %}
