serialusb is a cheap (~$5) USB proxy intended to be used with input devices.
Input devices generally use interrupt IN and OUT endpoints, and operate at low or full speed modes.
The maximum throughput is 64 kB/s = 512kbps in each direction (1000Hz, 64-byte packets).
A USB proxy requires a system with both device and host interfaces.
Many ARM boards fulfill this requirement, but those aren't as cheap (yet).
serialusb is the combination of:
- a PC software operating the host side of the proxy
- an atmega32u4 firmware operating the device side of the proxy
The atmega32u4 and the PC are connected using a USB to UART adapter, running at a baudrate of 500kbps.
target device ↔ PC ↔ USB to UART adapter ↔ atmega32u4 ↔ target host
I'm the developper of the GIMX project, which aims at allowing people to use any input device with any gaming console. It is quite frequent that people contact me asking if GIMX could emulate a specific device. As I can't afford buying every input device, the only solution is that people provide me a USB capture of the device protocol. Commercial USB capture tools are costly, and many people can't afford buying one. serialusb aims to be a solution to this problem.
serialusb attempts to meet the following goals:
- low cost (< $10)
- low latency and low CPU footprint
- low disturbance on transfered data
- allow code parts to be used into the GIMX project
- make it easy to later add support for cheap ARM-based devices such as CHIP
These goals led to the following decisions:
- use the same hardware as the GIMX DIY USB adapter → 1.
- interrupt-driven event processing in a single-threaded process → 2.
- once the proxy is started, only use libusb's asynchronous API → 2.
- use raw descriptors (don't reconstruct descriptors) → 3.
- abstract USB device and serial port handling → 4.
- libusb >= 1.0.16
- a computer with 2 USB host ports
- an atmega32u4 board running at 5V (~$4 on ebay)
- a CP2102- or FT232RL-based USB to UART adapter with 5V tolerance (~$1 on ebay)
- the FT232RL is better as its max baudrate is 3Mbps (vs 921600bps)
Note: the CP2102 adapter shown above is mislabeled (RXD and TXD are inverted).
- Assemble the atmega32u4 board and the USB to UART adapter as explained on the GIMX DIY USB adapter wiki page.
Use the latest emu-X.Y.hex firmware from the release page.
- Connect the USB to UART adapter to the PC, and the atmega32u4 board to the target host.
- Connect the target device to the PC.
- Either install serialusb from the sources, or install the package I built for Linux Mint 17.3 64-bit.
The prebuilt packages should work with any Ubuntu 14.04 64-bit derivate.
- Once installed, run the helper script: sudo serialusb-capture.sh
- Select the USB to UART adapter, and the target device.
- The atmega32u4 firmware is based on LUFA which is a great USB stack for AVRs.
- The PC software uses libusb, which is a great library for controlling USB devices.
- Only control and interrupt endpoints are currently supported.
- Multiple configurations are not supported. Only the first configuration can be used.
- The size of any control transfer (setup + data) should not exceed 254 bytes.
This limitation does not apply to the standard descriptors, see below.
- All standard descriptors should fit into 1kB, which is the size of the RAM buffer used to store them into the atmega32u4.
This limitation applies to the following standard descriptors:
- device descriptor
- configuration descriptors
- langId0 descriptor
- strings referenced in the device and configuration descriptors
- HID report descriptors
- This is a software proxy, not a hardware one: it's usefull for reverse-engineering protocols, not for investigating hardware issues.
The USB interface of the atmega32u4 has the following constraints for non-control endpoints:
- the number of endpoints is limited to 6
- the address can be from 1 to 6
- they can't be bidirectional
Due to these contraints, serialusb may change the endpoint addresses in the configuration descriptors.
- For now the UART speed is 500kbps, which means the theorical max throughput is 50kB/s. This is not enough to reach 64kB/s.
- When using a Raspberry Pi as the proxy host, expect issues with devices using interrupt OUT endpoints.