xbox 360 wireless usb adapter

Try the attached one. It loads without errors on my Mini, bua as for teh life of me I can't find my xbox 360 wireless USB adapter I haven't been able to test it.

Cool! Thanks for reporting back. Nice that it works.
I'm surprised you need to force loading with '-f'. I compiled it with the Modules.symvers from the Mini and on mine (fw 1_2_0-shield) the busybox insmod loads it OK.


Regarding the LEDs, the C64Mini kernel doesn't have LED driver support enabled. I tried an xpad.ko with CONFIG_JOYSTICK_XPAD_FF=y and CONFIG_JOYSTICK_XPAD_LEDS=y but no /sys/class/leds/xpad0/... appeared. Maybe I can provide LED support as a module too.

I suppose this should work with most Xbox controller's, as well as other gamepads as some use the xpad.ko driver?

I'v added led_core.ko and led_class.ko that are missing in the Mini's kernel an have compiled and tried various xpad sources and enabled CONFIG_JOYSTICK_XPAD_LEDS. Loading led_core.ko and led_class.ko allows xpad.ko to creat the /sys/class/leds/xpad0 structure, but echoing a number to brightness has no effect on the blinking 'X' on my 360 controller. The resulting modules are attached.

Maybe you have better luck. Otherwise a piece of tape will have to do 

The controller kind of works, at least a fire button and the start button. But using the standard SDL gamecontrollerdb entry does not make it work, so there's some mapping to do.



xpad-modules.zip (465.91 KB)

Here's an updated version with full LED support. Works fine with powering the pad on and off, but if you remove the USB receiver the Mini will hang.

Sorry for asking, but how would I permanently put this into my Mini? I understand that on FEL boot I can load these with commandline Tools. But how would I install them to the Mini?


(Ideally there will be another script for the USB Scripting Method from jj0 so I could just install via USB and FEL boot once).


Thank you!

IT WORKS!

Would like some different mapping though, but I can handle this myself. I am thinking of writing a script that does these steps automatically (including copying an updated controllerdb).

Just a short update on this because I finally updated my Mini from 1.2 to 1.3.x. Of course 1.3.x has a new controller.db and of course it is totally rubbish if you use Xbox 360 controllers. They are now detected but they do not use a proper mapping, so buttons are just insane.

You can take the controller.db from my year-old-posting and apply it (via jj0s excellent file manager!) if you want to use Xbox 360 controllers on your Mini (or Maxi). See article above this one or in quotes here on what I did.

Thanks to all people providing the tools to make all this possible!

The issue is that the Maxi uses a different SoC/CPU (Allwinner H3) compared to the Mini (Allwinner A20). This means they also use different Linux kernels so the kernel modules for the Mini are not compatible with the Maxi. They would need to be recompiled specifically with the SDK/kernel source and kernel configuration of the Maxi, but we do not have that SDK/kernel source nor kernel configuration.

I've had some hit and miss results compiling modules using an Allwinner SDK for the Orange Pi or Nano Pi, some modules work but some (notably USB2Ethernet adapter support) just crash. I'll try to compile the x360 modules and see if they work.

I have a wired Xbox 360 controller (I sometimes use it on my PC but most of the time I use my PS4 controller cause it has a soundcard built in to it so I can use headphones with it, and I can get it to emulate a Xbox 360 Controller) and added it to PCU gamecontollerdb.txt cause it never had it but I never tested yet, have to try it today, BTW how are you making the GUID mapping strings, I use SDL2 Gamepad Tool on Windows...?

My Xbox wired don't work... LEDs are just flashing.

When I connect it, it says.. and has no GUID number comes up like the other controllers I connect to THEC64 Maxi, its the number that come up like `0003/.../005` so you use that to make the GUID from.

[  112.130442] usb 3-1.2: new full-speed USB device number 6 using sunxi-ehci


so I am guessing this needs a driver in the kernal to work too, it properly works the same as the wireless version of the Xbox 360 controller but has the USB part all built into the controller.

The Xbox Controller GUID Mapping sting is added to the gamecontollerdb.txt file cause that what's included in the SDL database file, don't mean the controller will work with THEC64 at all cause it might need a driver in its kernal to work(We need Source Code C64OSS v1.4.2 now and it has to be complete, RGL.. ), so the wired version of the 360 controller is not supported too.

Well it only works on Windows cause it has a driver for the controller to work, One time I had a problem with it working on the PC cause windows couldn't load the driver for it so the controller stopped working. I had to restart the PC then it worked again, some times that happens if I plug it in after the PC has started so if I go to use it now I make sure it plugged in first before starting my PC.

The XBOX 360 Controller can make itself Player 1 or player 2, that what the LEDs are for, you can use 4 XBOX 360 controllers on the 360 or PC, it has 4 LEDs on the controller and they change if you have another controller plugged in so if I have my PS4 Controller(I can get it to emulate a XBOX 360 Controller using Input Mapper(DS4Windows or use Steam) plugged in thats Player 1 so Xbox 360 controller becomes play 2 so the top right LED comes on saying its player 2.

I have the same problem with my arcade Logic3 Tri Format Arcade stick that has 3 connectors on it, USB, Xbox Original and PS One(might be PS2) connectors, it works fine on the PC but nothing on THEC64 Maxi, it has a GUID on windows but not on Linux so missing the driver(in the kernal) it needs to work with it.

This is a video about the arcade stick...

If you make a script for this I can add it to PCUAE and PCUME if you like..? and only run it if it sees its a THEC64 Mini PCU is running on so it will not run it on THEC64 Maxi or THE VIC 20...?

And when it does come available for THEC64 Maxi/THE VIC 20 I will be able to get it to run 2 different scripts depending on what machine your running PCU on so it will only run one script ...

Oh just seen the other post by jj0, ok thats is a start-up script, I can do it so PCUAE copies all the files over to the firmware for you so you will not need to do anything at all, and it will only do it once then reboot.

It will be in a folder in Options called `XPAD_ XBox_360_Contoller_for_Mini` and it will check if its running on the Mini if its running on a maxi it will not copy the XPad files over so it will only work on THEC64 Mini, and when THEC64 Maxi version comes out I will do the same.. wow, never ever was me making scripts like this months ago..

I've compiled the drivers but there are still some symbols missing so still trying to figure it out.