![]() I’ve verified those breakdowns to the best of my ability using publicly available information about the USB standard. Wireshark provides both the raw data from the USB packet and a breakdown of the values using its built-in analyzers. After plugging in the controller Windows will request the device and configuration descriptors, and the controller will respond in kind. To sniff the USB data I’m using Wireshark version 2.6.4 with the USBPcap plugin. ![]() I’m using a genuine Microsoft Xbox 360 wired controller, connected to my desktop which is running Windows 10. I want to understand how the information in these descriptors translates into features of the device’s behavior. By copying the Xbox controller’s descriptors onto my own device, I can convince the computer that my device is also an Xbox controller and will behave like one, and therefore use the Xbox controller’s driver to easily interface with games.īut rather than just copying and pasting the descriptor from one place to another, I want to try and understand exactly what’s going on behind the scenes. These descriptors are a hierarchy of standardized reports that describe features of the device including who makes it, what version of USB it supports, how it’s powered, and more. ![]() The first step in this process is to fetch and then break down the device’s “USB descriptors”. One of my recent projects has been trying to modify some microcontrollers to function as XInput devices, emulating an Xbox controller. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |