20 pin xin mo wiring diagram set up

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