Hid keyboard device how to#
Hid keyboard device drivers#
Hid keyboard device update#
Hid keyboard device code#

Hid keyboard device drivers#

There are вЂњstandards or guidelinesвЂќ for different USB HID devices like mouse, keyboard, joystick, вЂ¦ and therefore drivers can be generalised amongs manufacturers. This descriptors are sent to host at initialisation and host afterwards expect data вЂ“ called reports вЂ“ as they were set here. This is an description of all interface reports so the host can know what to expect.

Hid keyboard device code#

This is USB HID device Configuration Descriptor вЂ“ defines general device informations about power, number/type of interface/s вЂ¦ Code is quite neatly commented by default.

We can learn more about this вЂњdefaultвЂќ implemented device by exploring device descriptors in this file (usbd_hid.c). In fact, mouse itself is merged into one report containing buttons and вЂњjoystickвЂќ вЂ“ axes (X, Y, wheel)! This is the file that holds all informations about what kind of a USB device this is, how its reports will look.ДЄs you can see, вЂњdefaultвЂќ file explains where our mouse (detected by PC) came from.

USB device/report configuration in usbd_hid.c.

This is set with CubeMX so donвЂ™t change this defines.

USB configuration defines in usbd_conf.h.

I suggest to leave VID/PID for the time of testing. Also, VID is something usb.org manage and costs around 2000в‚¬ to obtain your own Vendor ID. You can change this defines but be carefull when changing VID and PID, since PC uses the VID/PIDВ combination to find the drivers for this specific device. But with a little knowledge and look-around, you can find all USB HID specifics in this files:

There is no вЂњsinge file/functionвЂќ to implement USB mouse like arduino: Mouse.begin(). It is wise to get familiar with basics of USB before you get on to more serious work. More about file hierarchy can be found in chapter 2 of STM32Cube USB device library user manual. вЂ“ usbd_desc.c (provides USB device descriptors) вЂ“ usbd_device.c (provides initialising function called from main()) вЂ“ usbd_conf.c (provides low layer / HAL functions) вЂ“ usbd_hid.c (provides everything to interact with USB host, send reports, вЂ¦) вЂ“ usbd_ioreq.c, usbd_ctlreq.c (provides the USB IO requests) вЂ“ usbd_core.c (provides all USB device core functions) Lets take a look on CubeMX generated files: You might wonder where this mouse came from. It should show as additional Mouse device under вЂњMice and other pointing devicesвЂќ. When this is done, connect your usb cable to PC and wait for OS to initialise device. Button for triggering sending USB reports and LEDs for status. This is a template HID mouse, that works straight out of the box and is instantly recognised by PC when connecting USB cable. Note 2: Initialise USB as Full-Speed device, as Human Interface Device Class. In my case, I used 16MHz external oscillator. Note 1: USB in general need a proper reliable clock. Intialise all peripheral: USB, HSE, SWD, button (to send USB reports), leds (just for testing purposes).

Hid keyboard device update#

Update (): see the latest project with STM32 + USB + AHK here! Default USB HID device with STM32CubeMx STM32L100 discovery board was used for test.

Hid keyboard device how to#

Here is an example of a basic вЂ“ default code, which turns out to be USB HID mouse, and a guide how to transform this code to keyboard. I decided to break down this to smaller parts of modifying STM32 USB HID code, generated with STM32CubeMx. There is a post (STM32 And Custom USB HID Device? Yes Please!) that gets a lot of attention, although at the time it was created, only vague вЂњhow-toвЂќ was presented.