8bitdo m30 2.4g not work.

[xdemax]

hello! i have a fairly popular controller '8bitdo m30 2.4g' available, when connected via usb it works in xbox compatible mode (x-input), unfortunately mist does not detect it.

[gyurco]

Need firmware logs to see what happens. BTW, the XBOX driver is just partial, as I don't have too much XBOX compatible controllers to test.

[xdemax]

ok! i understand and upload log file. log.txt

[gyurco]

Is it from one session? As I see a reset around the middle, and then it boots with a different set of devices (I see an RTC at the second run, but not at the first). Also at the first run:

port 1 reset complete!
usb_configure(parent=1 port=1 lowspeed=0)
using free entry at 1
Setting addr 2
usb_set_addr(new=2)
USB vendor ID: 045E, product ID: 028E
wLangId: 0409
trying to init class 0
usb_hub_init()
not a hub!
 -> not accepted :-(
trying to init class 1
HID: usb_hid_init(2)
HID: unsupported descriptor type 65 size 6
HID: no hid interfaces found
 -> not accepted :-(
trying to init class 2
 -> accepted :-)

It found the XBOX controller. After a while, port 1 resets:

resetting port 1
status change on port 1, 0x100103
Status of port 1:
 connected
 enabled
 powered
Changes on port 1:
 reset
 port 1 reset complete!
usb_configure(parent=1 port=1 lowspeed=0)
using free entry at 3
Setting addr 4
usb_set_addr(new=4)
USB vendor ID: 057E, product ID: 2009

Thus it resets to 057E:2009 as a joystick.

On the second run, the XBOX controller doesn't show up, only the 057E:2009 device. Is this device shows up on the USB status screen?

[xdemax]

that's right, the first turn on with a connected gamepad - 'joy 1 -' appears in the menu, and after rebooting the button disappears.

[gyurco]

And did you reboot intentionally? Or it just happened by itself?

[xdemax]

forced by button.

[xdemax]

vid/pid -- 045E/028E.

[gyurco]

Yeah, that's the XBOX Controller VID/PID. Seems this controller also tries to be 'intelligent' and detects the host via its USB initialization pattern, and it switches to HID mode with 057E:2009 VID/PID after it detects something else (not Windows I guess). And why doesn't work in HID mode? That's another question... Unfortunately it'll be very hard to debug this without having the actual device to experiment with.

[xdemax]

according to the manual -- 'On USB connection, it works with Switch, Windows 10 and Raspberry Pi', 057E:2009 corresponds to joy-con nintendo switch.

[gyurco]

The HID parsing aborts:

HIDP: PHYSICAL_MAXIMUM(0)
HIDP: unexpected main item 0

There must be some unusual data in the report descriptor or an there's an issue with the report descriptor parser. I'll investigate. Maybe it would be easier to make it work in HID mode than find out how to stay in XBOX mode.

[xdemax]

unfortunately this guy doesn't know how to be hid. took another log, with the keyboard, mouse and gamepad connected. log2.txt

[gyurco]

There are 3 data dumps from 3 HID initialization attempts, and all of them differ. Strange device. Maybe under-powered? The report descriptor dumps in the first log.txt are definitely invalid (and the two dumps even not the same), as I tried to load it into the official HID Descriptor Tool: https://www.usb.org/document-library/hid-descriptor-tool

[gyurco]

The first HID descriptor dump in log.txt from offset 0f to 3f is all zero, in the second dump this area is almost all zero. Usually this data should be hardcoded in the firmware, thus it should be identical in all queries. Looks like a hardware problem for me. Maybe you can try a different power supply? Or a powered HUB?

[xdemax]

this log is obtained by connecting the gamepad after loading the core log3.txt .

[gyurco]

Another version of the report descriptor :) But at least it's fully parsed, unfortunately at the end: "HIDP: - unusable report 130" I wonder what would be the correct descriptor. Can you dump it somehow? I found this tool for Windows: https://github.com/todbot/win-hid-dump But maybe it'll be in XBOX mode if you connect it to a Windows machine.

If you have a Linux machine, you can use usbhid-dump: https://www.systutorials.com/docs/linux/man/8-usbhid-dump/

[xdemax]

yep, on windows is work perfectly, but dump with error:

0000:0000: Microsoft - HID Button over Interrupt Driver PATH:\?\hid#acpi0011#3&30be55&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} DESCRIPTOR: 05 01 09 0C A1 01 85 01 09 0C A1 02 09 C6 15 00 25 01 35 00 45 01 65 00 55 00 75 01 95 01 81 02 95 07 81 03 09 CB 95 01 B1 02 95 07 B1 03 C1 00 C1 00

[gyurco]

Are you sure this was the 8bitdo device? 0000:0000: Microsoft - HID Button over Interrupt Driver

Isn't it possible to update the firmware of this gamepad? Looks very strangely behaving.

[xdemax]

yes. when launching the application with a connected gamepad, the error 'unhandled exception -- failed to get info.'

[xdemax]

I don't think it's worth wasting time on this.

[jotego]

This is a controller I use too. I have also noticed this on/off behavior. It looks from the issue log that this cannot be fixed, at least not easily.

[gyurco]

The latest firmware has some fixes related to this by UzixLS. Maybe you can try it.

[jotego]

Thank you for the headsup. I upgraded the firmware and tested it but it made no difference :-(