mark w.
This is a work in progress. Trying to make a working arcade button to USB interface with the Nucleo F411RE.
This project was inspired by USB Joystick Device
The goal of this project is to build an simple interface that I will connect numerous Arcade buttons and joysticks to the Nucleo board, and the Nucleo will present itself as a USB Gamepad to Windows or Linux. The joysticks are Arcade joysticks that have four switches, up/down/left/right. It is not an analog joystick, just a set of switches. These will be connected to the Nucleo's pins configured as inputs.
The code will then continuously loop and test which buttons are closed, and transfer this data to the host via USBGamepad protocol.
Much thanks to Wim Huiskamp for his original project, documentation, and later reaching out to me to guide me to solving a last minute problem. Wim clued me into the fact that I needed a 1k5 pullup resistor between the 3v3 pin and the PA_12/D+ pin. Once I did this Windows detected the device as a Gamepad and registered it correctly! Yay!
Connecting USB cable to the board is as follows:
You will need a USB data cable (the one I used had a micro usb on one end and regular usb on the other). I cut off the micro USB end, and cut the insulation back about 30mm. This exposed four wires, Red, Black, White and Green. You will then either crimp some header connectors or solder directly to the Nucleo header pins as follows:
- Green USB D+ to PA_12
- White USB D- to PA_11
- Red USB 5V to E5V (with jumper JP5 set to E5V)
- Black USB GND to GND
As an extra debugging measure, you can connect both the ST/Link USB and the PA_12/11 USB to the Windows machine to run both at the same time, and you can see printf messages from within ST/Link.
We can verify the HID Vendor and Product IDs by looking at the Device Manager, and look for the HID Game Controller:
I used pid.codes to register my own Vendor_ID and Product_ID
If you go to the USB Game Controller control panel widget, you will see the new entry for Arcade Gamepad:
And here we can see all 32 buttons:
On the Nucleo board you may have difficulties depending on the revision. The board I am using is an STM32F411RE Revision C03, which has resistors and solder joints (bottom) to allow the use of the Crystal on the STLink board for USB purposes. After programming via STLink, remove the USB cable from the STLink, the jumper must be set to E5V to power the board from the PC's usb port. Plug the new cable into the PC.
When you're ready to install it in the arcade cabinet, or project, just remember to setup the jumper JP5 to E5V and you only need the single USB connection to the host.
Here are some useful links that I used to grasp all the little things involved in this project:
Diff: config.h
- Revision:
- 1:ad6066c16dbd
- Child:
- 4:05f4ace9508a
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/config.h Tue Dec 13 03:40:14 2016 +0000
@@ -0,0 +1,75 @@
+#define TARGET_STM32F4XX
+#define NUM_OF_BUTTONS 32
+
+
+// Joystick button input pin assignments.
+//
+// You can wire up to 32 GPIO ports to buttons (equipped with
+// momentary switches). Connect each switch between the desired
+// GPIO port and ground (J9 pin 12 or 14). When the button is pressed,
+// we'll tell the host PC that the corresponding joystick button is
+// pressed. We debounce the keystrokes in software, so you can simply
+// wire directly to pushbuttons with no additional external hardware.
+//
+// Note that we assign 24 buttons by default, even though the USB
+// joystick interface can handle up to 32 buttons. VP itself only
+// allows mapping of up to 24 buttons in the preferences dialog
+// (although it can recognize 32 buttons internally). If you want
+// more buttons, you can reassign pins that are assigned by default
+// as LedWiz outputs. To reassign a pin, find the pin you wish to
+// reassign in the LedWizPortMap array below, and change the pin name
+// there to NC (for Not Connected). You can then change one of the
+// "NC" entries below to the reallocated pin name. The limit is 32
+// buttons total.
+//
+// (If you're using TLC5940 chips to control outputs, many of the
+// GPIO pins that are mapped to LedWiz outputs in the default
+// mapping can be reassigned as keys, since the TLC5940 outputs
+// take over for the GPIO pins. The exceptions are the pins that
+// are reassigned to control the TLC5940 chips.)
+//
+// Note: PTD1 (pin J2-12) should NOT be assigned as a button input,
+// as this pin is physically connected on the KL25Z to the on-board
+// indicator LED's blue segment.
+PinName buttonMap[] = {
+ PC_10, // J10 pin 10, joystick button 1
+ PC_11, // J10 pin 8, joystick button 2
+ PC_12, // J10 pin 6, joystick button 3
+ PD_2, // J10 pin 4, joystick button 4
+
+ PC_13, // J10 pin 11, joystick button 5
+ PC_14, // J10 pin 5, joystick button 6
+
+ PC_15, // J9 pin 15, joystick button 7
+ PC_2, // J9 pin 13, joystick button 8
+ PC_3, // J9 pin 11, joystick button 9
+ PC_1, // J9 pin 9, joystick button 10
+ PC_0, // J9 pin 7, joystick button 11
+ PC_4, // J9 pin 5, joystick button 12
+ PA_10, // J9 pin 3, joystick button 13
+ PB_3, // J9 pin 1, joystick button 14
+
+ PB_5, // J2 pin 1, joystick button 15
+ PB_4, // J2 pin 3, joystick button 16
+ PB_13, // J2 pin 5, joystick button 17
+ PB_14, // J2 pin 7, joystick button 18
+ PB_15, // J2 pin 9, joystick button 19
+ PB_10, // J2 pin 11, joystick button 20
+ PB_1, // J2 pin 13, joystick button 21
+ PB_2, // J2 pin 17, joystick button 22
+ PC_7, // J2 pin 19, joystick button 23
+
+ PB_6, // J2 pin 20, joystick button 24
+
+ NC, // not used, joystick button 25
+ NC, // not used, joystick button 26
+ NC, // not used, joystick button 27
+ NC, // not used, joystick button 28
+ NC, // not used, joystick button 29
+ NC, // not used, joystick button 30
+ NC, // not used, joystick button 31
+ NC // not used, joystick button 32
+};
+// STANDARD ID SETTINGS. These provide full, transparent LedWiz compatibility.
+const uint16_t USB_VENDOR_ID = 0xFAFA; // LedWiz vendor ID = FAFA
+const uint16_t USB_PRODUCT_ID = 0x00F0; // LedWiz start of product ID range = 00F0
\ No newline at end of file