8bitdo controller with 3.8+ update

django1980

@jloc0 Downgrading the firmware of the 8bitdo controller worked for me in getting it to work again. I'm currently using 1.68 for both my FC30 Pro and NES30 Pro.

jloc0

@django1980 interesting. I'll have to do this when I'm back home later. Not quite sure why it would unexpectedly stop working on 1.69, but I'll give 1.68 a try and report back on any findings.

firepowr

I'm having issues with my new SNES30 on my Pi 3. I can pair it but when I try to map the buttons only the D pad works.

When the SNES30 is connected via USB cable it works fine. I'm using the latest firmware for that gamepad.

I haven't tested it on any previous builds. I have a Pi2 which I setup retropi last year. And I just recently got the Pi 3 and set it up from scratch. I got the SNES30 gamepad hoping to go wireless, but so far I can't seem to get it working. Any help would be appreciated.

BuZz

I got a snes30 in the last few days. I haven't tried it yet, but when I do I will be able to advise.

BuZz

Mine works fine - I have not checked the firmware version or updated it so unsure what version it is on currently - I powered it up with Start+Right shoulder, used the Bluetooth configuration from RetroPie-Setup to pair it, and then ssh'd in and added a file

/etc/udev/rules.d/99-8bitdo.rules

with the contents

SUBSYSTEM=="input", ATTRS{name}=="8Bitdo SFC30 GamePad Joystick", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"

8Bitdo SFC30 GamePad Joystick is the name the device reported when pairing after powering up with Start+Right shoulder - (eg the output of dmesg | grep "BLUETOOTH" | sed "s/.*BLUETOOTH.*\[\(.*\)\].*/\1/"

Thak

Hi,
I use the Last firmware too with my both nes30 and nes30pro
The trick you used @BuZz is the same explained in the wiki by @Floob and didn't work for me :/...
I'll try to downgrade the firmware this we and see what happen

BuZz

I have pushed an update to the Bluetooth pairing utility in RetroPie-Setup to be able to add the udev rule automatically (once you have paired the device). Should simplify setup for people with 8bitdo and other controllers that require a udev rule.

jloc0

Well after applying the bluetooth update and the udev rule (which I had already made my own, and didn't fix the problem) I downgraded the controller to firmware 1.68, rebooted the pi and reconnected the controller. Only this time when loading a game my buttons continued to work!

There must be some change in the 8bitdo 1.69+ firmware which breaks compatibility. From their changelog I'm assuming it has something to do with the OSX compatibility changes, though one can never be to sure with closed source software such as theirs.

theroamer

I guess 3.8 didn't fix the 8bitdo 1.69 issue. If you want to run 1.69 just pair it with power + R1, set it up with emulation station, then edit /opt/retropie/configs/all/retroarch-joypads/8BitdoNES30ProJoystick.cfg
to the following and everything should work fine.

input_device = "8Bitdo NES30 Pro Joystick"
input_driver = "udev"
input_up_btn = "h0up"
input_down_btn = "h0down"
input_left_btn = "h0left"
input_right_btn = "h0right"
input_a_btn = "0"
input_b_btn = "1"
input_x_btn = "3"
input_y_btn = "4"
input_l_btn = "6"
input_r_btn = "7"
input_l2_btn = "8"
input_r2_btn = "9"
input_l3_btn = "13"
input_r3_btn = "14"
input_select_btn = "10"
input_start_btn = "11"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_enable_hotkey_btn = "10"
input_state_slot_increase_btn = "h0right"
input_exit_emulator_btn = "11"
input_state_slot_decrease_btn = "h0left"
input_save_state_btn = "9"
input_load_state_btn = "8"
input_reset_btn = "14"
input_menu_toggle_btn = "13"

Patrick2209

I updated to 3.8 and my 8bitdo SNES30 controllers which I set up and used the UDEV file as shown above still worked. I, however, purchased an NES Pro pad and cannot get it to pair. I downgraded the firmware on it to 1.68, but it still does the same thing. When I try and pair it, it is detected and identified correctly. When I select it, and it asks for the security mode and I select EITHER one, it crashes the system and displays the text pictured below. Any ideas?

screen shot