9632360caa
* Add ARRAY_SIZE and CEILING utility macros * Apply a coccinelle patch to use ARRAY_SIZE * fix up some straggling items * Fix 'make test:secure' * Enhance ARRAY_SIZE macro to reject acting on pointers The previous definition would not produce a diagnostic for ``` int *p; size_t num_elem = ARRAY_SIZE(p) ``` but the new one will. * explicitly get definition of ARRAY_SIZE * Convert to ARRAY_SIZE when const is involved The following spatch finds additional instances where the array is const and the division is by the size of the type, not the size of the first element: ``` @ rule5a using "empty.iso" @ type T; const T[] E; @@ - (sizeof(E)/sizeof(T)) + ARRAY_SIZE(E) @ rule6a using "empty.iso" @ type T; const T[] E; @@ - sizeof(E)/sizeof(T) + ARRAY_SIZE(E) ``` * New instances of ARRAY_SIZE added since initial spatch run * Use `ARRAY_SIZE` in docs (found by grep) * Manually use ARRAY_SIZE hs_set is expected to be the same size as uint16_t, though it's made of two 8-bit integers * Just like char, sizeof(uint8_t) is guaranteed to be 1 This is at least true on any plausible system where qmk is actually used. Per my understanding it's universally true, assuming that uint8_t exists: https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1 * Run qmk-format on core C files touched in this branch Co-authored-by: Stefan Kerkmann <karlk90@pm.me> |
||
---|---|---|
.. | ||
examples | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
address.h | ||
adk.cpp | ||
adk.h | ||
avrpins.h | ||
BTD.cpp | ||
BTD.h | ||
BTHID.cpp | ||
BTHID.h | ||
cdc_XR21B1411.cpp | ||
cdc_XR21B1411.h | ||
cdcacm.cpp | ||
cdcacm.h | ||
cdcftdi.cpp | ||
cdcftdi.h | ||
cdcprolific.cpp | ||
cdcprolific.h | ||
confdescparser.h | ||
controllerEnums.h | ||
gpl2.txt | ||
hexdump.h | ||
hid.cpp | ||
hid.h | ||
hidboot.cpp | ||
hidboot.h | ||
hidescriptorparser.cpp | ||
hidescriptorparser.h | ||
hiduniversal.cpp | ||
hiduniversal.h | ||
hidusagestr.h | ||
hidusagetitlearrays.cpp | ||
keywords.txt | ||
library.json | ||
library.properties | ||
macros.h | ||
masstorage.cpp | ||
masstorage.h | ||
max_LCD.cpp | ||
max_LCD.h | ||
max3421e.h | ||
message.cpp | ||
message.h | ||
parsetools.cpp | ||
parsetools.h | ||
printhex.h | ||
PS3BT.cpp | ||
PS3BT.h | ||
PS3Enums.h | ||
PS3USB.cpp | ||
PS3USB.h | ||
PS4BT.h | ||
PS4Parser.cpp | ||
PS4Parser.h | ||
PS4USB.h | ||
PSBuzz.cpp | ||
PSBuzz.h | ||
README.md | ||
settings.h | ||
sink_parser.h | ||
SPP.cpp | ||
SPP.h | ||
usb_ch9.h | ||
Usb.cpp | ||
Usb.h | ||
UsbCore.h | ||
usbhost.h | ||
usbhub.cpp | ||
usbhub.h | ||
version_helper.h | ||
Wii.cpp | ||
Wii.h | ||
WiiCameraReadme.md | ||
xboxEnums.h | ||
XBOXOLD.cpp | ||
XBOXOLD.h | ||
XBOXONE.cpp | ||
XBOXONE.h | ||
XBOXRECV.cpp | ||
XBOXRECV.h | ||
XBOXUSB.cpp | ||
XBOXUSB.h |
USB Host Library Rev.2.0
The code is released under the GNU General Public License.
Summary
This is Revision 2.0 of MAX3421E-based USB Host Shield Library for AVR's.
Project main web site is: http://www.circuitsathome.com.
Some information can also be found at: http://blog.tkjelectronics.dk/.
The shield can be purchased at the main site: https://www.circuitsathome.com/arduino_usb_host_shield_projects/ or from TKJ Electronics: http://shop.tkjelectronics.dk/product_info.php?products_id=43.
For more information about the hardware see the Hardware Manual.
Developed By
- Oleg Mazurov, Circuits@Home - mazurov@circuitsathome.com
- Alexei Glushchenko, Circuits@Home - alex-gl@mail.ru
- Developers of the USB Core, HID, FTDI, ADK, ACM, and PL2303 libraries
- Kristian Lauszus, TKJ Electronics - kristianl@tkjelectronics.com
- Andrew Kroll - xxxajk@gmail.com
- Major contributor to mass storage code
- guruthree
- Xbox ONE controller support
Donate
Help yourself by helping us support you! Many thousands of hours have been spent developing the USB Host Shield library. Since you find it useful, please consider donating via the button below. Donations will allow us to support you by ensuring hardware that you have can be acquired in order to add support for your microcontroller board.
Table of Contents
How to include the library
Arduino Library Manager
First install Arduino IDE version 1.6.2 or newer, then simply use the Arduino Library Manager to install the library.
Please see the following page for instructions: http://www.arduino.cc/en/Guide/Libraries#toc3.
Manual installation
First download the library by clicking on the following link: https://github.com/felis/USB_Host_Shield_2.0/archive/master.zip.
Then uncompress the zip folder and rename the directory to "USB_Host_Shield_20", as any special characters are not supported by the Arduino IDE.
Now open up the Arduino IDE and open "File>Preferences". There you will see the location of your sketchbook. Open that directory and create a directory called "libraries" inside that directory. Now move the "USB_Host_Shield_20" directory to the "libraries" directory.
The final structure should look like this:
- Arduino/
- libraries/
- USB_Host_Shield_20/
- libraries/
Now quit the Arduino IDE and reopen it.
Now you should be able to go open all the examples codes by navigating to "File>Examples>USB_Host_Shield_20" and then select the example you will like to open.
For more information visit the following sites: http://arduino.cc/en/Guide/Libraries and https://learn.adafruit.com/adafruit-all-about-arduino-libraries-install-use.
How to use the library
Documentation
Documentation for the library can be found at the following link: http://felis.github.com/USB_Host_Shield_2.0/.
Enable debugging
By default serial debugging is disabled. To turn it on simply change ENABLE_UHS_DEBUGGING
to 1 in settings.h like so:
#define ENABLE_UHS_DEBUGGING 1
Boards
Currently the following boards are supported by the library:
- All official Arduino AVR boards (Uno, Duemilanove, Mega, Mega 2560, Mega ADK, Leonardo etc.)
- Arduino Due, Intel Galileo, Intel Galileo 2, and Intel Edison
- Note that the Intel Galileo uses pin 2 and 3 as INT and SS pin respectively by default, so some modifications to the shield are needed. See the "Interface modifications" section in the hardware manual for more information.
- Teensy (Teensy++ 1.0, Teensy 2.0, Teensy++ 2.0, and Teensy 3.x)
- Note if you are using the Teensy 3.x you should download this SPI library as well: https://github.com/xxxajk/spi4teensy3. You should then add
#include <spi4teensy3.h>
to your .ino file.
- Note if you are using the Teensy 3.x you should download this SPI library as well: https://github.com/xxxajk/spi4teensy3. You should then add
- Balanduino
- Sanguino
- Black Widdow
- RedBearLab nRF51822
- Digilent chipKIT
The following boards need to be activated manually in settings.h:
- Arduino Mega ADK
- If you are using Arduino 1.5.5 or newer there is no need to activate the Arduino Mega ADK manually
- Black Widdow
Simply set the corresponding value to 1 instead of 0.
Bluetooth libraries
The BTD library is a general purpose library for an ordinary Bluetooth dongle. This library make it easy to add support for different Bluetooth services like a PS3 or a Wii controller or SPP which is a virtual serial port via Bluetooth. Some different examples can be found in the example directory.
The BTD library also makes it possible to use multiple services at once, the following example sketch is an example of this: PS3SPP.ino.
BTHID library
The Bluetooth HID library allows you to connect HID devices via Bluetooth to the USB Host Shield.
Currently HID mice and keyboards are supported.
It uses the standard Boot protocol by default, but it is also able to use the Report protocol as well. You would simply have to call setProtocolMode()
and then parse HID_RPT_PROTOCOL
as an argument. You will then have to modify the parser for your device. See the example: BTHID.ino for more information.
The PS4 library also uses this class to handle all Bluetooth communication.
For information see the following blog post: http://blog.tkjelectronics.dk/2013/12/bluetooth-hid-devices-now-supported-by-the-usb-host-library/.
SPP library
SPP stands for "Serial Port Profile" and is a Bluetooth protocol that implements a virtual comport which allows you to send data back and forth from your computer/phone to your Arduino via Bluetooth. It has been tested successfully on Windows, Mac OS X, Linux, and Android.
Take a look at the SPP.ino example for more information.
More information can be found at these blog posts:
- http://www.circuitsathome.com/mcu/bluetooth-rfcommspp-service-support-for-usb-host-2-0-library-released
- http://blog.tkjelectronics.dk/2012/07/rfcommspp-library-for-arduino/
To implement the SPP protocol I used a Bluetooth sniffing tool called PacketLogger developed by Apple. It enables me to see the Bluetooth communication between my Mac and any device.
PS4 Library
The PS4BT library is split up into the PS4BT and the PS4USB library. These allow you to use the Sony PS4 controller via Bluetooth and USB.
The PS4BT.ino and PS4USB.ino examples shows how to easily read the buttons, joysticks, touchpad and IMU on the controller via Bluetooth and USB respectively. It is also possible to control the rumble and light on the controller and get the battery level.
Before you can use the PS4 controller via Bluetooth you will need to pair with it.
Simply create the PS4BT instance like so: PS4BT PS4(&Btd, PAIR);
and then hold down the Share button and then hold down the PS without releasing the Share button. The PS4 controller will then start to blink rapidly indicating that it is in paring mode.
It should then automatically pair the dongle with your controller. This only have to be done once.
For information see the following blog post: http://blog.tkjelectronics.dk/2014/01/ps4-controller-now-supported-by-the-usb-host-library/.
Also check out this excellent Wiki by Frank Zhao about the PS4 controller: http://eleccelerator.com/wiki/index.php?title=DualShock_4 and this Linux driver: https://github.com/chrippa/ds4drv.
PS3 Library
These libraries consist of the PS3BT and PS3USB. These libraries allows you to use a Dualshock 3, Navigation or a Motion controller with the USB Host Shield both via Bluetooth and USB.
In order to use your Playstation controller via Bluetooth you have to set the Bluetooth address of the dongle internally to your PS3 Controller. This can be achieved by first plugging in the Bluetooth dongle and wait a few seconds. Now plug in the controller via USB and wait until the LEDs start to flash. The library has now written the Bluetooth address of the dongle to the PS3 controller.
Finally simply plug in the Bluetooth dongle again and press PS on the PS3 controller. After a few seconds it should be connected to the dongle and ready to use.
Note: You will have to plug in the Bluetooth dongle before connecting the controller, as the library needs to read the address of the dongle. Alternatively you could set it in code like so: PS3BT.ino#L20.
For more information about the PS3 protocol see the official wiki: https://github.com/felis/USB_Host_Shield_2.0/wiki/PS3-Information.
Also take a look at the blog posts:
- http://blog.tkjelectronics.dk/2012/01/ps3-controller-bt-library-for-arduino/
- http://www.circuitsathome.com/mcu/sony-ps3-controller-support-added-to-usb-host-library
- http://www.circuitsathome.com/mcu/arduino/interfacing-ps3-controllers-via-usb
A special thanks go to the following people:
- Richard Ibbotson who made this excellent guide: https://www.circuitsathome.com/mcu/ps3-and-wiimote-game-controllers-on-the-arduino-host-shield-part-1/
- Tomoyuki Tanaka for releasing his code for the Arduino USB Host shield connected to the wiimote: http://www.circuitsathome.com/mcu/rc-car-controlled-by-wii-remote-on-arduino
Also a big thanks all the people behind these sites about the Motion controller:
- http://thp.io/2010/psmove/
- http://www.copenhagengamecollective.org/unimove/
- https://github.com/thp/psmoveapi
- http://code.google.com/p/moveonpc/
Xbox Libraries
The library supports both the original Xbox controller via USB and the Xbox 360 controller both via USB and wirelessly.
Xbox library
The XBOXOLD class implements support for the original Xbox controller via USB.
All the information are from the following sites:
- https://github.com/torvalds/linux/blob/master/Documentation/input/devices/xpad.rst
- https://github.com/torvalds/linux/blob/master/drivers/input/joystick/xpad.c
- http://euc.jp/periphs/xbox-controller.ja.html
- https://github.com/Grumbel/xboxdrv/blob/stable/PROTOCOL#L15
Xbox 360 Library
The library support one Xbox 360 via USB or up to four Xbox 360 controllers wirelessly by using a Xbox 360 wireless receiver.
To use it via USB use the XBOXUSB library or to use it wirelessly use the XBOXRECV library.
Note that a Wireless controller can NOT be used via USB!
Examples code can be found in the examples directory.
Also see the following blog posts:
- http://www.circuitsathome.com/mcu/xbox360-controller-support-added-to-usb-host-shield-2-0-library
- http://blog.tkjelectronics.dk/2012/07/xbox-360-controller-support-added-to-the-usb-host-library/
- http://blog.tkjelectronics.dk/2012/12/xbox-360-receiver-added-to-the-usb-host-library/
All the information regarding the Xbox 360 controller protocol are form these sites:
- http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller/UsbInfo
- http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller/WirelessUsbInfo
- https://github.com/Grumbel/xboxdrv/blob/stable/PROTOCOL
Xbox ONE Library
An Xbox ONE controller is supported via USB in the XBOXONE class. It is heavily based on the 360 library above. In addition to cross referencing the above, information on the protocol was found at:
- https://github.com/quantus/xbox-one-controller-protocol
- https://github.com/torvalds/linux/blob/master/drivers/input/joystick/xpad.c
- https://github.com/kylelemons/xbox/blob/master/xbox.go
Wii library
The Wii library support the Wiimote, but also the Nunchuch and Motion Plus extensions via Bluetooth. The Wii U Pro Controller and Wii Balance Board are also supported via Bluetooth.
First you have to pair with the controller, this is done automatically by the library if you create the instance like so:
WII Wii(&Btd, PAIR);
And then press 1 & 2 at once on the Wiimote or the SYNC buttons if you are using a Wii U Pro Controller or a Wii Balance Board.
After that you can simply create the instance like so:
WII Wii(&Btd);
Then just press any button on the Wiimote and it will then connect to the dongle.
Take a look at the example for more information: Wii.ino.
Also take a look at the blog post:
The Wii IR camera can also be used, but you will have to activate the code for it manually as it is quite large. Simply set ENABLE_WII_IR_CAMERA
to 1 in settings.h.
The WiiIRCamera.ino example shows how it can be used.
All the information about the Wii controllers are from these sites:
- http://wiibrew.org/wiki/Wiimote
- http://wiibrew.org/wiki/Wiimote/Extension_Controllers
- http://wiibrew.org/wiki/Wiimote/Extension_Controllers/Nunchuck
- http://wiibrew.org/wiki/Wiimote/Extension_Controllers/Wii_Motion_Plus
- http://wiibrew.org/wiki/Wii_Balance_Board
- The old library created by Tomoyuki Tanaka: https://github.com/moyuchin/WiiRemote_on_Arduino also helped a lot.
PS Buzz Library
This library implements support for the Playstation Buzz controllers via USB.
It is essentially just a wrapper around the HIDUniversal which takes care of the initializing and reading of the controllers. The PSBuzz class simply inherits this and parses the data, so it is easy for users to read the buttons and turn the big red button on the controllers on and off.
The example PSBuzz.ino shows how one can do this with just a few lines of code.
More information about the controller can be found at the following sites:
- http://www.developerfusion.com/article/84338/making-usb-c-friendly/
- https://github.com/torvalds/linux/blob/master/drivers/hid/hid-sony.c
Interface modifications
The shield is using SPI for communicating with the MAX3421E USB host controller. It uses the SCK, MISO and MOSI pins via the ICSP on your board.
Note this means that it uses pin 13, 12, 11 on an Arduino Uno, so these pins can not be used for anything else than SPI communication!
Furthermore it uses one pin as SS and one INT pin. These are by default located on pin 10 and 9 respectively. They can easily be reconfigured in case you need to use them for something else by cutting the jumper on the shield and then solder a wire from the pad to the new pin.
After that you need modify the following entry in UsbCore.h:
typedef MAX3421e<P10, P9> MAX3421E;
For instance if you have rerouted SS to pin 7 it should read:
typedef MAX3421e<P7, P9> MAX3421E;
See the "Interface modifications" section in the hardware manual for more information.
FAQ
When I plug my device into the USB connector nothing happens?
- Try to connect a external power supply to the Arduino - this solves the problem in most cases.
- You can also use a powered hub between the device and the USB Host Shield. You should then include the USB hub library:
#include <usbhub.h>
and create the instance like so:USBHub Hub1(&Usb);
.
When I connecting my PS3 controller I get a output like this:
Dualshock 3 Controller Enabled
LeftHatX: 0 LeftHatY: 0 RightHatX: 0 RightHatY: 0
LeftHatX: 0 LeftHatY: 0 RightHatX: 0 RightHatY: 0
LeftHatX: 0 LeftHatY: 0 RightHatX: 0 RightHatY: 0
LeftHatX: 0 LeftHatY: 0 RightHatX: 0 RightHatY: 0
LeftHatX: 0 LeftHatY: 0 RightHatX: 0 RightHatY: 0
- This means that your dongle does not support 2.0+EDR, so you will need another dongle. Please see the following list for tested working dongles.
When compiling I am getting the following error: "fatal error: SPI.h: No such file or directory".
- Please make sure to include the SPI library like so:
#include <SPI.h>
in your .ino file.