Incompatibilites with 8-bitdo m30 controllers / adapters and USB hub board v2.1 when other devices are plugged in

[redsteakraw]

I have found that my bluetooth m30 in wired mode simply isn't working on the hub board. It was working fine on a external hub but not on the hub board. It tries to connect and the LED on the hub board blinks and doesn't stay solid. I have tried ever input mode, x-input, d-input, MacOS and Nintendo switch and the same problem is with all of them. I have tried different wires and still no difference. I also found a user on reddit with a similar problem but with the usb wireless dongle. I am using the stock power supply and a y shaped barrel plug adapter connected to the stock power supply with no heavy power draw devices. The hub works fine on my daemonbite arcade controller with working coin mech. It also works fine with my Logitech k400 usb universal wireless adapter.

Here is another user with problems. They seem to be using a beefier power supply with no luck.
https://www.reddit.com/r/fpgagaming/comments/jex098/mister_usb_21_addon_not_working_with_8bitdo/.

[sorgelig]

Try different USB port on hub. If you use other USB devices try unplug them. de10-nano has picky USB hub HW/driver. So sometimes need to find a working combinations of occupied USB ports.

[redsteakraw]

Okay so I plugged it in with just my keyboard and controller in the rear right port and it worked and was able to assign buttons, but then I plugged in my daemonbite controller and it also worked. I did a hard reboot and then then it stopped working. Apparently it won't work unless the daemonbite is plugged in after reboot. Then I unplugged the keyboard adapter and they both work on reboot. Okay I think the problem is the keyboard adapter, I finally found a combo that works with the keyboard in the rear right port daemonbite in the rear left port and m30 on the front center port. Thank you

[redsteakraw]

Okay so on a full power down and up it seems that the issue that is conflicting is the logitech universal adapter paired with a M30 controller on the hub 2.1

The M30 works with the daemonbit as long as it is seperated by more than one port. The main issue that is enduring is if the logitech adapter is plugged in at all on boot up.

[redsteakraw]

I have a second , Logitech k400 keyboard and tested it with the setup and it had the same results. Can anyone else replicate this?

[redsteakraw]

I wanted to rule out wireless interference so I plugged the logitech adapter into an USB extension cable so it wasn't directly on the board, there is no effect it still seems to mess with the M30.

[redsteakraw]

They all will work if the adapter is plugged in after a full reboot and all the controllers are working and if it is in the last USB port.

[sorgelig]

i have connected following devices:

opened 0( 0): /dev/input/event0 (046d:4024) 0 "usb-ffb40000.usb-1.2:1/4024-19-a2-39-0a" "Logitech K400"
opened 1( 0): /dev/input/mouse0 (046d:4024) 0 "usb-ffb40000.usb-1.2:1/4024-19-a2-39-0a" "Logitech K400"
opened 2( 2): /dev/input/event6 (1997:2535) 0 "usb-ffb40000.usb-1.6/input1" "  mini keyboard Consumer Control"
opened 3( 2): /dev/input/event5 (1997:2535) 0 "usb-ffb40000.usb-1.6/input1" "  mini keyboard System Control"
opened 4( 2): /dev/input/event4 (1997:2535) 0 "usb-ffb40000.usb-1.6/input1" "  mini keyboard Mouse"
opened 5( 2): /dev/input/mouse1 (1997:2535) 0 "usb-ffb40000.usb-1.6/input1" "  mini keyboard Consumer Control"
opened 6( 6): /dev/input/event3 (1997:2535) 0 "usb-ffb40000.usb-1.6/input0" "  mini keyboard"
opened 7( 7): /dev/input/event2 (2341:8037) 0 "usb-ffb40000.usb-1.7/input2/Picade control" "Picade control"
opened 8( 8): /dev/input/event1 (045e:028e) 0 "usb-ffb40000.usb-1.3/input0" "Microsoft X-Box 360 pad"

Microsoft X-Box 360 pad is M30 in wired X-Input mode. Picade control is DIY Arduino Micro adapter for stick and buttons.

All this works fine after hard reboot. Note Hub v2.1 may have VBUS control (turns off the USB power upon reboot - which helps some devices to reset correctly) or not - depending on specific manufacturer. I use full version with VBUS control.

[redsteakraw]

It seems the M30 is incompatible with pretty much any device, it only works reliably when it is the only device plugged in on boot and everything else is plugged in after. So I plugged everything and grepped the /var/log/messages for input and here is the result

inputlog.txt

[redsteakraw]

I do have a board with VBUS control with a diode included and PMIC that is rated for 2.1A

[birdybro]

Does this problem persist with the M30 no matter which mode it is ran in? For instance:

X+Start = Windows input mode
Y+Start = Switch input mode
B+Start = Android input mode
A+Start = macOS input mode

These options don't only make a difference for bluetooth, they also impact how it behaves when running wired. Potentially you could be running it in a mode different than Windows input mode, and this could be messing things up. i have successfully used my M30 in alternate modes with the MiSTer but it doesn't detect it or operate quite the same sometimes. Been awhile since I tried it so can't remember, but hope this helps figure out what the issue is.

[zerohimself]

I just had a similar issue with a retro receiver, as well as a wired sn30.

The issue with the retro receiver was resolved by updating the firmware. I will give an update after I have updated the sn30's FW. At the moment, it is presenting similar behavior. It freezes & glitches other devices on the hub when used with any other USB devices present.

[edrozenberg]

I've got many USB issues, some with 8BitDo controllers, and other issues as well. Currently using a MiSTerAddons complete system (recently purchased) with latest analog board + usb hub in the metal case.

Using 8BitDo 2.4G (not bluetooth) USB wireless M30 and wireless TG16 controllers. After booting the MiSTer, frequently have to unplug/replug the 2.4G USB dongles, reboot the system, repower the system to get one or the other controller to be recognized. Sometimes when I try to use the M30 controller the selection bar on the main menu starts to move upward quickly on auto-repeat and I can only fix it by repowering the system.

Only good news is once a controller is properly recognized and responding, it works fine from then on as long as I keep the system turned on. The controllers are not broken in any way. The issue appears to be something about the way the USB hub handshakes with the plugged in USB devices, or the handshake between the usb hub and the de10. No idea really though.

A separate issue, maybe related not sure - frequently after doing a "soft" reboot (for ex. reboot menu option after a normal MiSTer update script run finishes), the USB lightpipes on the ports on the USB hub do not light up (i.e. USB ports are not active). Even with no controllers connected (though I do have wifi dongles connnected). Have to switch the system off/on to get the usb ports to light up normally.

The persistent USB issues unfortunately mean the system is spending a lot of time in the closet, and I'm using other game systems instead for now. Hopefully the issue can eventually be resolved by some software changes, because if it's some kind of unsolvable issue with mister hardware components we'll all be sad.

[sorgelig]

A separate issue, maybe related not sure - frequently after doing a "soft" reboot (for ex. reboot menu option after a normal MiSTer update script run finishes), the USB lightpipes on the ports on the USB hub do not light up (i.e. USB ports are not active). Even with no controllers connected (though I do have wifi dongles connnected). Have to switch the system off/on to get the usb ports to light up normally.

Probably USB HUB board is not properly assembled or some options were skipped or hub trying to get the power from micro-USB plug which is wrong. I'm also using USB hub v2.1 with all features soldered in. Never had problem with total hub shutdown upon reboot. This is not the thing which can be solved by software. It's some HW problem.

[rsn8887]

I would say use an external USB HUB. I use Amazonbasics 10 port powered USB2 hub, never any issues. I use many devices simultaneously: 8bitdo M30 wireless dongle together with Logitech wireless USB keyboard and mouse, BT dongle, Wifi stick, Mojo retroadapter USB controller adapters, Sony DS4 USB dongle etc etc no problems ever. If it works with an external hub, not only you can enjoy your MiSTer again, but you will have also verified that the problem is indeed your HUB board hardware.

[birdybro]

Probably USB HUB board is not properly assembled or some options were skipped or hub trying to get the power from micro-USB plug which is wrong. I'm also using USB hub v2.1 with all features soldered in. Never had problem with total hub shutdown upon reboot. This is not the thing which can be solved by software. It's some HW problem.

Is P2 on the board an optional feature that might impact this? I've noticed that I ordered one board from misterfpga.co.uk a year ago and another from misteraddons.com a few months ago, and they differed in that misteraddons had P2 headers soldered on, and misterfpga.co.uk did not. Would this make the difference? Also, R1a in the diagram is labeled as DNI, but seems to be related to P2. If I were to install the P2 headers on my usb hub, would I require the 47k resistor on R1a?

[sorgelig]

It's more important how you power your USB hub. Where it gets 5V from?

[birdybro]

EDIT: Oh I see you were replying to them above.

This is the USB hub they use, it's the 2.0 version of the same one I have that i use for my PC which is 3.0, it's a self-powered hub.

[zerohimself]

P2 is the jumper that allows it to pull power via the OTG port. If you do not populate it, it will pull power from the DC connector instead. I have found no difference in devices functioning when powered from either.

I've noticed lots of issues with 8bitdo's, as well as some of the cheap aliexpress wifi dongles lately. They used to work without any issue, however lately, they seem intermittent at best. I've test both cases, powered by OTG, and powered by the DC connector.

The wifi dongles, only work upon initial boot, but fail to function properly after restarting the MiSTer. (They only work from a cold boot state). While the 8bitdo receivers will often have(or cause) issues when used with keyboard adapters, or other controllers. In some cases, a FW update to the 8bitdo receiver will fix the issue.

On Wed, Jan 13, 2021 at 10:53 AM birdybro notifications@github.com wrote:

I personally only have had issues with delay on a Razer turret keyboard+mouse (small form factor setup for use with HTPCs) if I have the 8bitdo plugged in.

Previously I powered it with the switch+splitter from misteraddons and the 5v 20w 4a mean well power supply (GST25A05-P1J) as I had the analog I/O board. Now I power it with the jumper cable from de10-nano to usb hub, and the Digital I/O board gets one plug to power it (from the same Mean Well PSU).

The razer turret + 8bitdo setup results in massive delays on keyboard inputs, and sometimes phantom inputs on the controller, so I just don't use them at the same time.

I assumed my issue was signal interference, but I was just asking whether or not P2 being present or not was helpful for OP's issue.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MiSTer-devel/Main_MiSTer/issues/297#issuecomment-759539315, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKNK2YSTQAPLFG576ER2XDSZW6XZANCNFSM4S6KTDMQ .

[sorgelig]

To help re-initialize the devices i've added VBUS control chip, so upon reset the power on USB ports get disabled for short time.

[edrozenberg]

@sorgelig Regarding my various USB issues, I'm using a pre-assembled MisterAddons system purchased a few weeks ago so I assume well assembled with the latest board revisions. Haven't taken it apart yet to look inside (can do if there's something important to check) but looks like this from the outside:

Regarding the reboot issue: most of the time after reboot the system comes up normally, but once in a while it doesn't and this is what I saw on the usb console when this happened - so maybe the reboot issue is not a USB hub issue, but some other system issue:

Saving random seed... done.
Stopping logging: OK
umount: /media/fat: target is busy.
Sent SIGKILL to all processes
Requesting system reboot
[   33.764467] reboot: Restarting system

U-Boot SPL 2017.03+ (May 23 2018 - 19:09:48)
Trying to boot from MMC1

U-Boot SPL 2017.03+ (May 23 2018 - 19:09:48)
Trying to boot from MMC1

U-Boot SPL 2017.03+ (May 23 2018 - 19:09:48)
Trying to boot from MMC1
...
...

I see your note To help re-initialize the devices i've added VBUS control chip but I don't know what that means (I'm new here ...). I assume that means new boards will soon have some hardware tweak.

[edrozenberg]

Update - there is actually an issue with USB hub being disabled after reboot sometimes. Just happened now. Gists below: first one normal boot, second one boot with USB hub ports disabled. When the boot happened with USB hub disabled, multiple reboot commands did not fix the issue, multiple RESET button presses did not fix the issue. Only fix was power button OFF then ON.

https://gist.github.com/edrozenberg/3b09d04b9e2eb82aa94c7de9fe943e77

So I've now run into 2 separate reboot issues: 1) Failure to reboot with endless Trying to boot from MMC1 messages 2) Reboot with USB hub ports not enabled (not lit up)

[birdybro]

@edrozenberg make sure to check with misteraddons support, he's usually experienced in some of these issues that can be seen from time to time.

Are you just plugging in two wifi adaptors for the picture for the fun of it or to show which adaptors you use overall? Two wifi adaptors and a bluetooth adapter actively being used at the same time would pull a lot of current to the board for sure. 802.11ac routers already have 802.11a/b/g/n typically built into them either on 5ghz or 2.4ghz so no need for more than one running at the same time on the same device.

[edrozenberg]

@birdybro thanks will check with misteraddons. I was plugging in 2 wifi adapters because the 'n' is well supported and the 'AC' is faster but with a driver that is a bit of a work in progress. Pretty sure I had the various issues even with only 1 of them plugged in but will try running with only 1 for some time.

[sorgelig]

repeated Trying to boot from MMC1 is very low level error. Probably either contacts of SD card are dirty or SD card better to replace.

[edrozenberg]

repeated Trying to boot from MMC1 is very low level error. Probably either contacts of SD card are dirty or SD card better to replace.

Thanks, everything is brand new with zero dirt and a new Sandisk Extreme Pro card but I guess random cosmic radiation or pesky electrons do ocasionally behave in inconvenient ways. Only saw this issue once so far that I'm aware of...

[sorgelig]

Original de10-nano power supply sometimes isn't good.

[sorgelig]

There is one thing you may don't understand: after HW reset, 8bitdo receiver break the current wireless connection. Then depending on gamepad it may quickly re-connect or not. Some gamepads like PS4/PS5 don't notice the wireless is disconnected and need several seconds to notice it and then shutdown. Then by pressing PS button it get connected again. XBoxOne gamepad quickly reconnects.

[M0b13us]

I have also run into this issue after running the update script on my unit that hasn't been updated in serveral months. Mister had been running fine with my SN30 Pro since I originally setup the Mister a couple years ago.

The controller worked just fine to navigate the menus to run the update script however after the reboot at the end of the update my 8bitdo SN20 Pro no longer works.

It connects to the 8bitdo Orange Brick dongle just fine as normal but no button presses are accepted

Attempting to remap the controller no button presses are accepted.

Linux seems to be having trouble with it. Looking at /var/log/messages shows it just keeps trying and disconnecting over and over.

/root# tail /var/log/messages -n 100 May 9 18:51:29 MiSTer user.warn kernel: [ 641.360514] nintendo 0003:057E:2009.00BD: Failed to read right stick cal, using dflts; e=-71 May 9 18:51:29 MiSTer user.err kernel: [ 641.377524] nintendo 0003:057E:2009.00BD: failed reading SPI flash; ret=-71 May 9 18:51:29 MiSTer user.info kernel: [ 641.384511] nintendo 0003:057E:2009.00BD: using factory cal for IMU May 9 18:51:29 MiSTer user.err kernel: [ 641.401511] nintendo 0003:057E:2009.00BD: failed reading SPI flash; ret=-71 May 9 18:51:29 MiSTer user.warn kernel: [ 641.408499] nintendo 0003:057E:2009.00BD: Failed to read IMU cal, using defaults; ret=-71 May 9 18:51:29 MiSTer user.warn kernel: [ 641.408506] nintendo 0003:057E:2009.00BD: Unable to read IMU calibration data May 9 18:51:29 MiSTer user.err kernel: [ 641.425516] nintendo 0003:057E:2009.00BD: Failed to set report mode; ret=-71 May 9 18:51:29 MiSTer user.err kernel: [ 641.433182] nintendo 0003:057E:2009.00BD: probe - fail = -71 May 9 18:51:29 MiSTer user.warn kernel: [ 641.438930] nintendo: probe of 0003:057E:2009.00BD failed with error -71 May 9 18:51:29 MiSTer user.info kernel: [ 641.463777] usb 1-1.1: USB disconnect, device number 68 May 9 18:51:29 MiSTer user.info kernel: [ 641.653554] usb 1-1.1: new full-speed USB device number 69 using dwc2 May 9 18:51:29 MiSTer user.info kernel: [ 641.743641] usb 1-1.1: New USB device found, idVendor=057e, idProduct=2009, bcdDevice= 2.00 May 9 18:51:29 MiSTer user.info kernel: [ 641.743652] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 9 18:51:29 MiSTer user.info kernel: [ 641.743659] usb 1-1.1: Product: Pro Controller May 9 18:51:29 MiSTer user.info kernel: [ 641.743666] usb 1-1.1: Manufacturer: Nintendo Co., Ltd. May 9 18:51:29 MiSTer user.info kernel: [ 641.743672] usb 1-1.1: SerialNumber: 000000000001 May 9 18:51:29 MiSTer user.info kernel: [ 641.749384] HID usage: 0x00010004, original interval: 4 May 9 18:51:29 MiSTer user.info kernel: [ 641.749393] JS: endpoint->bInterval=4, interval=1 May 9 18:51:29 MiSTer user.info kernel: [ 641.749398] HID usage: 0x00010004, applied interval: 1 May 9 18:51:29 MiSTer user.info kernel: [ 641.749403] HID usage: 0x00010004, original interval: 8 May 9 18:51:29 MiSTer user.info kernel: [ 641.749407] JS: endpoint->bInterval=8, interval=1 May 9 18:51:29 MiSTer user.info kernel: [ 641.749411] HID usage: 0x00010004, applied interval: 1 May 9 18:51:29 MiSTer user.info kernel: [ 641.750174] nintendo 0003:057E:2009.00BE: hidraw2: USB HID v81.11 Joystick [Nintendo Co., Ltd. Pro Controller] on usb-ffb40000.usb-1.1/input0 May 9 18:51:34 MiSTer user.err kernel: [ 646.786498] nintendo 0003:057E:2009.00BE: failed reading SPI flash; ret=-71 May 9 18:51:34 MiSTer user.info kernel: [ 646.793494] nintendo 0003:057E:2009.00BE: using factory cal for left stick May 9 18:51:34 MiSTer user.err kernel: [ 646.810758] nintendo 0003:057E:2009.00BE: failed reading SPI flash; ret=-71 May 9 18:51:34 MiSTer user.info kernel: [ 646.817744] nintendo 0003:057E:2009.00BE: using factory cal for right stick May 9 18:51:34 MiSTer user.err kernel: [ 646.834753] nintendo 0003:057E:2009.00BE: failed reading SPI flash; ret=-71 May 9 18:51:34 MiSTer user.warn kernel: [ 646.841739] nintendo 0003:057E:2009.00BE: Failed to read left stick cal, using dflts; e=-71 May 9 18:51:34 MiSTer user.err kernel: [ 646.858752] nintendo 0003:057E:2009.00BE: failed reading SPI flash; ret=-71 May 9 18:51:34 MiSTer user.warn kernel: [ 646.865737] nintendo 0003:057E:2009.00BE: Failed to read right stick cal, using dflts; e=-71 May 9 18:51:34 MiSTer user.err kernel: [ 646.882752] nintendo 0003:057E:2009.00BE: failed reading SPI flash; ret=-71 May 9 18:51:34 MiSTer user.info kernel: [ 646.889740] nintendo 0003:057E:2009.00BE: using factory cal for IMU May 9 18:51:34 MiSTer user.err kernel: [ 646.906751] nintendo 0003:057E:2009.00BE: failed reading SPI flash; ret=-71 May 9 18:51:34 MiSTer user.warn kernel: [ 646.913737] nintendo 0003:057E:2009.00BE: Failed to read IMU cal, using defaults; ret=-71 May 9 18:51:34 MiSTer user.warn kernel: [ 646.913744] nintendo 0003:057E:2009.00BE: Unable to read IMU calibration data May 9 18:51:34 MiSTer user.err kernel: [ 646.930752] nintendo 0003:057E:2009.00BE: Failed to set report mode; ret=-71 May 9 18:51:34 MiSTer user.err kernel: [ 646.938667] nintendo 0003:057E:2009.00BE: probe - fail = -71 May 9 18:51:34 MiSTer user.warn kernel: [ 646.944420] nintendo: probe of 0003:057E:2009.00BE failed with error -71 May 9 18:51:34 MiSTer user.info kernel: [ 647.095778] usb 1-1.1: USB disconnect, device number 69 May 9 18:51:35 MiSTer user.info kernel: [ 647.286440] usb 1-1.1: new full-speed USB device number 70 using dwc2 May 9 18:51:35 MiSTer user.info kernel: [ 647.376512] usb 1-1.1: New USB device found, idVendor=057e, idProduct=2009, bcdDevice= 2.00 May 9 18:51:35 MiSTer user.info kernel: [ 647.376526] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 9 18:51:35 MiSTer user.info kernel: [ 647.376533] usb 1-1.1: Product: Pro Controller May 9 18:51:35 MiSTer user.info kernel: [ 647.376539] usb 1-1.1: Manufacturer: Nintendo Co., Ltd. May 9 18:51:35 MiSTer user.info kernel: [ 647.376546] usb 1-1.1: SerialNumber: 000000000001 May 9 18:51:35 MiSTer user.info kernel: [ 647.382420] HID usage: 0x00010004, original interval: 4 May 9 18:51:35 MiSTer user.info kernel: [ 647.382474] JS: endpoint->bInterval=4, interval=1 May 9 18:51:35 MiSTer user.info kernel: [ 647.382479] HID usage: 0x00010004, applied interval: 1 May 9 18:51:35 MiSTer user.info kernel: [ 647.382486] HID usage: 0x00010004, original interval: 8 May 9 18:51:35 MiSTer user.info kernel: [ 647.382490] JS: endpoint->bInterval=8, interval=1 May 9 18:51:35 MiSTer user.info kernel: [ 647.382495] HID usage: 0x00010004, applied interval: 1 May 9 18:51:35 MiSTer user.info kernel: [ 647.382753] nintendo 0003:057E:2009.00BF: hidraw2: USB HID v81.11 Joystick [Nintendo Co., Ltd. Pro Controller] on usb-ffb40000.usb-1.1/input0 May 9 18:51:36 MiSTer user.err kernel: [ 648.499510] nintendo 0003:057E:2009.00BF: Failed to set baudrate; ret=-71 May 9 18:51:36 MiSTer user.err kernel: [ 648.507551] nintendo 0003:057E:2009.00BF: probe - fail = -71 May 9 18:51:36 MiSTer user.warn kernel: [ 648.513290] nintendo: probe of 0003:057E:2009.00BF failed with error -71 May 9 18:51:36 MiSTer user.info kernel: [ 648.631786] usb 1-1.1: USB disconnect, device number 70 May 9 18:51:36 MiSTer user.info kernel: [ 648.818685] usb 1-1.1: new full-speed USB device number 71 using dwc2 May 9 18:51:36 MiSTer user.info kernel: [ 648.908882] usb 1-1.1: New USB device found, idVendor=057e, idProduct=2009, bcdDevice= 2.00 May 9 18:51:36 MiSTer user.info kernel: [ 648.908894] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 9 18:51:36 MiSTer user.info kernel: [ 648.908901] usb 1-1.1: Product: Pro Controller May 9 18:51:36 MiSTer user.info kernel: [ 648.908908] usb 1-1.1: Manufacturer: Nintendo Co., Ltd. May 9 18:51:36 MiSTer user.info kernel: [ 648.908914] usb 1-1.1: SerialNumber: 000000000001 May 9 18:51:36 MiSTer user.info kernel: [ 648.914433] HID usage: 0x00010004, original interval: 4 May 9 18:51:36 MiSTer user.info kernel: [ 648.914442] JS: endpoint->bInterval=4, interval=1 May 9 18:51:36 MiSTer user.info kernel: [ 648.914447] HID usage: 0x00010004, applied interval: 1 May 9 18:51:36 MiSTer user.info kernel: [ 648.914464] HID usage: 0x00010004, original interval: 8 May 9 18:51:36 MiSTer user.info kernel: [ 648.914468] JS: endpoint->bInterval=8, interval=1 May 9 18:51:36 MiSTer user.info kernel: [ 648.914472] HID usage: 0x00010004, applied interval: 1 May 9 18:51:36 MiSTer user.info kernel: [ 648.914791] nintendo 0003:057E:2009.00C0: hidraw2: USB HID v81.11 Joystick [Nintendo Co., Ltd. Pro Controller] on usb-ffb40000.usb-1.1/input0 May 9 18:51:41 MiSTer user.err kernel: [ 653.951518] nintendo 0003:057E:2009.00C0: failed reading SPI flash; ret=-71 May 9 18:51:41 MiSTer user.info kernel: [ 653.958515] nintendo 0003:057E:2009.00C0: using factory cal for left stick May 9 18:51:41 MiSTer user.err kernel: [ 653.975519] nintendo 0003:057E:2009.00C0: failed reading SPI flash; ret=-71 May 9 18:51:41 MiSTer user.info kernel: [ 653.982504] nintendo 0003:057E:2009.00C0: using factory cal for right stick May 9 18:51:41 MiSTer user.err kernel: [ 653.999519] nintendo 0003:057E:2009.00C0: failed reading SPI flash; ret=-71 May 9 18:51:41 MiSTer user.warn kernel: [ 654.006507] nintendo 0003:057E:2009.00C0: Failed to read left stick cal, using dflts; e=-71 May 9 18:51:41 MiSTer user.err kernel: [ 654.023517] nintendo 0003:057E:2009.00C0: failed reading SPI flash; ret=-71 May 9 18:51:41 MiSTer user.warn kernel: [ 654.030502] nintendo 0003:057E:2009.00C0: Failed to read right stick cal, using dflts; e=-71 May 9 18:51:41 MiSTer user.err kernel: [ 654.047526] nintendo 0003:057E:2009.00C0: failed reading SPI flash; ret=-71 May 9 18:51:41 MiSTer user.info kernel: [ 654.054514] nintendo 0003:057E:2009.00C0: using factory cal for IMU May 9 18:51:41 MiSTer user.err kernel: [ 654.071524] nintendo 0003:057E:2009.00C0: failed reading SPI flash; ret=-71 May 9 18:51:41 MiSTer user.warn kernel: [ 654.078567] nintendo 0003:057E:2009.00C0: Failed to read IMU cal, using defaults; ret=-71 May 9 18:51:41 MiSTer user.warn kernel: [ 654.078582] nintendo 0003:057E:2009.00C0: Unable to read IMU calibration data May 9 18:51:42 MiSTer user.err kernel: [ 654.095521] nintendo 0003:057E:2009.00C0: Failed to set report mode; ret=-71 May 9 18:51:42 MiSTer user.err kernel: [ 654.103189] nintendo 0003:057E:2009.00C0: probe - fail = -71 May 9 18:51:42 MiSTer user.warn kernel: [ 654.108945] nintendo: probe of 0003:057E:2009.00C0 failed with error -71 May 9 18:51:42 MiSTer user.info kernel: [ 654.118405] usb 1-1.1: USB disconnect, device number 71 May 9 18:51:42 MiSTer user.info kernel: [ 654.308613] usb 1-1.1: new full-speed USB device number 72 using dwc2 May 9 18:51:42 MiSTer user.info kernel: [ 654.398764] usb 1-1.1: New USB device found, idVendor=057e, idProduct=2009, bcdDevice= 2.00 May 9 18:51:42 MiSTer user.info kernel: [ 654.398776] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 9 18:51:42 MiSTer user.info kernel: [ 654.398783] usb 1-1.1: Product: Pro Controller May 9 18:51:42 MiSTer user.info kernel: [ 654.398790] usb 1-1.1: Manufacturer: Nintendo Co., Ltd. May 9 18:51:42 MiSTer user.info kernel: [ 654.398796] usb 1-1.1: SerialNumber: 000000000001 May 9 18:51:42 MiSTer user.info kernel: [ 654.404661] HID usage: 0x00010004, original interval: 4 May 9 18:51:42 MiSTer user.info kernel: [ 654.404671] JS: endpoint->bInterval=4, interval=1 May 9 18:51:42 MiSTer user.info kernel: [ 654.404676] HID usage: 0x00010004, applied interval: 1 May 9 18:51:42 MiSTer user.info kernel: [ 654.404681] HID usage: 0x00010004, original interval: 8 May 9 18:51:42 MiSTer user.info kernel: [ 654.404685] JS: endpoint->bInterval=8, interval=1 May 9 18:51:42 MiSTer user.info kernel: [ 654.404689] HID usage: 0x00010004, applied interval: 1 May 9 18:51:42 MiSTer user.info kernel: [ 654.404953] nintendo 0003:057E:2009.00C1: hidraw2: USB HID v81.11 Joystick [Nintendo Co., Ltd. Pro Controller] on usb-ffb40000.usb-1.1/input0

[M0b13us]

Update Downgrading the Linux OS to release_20200618 but keeping latest Mister Cores restores the controller functionality so something has gone wacky in the newer linux Kernels.

Creating an update.ini file for the update.sh scrip and setting UPDATE_LINUX="false" is a temporary workaround for now.

[sorgelig]

Do you have any other input devices plugged in? it seems your receiver is in Switch mode (nintendo name all over) which never worked right with MiSTer. I suggest to use X-Input or D-Input mode for better compatibility.

[sorgelig]

I have both SN30 Pro and brown brick receiver. I was trying to reproduce your case but coudn't. I can't switch to mode with 057E:2009 VID:PD. Did you update your receiver to latest firmware?

[M0b13us]

It didn't matter which input mode was used they would all fail.

I did some more testing this afternoon at your suggestion. Updating the firmware on the Orange brick receiver resolved the issue and the controller and MIster now work with the latest Linux build.

Receiver Brick firmware was at 1.16 and was upgraded to v2.0 to resolve the issue. Thanks for the input.

[sorgelig]

great!