I have to pick this post up, as I am encountering a similar problem with my XBOX 360 controller, and tried about everything I could find so far.

I have a wired XBOX 360 controller (not an original one) connected to my Retropie (directly or through a hub, it doesn’t matter) as well as a keyboard. The led on the controller is constantly blinking, it still works on emulatorstation and on some emulators… It is available on /dev/input/js0 and I can map the buttons.

BUT: It’s not recognized by xboxdrv. Whichever method to configure it I chose, I only get a “no xbox controller connected” error message, and the led keeps blinking.

When I start xboxdrv with the “xboxdrv –device-by-id [ID]…” (from lsusb), the LED lights up, completely, not as player 1 or player 2. But I loose the possibility to enter commands in terminal (as xboxdrv is running) and cannot start emulatorstation anyway.

So, how can I get this controller to connect the way it is meant to be? (I installed retropie 1.10.1 from the SD Card image that’s available in the downloads section), since this version the controller is recognized by emulatorstation at startup, the previous version of retropie did not recognize it at all.

Here’s the dmesg output about the controller:

[    3.738107] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[    3.875527] usb 1-1.3: New USB device found, idVendor=046d, idProduct=f301
[    3.896032] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.917618] usb 1-1.3: Product: Controller
[    3.925537] usb 1-1.3: Manufacturer: Microsoft Inc.
[    3.933266] usb 1-1.3: SerialNumber: 103183E
[    4.215583] udevd[156]: starting version 175
[    6.036418] input: Generic X-Box pad as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input1
[    6.328113] usbcore: registered new interface driver xpad

And here’s the lsusb output:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 
Bus 001 Device 004: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 005: ID 046d:f301 Logitech, Inc. 

And this is what ls /dev/input gives me:

by-id
by-path
event0
event1
js0
mice

Any help is more than welcome ;)

Thanks in advance,
Floeg

[quote=10180]I have the X-Arcade DIY dual kit installed in an arcade cab.
Running lsinput returns

/dev/input/event0
   bustype : BUS_USB
   vendor  : 0xaa55
   product : 0x101
   version : 272
   name    : "XGaming X-Arcade"
   phys    : "usb-bcm2708_usb-1.3.5/input0"
   uniq    : ""
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

[/quote]

What do you get when you follow the commands given above (https://www.petrockblock.com/forums/topic/retropie-not-recognizing-xarcade-dual-tank-stick/#post-10106)?

Saw the contest, couldn’t resist submitting my Pitendo.

[img]http://i.imgur.com/6UFaTW4.jpg[/img]
Front profile. I took an old NES and, after some trial and error, managed to get paint in the exact shades of the original colors. Yeah, I’ve heard of retr0brite, but didn’t want to bother when I already had everything I needed on hand to paint it to colors that were just as perfect as the original.
The labels are custom as well, naturally.
Front buttons work as they used to, with Power doing exactly what you’d expect (including safely shutting the Pi down through terminal commands) and Reset just does a hard reset on the thing. And yes, the red LED is still the original one from the NES.

[img]http://i.imgur.com/VCQUT80.jpg[/img]
[img]http://i.imgur.com/rUDVk63.jpg[/img]
I made a simple little tray, lined with thin black foam, to serve as storage for the SD cards and remote. There is also the extension for the SD slot so I can swap things out more easily. I am currently running the Pitendo as both RetroPie and RaspBMC.
[img]http://i.imgur.com/yFjo2R2.jpg[/img]

[img]http://i.imgur.com/np0zIbG.jpg[/img]
Got annoyed with always having to plug in the USB dongle to the remote for RaspBMC, so I just went ahead and installed my own receiver. Reduces the muss and fuss.
The USB slots were put in place of the original controller ports for versatility. I just used a Dremel and some putty to resize the holes for USB.

[img]http://i.imgur.com/H17nZeK.jpg[/img]
Did the same thing for the power and network extensions in the back. The power goes to the USB hub which powers everything else, including the wireless dongle and USB memory stick for RaspBMC inside.
And yes, I made sure to put the Pi’s ports in the same places they were in for the original NES, substituting the RF adapter for network and…
[img]http://i.imgur.com/k7k0sa1.jpg[/img]
HDMI for the original RCA ports on the side.

[img]http://i.imgur.com/Huj3Y1u.jpg[/img]
Made sure to keep the old metallic labels on the bottom through simple masking while airbrushing. For some reason, the bottom of the NES has a removable panel that leads to a section of the bottom chassis that’s still blocked off. Whatever, I can still use it.
[img]http://i.imgur.com/jcTzisj.jpg[/img]
Spare USB slot for keyboard use should I have two controllers hooked up at once.

[img]http://i.imgur.com/tiheMmc.jpg[/img]
Your standard SNES-style USB controller looked a little… off… when next to the original NES’s color scheme, so screw it, might as well paint that, too.

[img]http://i.imgur.com/2HH9IyU.jpg[/img]
The finished product. Works as both RetroPie console and RaspBMC media center.

[img]http://i.imgur.com/oiQnByP.png[/img]
Complete with custom splash screen.

I have the X-Arcade DIY dual kit installed in an arcade cab.
Running lsinput returns

/dev/input/event0
   bustype : BUS_USB
   vendor  : 0xaa55
   product : 0x101
   version : 272
   name    : "XGaming X-Arcade"
   phys    : "usb-bcm2708_usb-1.3.5/input0"
   uniq    : ""
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

This is without Xarcade2jstick installed. This is on raspberry pi model b. Xarcade DualJoyStick

Additionally, when I first setup RetroPie I registered a usb keyboard and both joysticks with their keyboard commands so they could navigate the menus, so I am not sure if that will cause extra input events below.

/dev/input/event0
bustype : BUS_USB
vendor : 0xaa55
product : 0x101
version : 272
name : “XGaming X-Arcade”
phys : “usb-bcm2708_usb-1.2/input0”
uniq : “”
bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

/dev/input/event1
bustype : BUS_USB
vendor : 0xb38
product : 0x10
version : 272
name : “HID 0b38:0010”
phys : “usb-bcm2708_usb-1.3/input0”
uniq : “”
bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

/dev/input/event2
bustype : BUS_USB
vendor : 0xb38
product : 0x10
version : 272
name : “HID 0b38:0010”
phys : “usb-bcm2708_usb-1.3/input1”
uniq : “”
bits ev : EV_SYN EV_KEY EV_REL EV_ABS EV_MSC

/dev/input/event3
bustype : BUS_USB
vendor : 0x1
product : 0x1
version : 4
name : “Xarcade-to-Gamepad Device”
bits ev : EV_SYN EV_KEY EV_REL EV_ABS

/dev/input/event4
bustype : BUS_USB
vendor : 0x1
product : 0x1
version : 4
name : “Xarcade-to-Gamepad Device”
bits ev : EV_SYN EV_KEY EV_REL EV_ABS

/dev/input/event5
bustype : BUS_USB
vendor : 0x1
product : 0x1
version : 4
name : “SNES-to-Keyboard Device”
bits ev : EV_SYN EV_KEY EV_REL

I assume the usb Drive has to be fat32 formatted aswell, doesn’t it?
Can i access the filesystem on a windows computer afterwards aswell?

Sorry for the late answer @royenroy .. i was quite busy.
I would run the Adafruit-Retrogame script on boot/startup. This script then runs backgrounded and maps your custom gpio inputs as keypresses. again, i used this to build my own controller for retro games. but maybie you can map usb controller inputs aswell and then just assign them values for example left and right and navigate through xbmc like this.
EDIT: it didnt paste links for some reason:
this is the script u have to run in background:
https://github.com/adafruit/Adafruit-Retrogame
this is how you run it in background:
http://stackoverflow.com/questions/12973777/how-to-run-a-shell-script-at-startup

i hope it will work. please give me some feedback as soon as u tried it because i want to make it aswell one day.

cheers!

My retropie project:

Usb adapter 2 intellivision controller for retropie

[IMG]http://i.imgur.com/mAs39l0.jpg[/IMG]

oop http://mypiandi.blogspot.com/2012/12/retropie-sixaxis-over-bluetooth.html says L3 is button 1, otherwise it seems to agree with me.

https://www.youtube.com/watch?v=j_Jk8up_Aqw shows automated ds3 config built into retropie(just need to know where to look), he did mention something about powered usb being better for bluetooth. The controllers themselves are wireless and have battereies on board, so it would be surprising if they could fail due to insufficient power.

Sounds like a localisation issue.
In bash execute sudo raspi-config
then option 4 Internationalisation Options
Check your language and keyboard layout settings there.

In terms of the controller, if you have another controller that you could test on emulators that could be useful.

use jtest /dev/input/js0 to check that the buttons and axis are working. (ctrl+c to exit)

That will also give you the button numbers so you can then edit config files for each emulator and assign them.

Haven’t gone into using USB drives so can’t help there.

This is because it is a knock-off controller and the id is misspelt: PLAYSTATION(R)3Conteroller.

I have the same problem and I’ve been unable to figure it out yet. Using the controller via USB cable works, though.

I can’t find any details on power requirements for any arcade sticks, but I don’t think it’s an issue with a 1000ma PSU. You could use an externally powered USB hub to see if it really is a power problem.

You say it worked with the previous RetroPie image, so that leads me to think that this is a driver problem. I’ll need to do a bit more digging to try and find out whats going on.

http://elinux.org/RPi_VerifiedPeripherals
This page has a lot of information on peripherals, it also includes information on the power usage between different models of the Raspberry Pi and lists all the peripherals that are known to work.

May I suggest updating your RPi:

There are two steps to upgrading. First, run sudo apt-get update in order to synchronise the database of available software packages and the versions available. Next, run sudo apt-get upgrade which will cause any packages with newer versions available to be updated.

==== My modest RetroPie NES ====

– Bluetooth
– Wifi
– 2 side USB for other controllers

Original games fit in the gametray. Sadly I had to take out the 72pin-connector. Maybe in a future project :)

[IMG]http://i.imgur.com/DdrX7Ix.jpg[/IMG]
[IMG]http://i.imgur.com/ZUfplTP.jpg[/IMG]
[IMG]http://i.imgur.com/BJoyrz6.jpg[/IMG]

there is a way to fix this issue, it’s a little more complicated than the basic move file systems, it’s the “extended procedure” part your looking for, and this should fix yer issue, as it’s the method I use and alls cool with mine

http://www.raspberrypi.org/forums/viewtopic.php?f=29&t=44177&hilit=move+root+fs+usb+tutorial&sid=2503f9ffe9afaa2edb49aef4537a862a

Sent from my iPhone using Tapatalk

also, for future reference, if you find you require a usb hub, make sure its one of the approved powered ones!

Before you buy anything check the verified peripherals list: http://elinux.org/RPi_VerifiedPeripherals

Regarding power supplies you need at least a 1A psu, or a usb hub if you are using several peripherals at once, I recommend this one it can power the Pi as well: http://www.amazon.co.uk/gp/aw/d/B001GXR6XO/ref=mp_s_a_1_94?qid=1402940552&sr=8-94&pi=SL75

Also important is a good quality micro usb cable and SD card. Good luck :-)

I just did a install as you describe and am using the same controller. I just got this all working yesterday but started on Tuesday so I understand your woes. I did not run into the problem like you are experiencing but I’d like to try to help. I think your problem may lie with the USB bus activity itself.

A question that needs to be asked is please explain any and all USB peripherals that you have connected to the PI device. Hub (Powered or not), controller, keyboard, etc.

and run this command and report back the results.

lsusb

Maybe there is a conflict with another USB device on your bus or for some reason the bus is having power issues. If you are using a powered USB hub, check to make sure it is one that is certified for use with Raspberry Pi. Some feed power back into the bus and can cause some strange things to occur.