20 pin xin mo wiring diagram set up

Graboid

I wired mine up as per below, works fine with the usb quirks fix

Greg

For now I edited source files manually and added new lines.
Krenel is now compiling, waiting it to end.

My usb controller is 40 pin.

stuntstein

@Greg Not sure why the patch didn't work. It is difficult to tell if some typo error from the above print because the forum reformat the text.
Anyway, I hope that your kernel compiled successfully and your controller now fully working.

stuntstein

@Graboid The original Xin Mo controller works fine because the fix for joystick up&left is already included in the linux kernel.
The Xin Mo and the clones have same Vendor ID 0x16c0.
The original Xin Mo has Product ID 0x05e1.
Mine and Subz clone has PID 0x75e1.
Gregs clone has PID 0x05e0.

I submitted a patch to Linux Kernel to fix PID 0x75e1. We might need another patch to permanently fix 0x05e0.

Greg

@stuntstein I still trying to compile the krenel but at the end it cannot create img. file, During compiling I have errors about xinmo.
Now i`m trying third time. Fresh install retropie with rpi3.

Greg

Problem with the patch is that there are different lines in source files which it modifies. I had to manually add new lines in 3 files (commented in the patch).

Greg

Steps with compiling :

Enter console raspberry
enter home folder
sudo git clone --depth=1 https://github.com/raspberrypi/linux
sudo apt-get install bc
enter cloned linux dir
copy changed files over original
7)in linux dir enter commands:
KERNEL=kernel7
make bcm2709_defconfig
8)make -j4 zImage modules dtbs
takes time ( 1h)

sudo make modules_install
sudo cp arch/arm/boot/dts/.dtb /boot/
sudo cp arch/arm/boot/dts/overlays/.dtb* /boot/overlays/
sudo cp arch/arm/boot/dts/overlays/README /boot/overlays/
sudo scripts/mkknlimg arch/arm/boot/zImage /boot/$KERNEL.img

problem cannot find zImage file

Maybe I do something wrong.
Any suggestions ?

stuntstein

In step 8 try to build only zImage:
make -j4 zImage
Then you should see the error message.
When fixed then do the complete make instruction.

Greg

@stuntstein Ok after make -j4 zImage the image is done. What next ?
make -j4 zImage modules dtbs ?
or separate make modules dtbs ?

stuntstein

You can do either. Make system will not rebuild zImage unless you change the source files.
But try
make -j4 modules dtbs

Greg

@stuntstein Thanks i just ran make -j4 modules, next i will run make -j4 dtbs. It takes time so I have to wait and see if there is any error.

Greg

I can confirm that everything is working ok after making changes to kernel. 3H Dual Arcade 2 Players are now working properly ( every directions).
If someone need help please read whole post. There are informations how to compile new kernel.
1.Before compiling kernel i had to su apt-get upgrade and apt-update.
Soon i will post comloete guide how to get it working.
How about post this change to retropie team to support this patch in future releases ?

stuntstein

I have written a guide here:
https://retropie.org.uk/forum/topic/7832/fix-up-left-joystick-direction-for-tht-2p-arcade-controller-with-device-id-0x75e1

It is not a patch that the retropie team has to maintain, but rather a patch for the linux kernel.
I have submitted the patch to support the THT controller. I can add the new changes to another patch but I don't know if Linux org will keep accepting changes to kernel because of an unknown USB clone is coming out now and then.

pajaroloco

@Greg Hello:Please, when you have the guide please publish as soon as possible; i have the same controller (3H) and don´t go left/up joystick, and im noob with linux, errors, thank you

subvers

Hi Guys,

I have the same problem with the 3H Dual Arcade 2 Players, did you found any solution to solve this?

robthedude81

I am still having this issue with the 75e0 one

Daz409

I'm sorry to bump this thread but I'm struggling to get my 20 pin board working - specifically UP & LEFT on the joysticks - does anyone have an idea how to fix this?????

stuntstein

could you do
lsusb
and paste the list here? Need to see if Vendor and Product ID is the same as we have already found.

I still have a task to make a new patch to the linux kernel to fix the issue for the other device that have the issue.

Currently I have this list of devices that also need the fix:
Vendor ID 0x16c0.
Product ID 0x05e1, 0x05e0