There are many projects that turn a computer keyboard into a MIDI device, e.g. to connect to a MIDI synthesizer. But there are little projects that work the otherway around. i.e. A hardware solution to map MIDI notes to keyboard strokes. There are software tools available, like the MIDI Translator from Bone. But of course this limits the use for Windows and might not work in all cases.
This project uses a BeagleBone Black which comes with a USB Host and a USB client. The USB host is usually used to connect Keyboard/Mouse to the board, and the USB client is used to connect it to a PC for communication and mass storage device.
The mass storage device and the USB ethernet is created using GadgetFS using the ConfigFS Composite Gadget.
the script in /opt/scripts/boot/am335x_evm.sh sets up the /sys/kernel/config/usb_gadget/g_multi gadget with 3 functions:
/sys/kernel/config/usb_gadget/g_multi
├── bcdDevice
├── bcdUSB
├── bDeviceClass
├── bDeviceProtocol
├── bDeviceSubClass
├── bMaxPacketSize0
├── configs
│ └── c.1
│ ├── bmAttributes
│ ├── hid.usb0 -> ../../../../usb_gadget/g_multi/functions/hid.usb0
│ ├── MaxPower
│ └── strings
│ └── 0x409
│ └── configuration
├── functions
│ └── hid.usb0
│ ├── dev
│ ├── protocol
│ ├── report_desc
│ ├── report_length
│ └── subclass
├── idProduct
├── idVendor
├── os_desc
│ ├── b_vendor_code
│ ├── qw_sign
│ └── use
├── strings
│ └── 0x409
│ ├── manufacturer
│ ├── product
│ └── serialnumber
└── UDC
So it should be easy to add an extra gadget for a HID Keyboard
As first POC, we try to disable the all the gadgets in g_multi so we can disable the gadget and add our own (otherwise, we get Device Busy errors).
- Disable Mass Storage and Tethering
in
/etc/default/bb-bootuncomment the settings so the Mass Storage Device and the USB Network are disabled:
USB_IMAGE_FILE_DISABLED=yes
USB_NETWORK_DISABLED=yes- Disable the ACM (USB Serial)
Unfortunately, the acm device is not controlled via flags in the
bb-bootscript, so just uncomment the 2 lines in/opt/scripts/boot/am335x_evm.sh
# diff -u am335x_evm.sh.ori am335x_evm.sh
--- am335x_evm.sh.ori 2018-10-06 08:54:48.042948584 +0000
+++ am335x_evm.sh 2018-09-30 14:16:05.017540771 +0000
@@ -527,7 +527,7 @@
echo ${cpsw_5_mac} > functions/ecm.usb0/dev_addr
fi
- mkdir -p functions/acm.usb0
+ # disabled by tripod: mkdir -p functions/acm.usb0
if [ "x${has_img_file}" = "xtrue" ] ; then
echo "${log} enable USB mass_storage ${usb_image_file}"
@@ -549,7 +549,7 @@
ln -s functions/rndis.usb0 configs/c.1/
ln -s functions/ecm.usb0 configs/c.1/
fi
- ln -s functions/acm.usb0 configs/c.1/
+ # disable by tripod: ln -s functions/acm.usb0 configs/c.1/
if [ "x${has_img_file}" = "xtrue" ] ; then
ln -s functions/mass_storage.usb0 configs/c.1/
fi
- reboot NOTE Be sure to be connected via ethernet and remember the IP. otherwise it's the last thing you do :-)
- turn off UDC (USB Device Controller)
cd /sys/kernel/config/usb_gadget/g_multi
echo "" > UDC
- install HID Keyboad
./init.sh
For testing, compile the test_gadget.c, attach to a computer, and play around:
cc -o test_gadget test_gadget
sudo ./test_gadget /dev/hidg0 k
....
Of course it would be best, if we can keep the USB Network enabled.
so add the init stuff to: /opt/scripts/boot/am335x_evm.sh
# diff -u am335x_evm.ori am335x_evm.sh
--- am335x_evm.ori 2018-10-06 08:54:48.042948584 +0000
+++ am335x_evm.sh 2018-10-06 08:59:07.082173424 +0000
@@ -553,6 +553,18 @@
if [ "x${has_img_file}" = "xtrue" ] ; then
ln -s functions/mass_storage.usb0 configs/c.1/
fi
+ # -------------------------------------------
+ # create HID Keyboard
+ mkdir functions/hid.usb0
+ echo 1 > functions/hid.usb0/protocol
+ echo 1 > functions/hid.usb0/subclass
+ echo 8 > functions/hid.usb0/report_length
+ # write the keyboard usb page. see https://docs.mbed.com/docs/ble-hid/en/latest/api/md_doc_HID.html#keyboard
+ echo -ne "\\x05\\x01\\x09\\x06\\xa1\\x01\\x05\\x07\\x\\x19\\xe0\\x29\\xe7\\x15\\x00\\x25\\x01\\x75\\x01\\x95\\x08\\x81\\x02\\x95\\x01\\x\\x75\\x08\\x81\\x03\\x95\\x05\\x75\\x01\\x05\\x08\\x19\\x01\\x29\\x05\\x91\\x02\\x\\x95\\x01\\x75\\x03\\x91\\x03\\x95\\x06\\x75\\x08\\x15\\x00\\x25\\x65\\x05\\x07\\x19\\x00\\x29\\x65\\x81\\x00\\xc0" > functions/hid.usb0/report_desc
+
+ # 'install' new device
+ ln -s functions/hid.usb0 configs/c.1
+ # -------------------------------------------
Attach a MIDI instrument and test if we can read from it:
# amidi -l
Dir Device Name
IO hw:1,0,0 TD-1 MIDI 1
root@beaglebone:~# amidi -d -p hw:1,0,0
99 26 14
89 26 40
99 30 1C
89 30 40
The ALSA framework provides a sequencer, that sends MIDI events between clients.
To list all clients use aconnect -l. Now, if we want to receive MIDI events from a connected MIDI device, such as
a Keyboard or a DrumKit, we need to create a client and then connect the device to it.
For example, after connecting the TD-1 we see:
$ aconnect -l
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'TD-1' [type=kernel,card=1]
0 'TD-1 MIDI 1 '
Then, after starting the midi-listen test program:
$ aconnect -l
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'TD-1' [type=kernel,card=1]
0 'TD-1 MIDI 1 '
client 128: 'Midi Listener' [type=user,pid=3465]
0 'listen:in '
Then, we can connect the two:
$ aconnect 20:0 128:0
$ aconnect -l
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'TD-1' [type=kernel,card=1]
0 'TD-1 MIDI 1 '
Connecting To: 128:0
client 128: 'Midi Listener' [type=user,pid=3465]
0 'listen:in '
Connected From: 20:0
Of course this is a bit cumbersome to manually connect the device, we can also do it programmatically. see Capture from keyboard in ALSA - Sequencer.
TODO
The TD-1 allows to change the midi notes. so this table is my current setting
|----------------|--------|
| Pad | Note |
+----------------+--------+
| Kick | 0x24 |
| Snare Head | 0x26 |
| Snare Rim | 0x28 |
| Tom 1 | 0x30 |
| Tom 2 | 0x2d |
| Tom 3 | 0x2b |
| HH Open Bow | 0x2e |
| HH Open Edge | 0x1a |
| HH Closed Bow | 0x2a |
| HH Closed Edge | 0x16 |
| HH foot closed | 0x2c |
| Crash 1 (Bow) | 0x31 |
| Crash 1 (Edge) | 0x37 |
| Crash 2 (Bow) | 0x00 |
| Crash 2 (Edge) | 0x00 |
| Ride 2 (Bow) | 0x33 |
| Ride 2 (Edge) | 0x3b |
run /opt/scripts/tools/update_kernel.sh as root.
before:
Linux beaglebone 4.14.67-ti-r73 #1 SMP PREEMPT Thu Aug 30 00:08:52 UTC 2018 armv7l GNU/Linux
after:
Linux beaglebone 4.14.71-ti-r78 #1 SMP PREEMPT Tue Sep 25 21:14:59 UTC 2018 armv7l GNU/Linux
-
https://docs.mbed.com/docs/ble-hid/en/latest/api/md_doc_HID.html#keyboard
-
https://wiki.tizen.org/USB/Linux_USB_Layers/Configfs_Composite_Gadget/General_configuration
-
https://stackoverflow.com/questions/33016961/where-is-g-multi-configured-in-beaglebone-black
-
https://www.codeproject.com/Questions/1208305/Using-beaglebone-black-as-a-keyboard-device