-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxying usb gamecontroller with EP 0x04 / EP 0x84: failed to configure impossible endpoint with address 4 [EINVAL] #61
Comments
In a similar situation, while trying to sniff/analyze a very similar target device. Target is an original It does, just like the device mentioned above, feature an "impossible endpoint" on interface 5:
Desired outcomePS4 Console detects "mitm'd" PS4 Controller and lets you use it. Problem situationBoth approaches mentioned below do not yield usable results. Approach 1) endpoint rerouting, ends in a loop of "request descriptor". Ideas tried so farRewriting the endpoint
|
Did you ever find a good workaround for this? Also, what is this "Nintendo Switch Pro controller rewrite"? I'm asking because I'm looking to reliably capture controller data sent between video game controllers and the console... specifically the Nintendo Switch for now, but ideally I'd like a solution that works on any USB controller... |
hey @jaysonlarose, at one point we stopped using the greatfet hardware due to too many problems. for pure USB sniffing I can recommend http://openvizsla.org/ there's also another gsg hardware upcoming which might be more sufficent than greatfet: https://greatscottgadgets.com/cynthion/ |
Hi @dominikfehr ! |
BACKEND:
greatfet
Facedancer commit: e688fe6
GreatFET firmware:
Firmware version: v2021.2.1
Problem
Trying to proxy a XBox One Game-controller via FaceDancer, error received is:
greatdancer.set_up_endpoints: greatdancer: failed to configure impossible endpoint with address 4 [EINVAL]
Also tried older Facedancer repo states (end 2019)...
Any hints?
Error output
Device info (lsusb)
The text was updated successfully, but these errors were encountered: