Nintendo Adapter Box

[abunille]

@lackyluuk

Really fantastic work.
Reserve me one

[acris]

@lackyluuk
need archive of recalbox.support.sh ?
What material did you use?

modify driver udev or sdl2 in recalbox.conf ?

[lackyluuk]

@acris I will create a support file tomorrow and give you the link. The N64 controllers work perfectly in ES and in-game. Only the NES and SNES have issues (They use a different adapter than the N64 controllers. Maybe this can be a problem.

Do you mean the material of the box itself?

So far I haven't changed anything in recalbox.conf. Should I?

[acris]

do you use mayflash adapter or other ? link ?
may be you need usbhid quirk

[lackyluuk]

@acris This one for NES/SNES:
http://www.raphnet-tech.com/products/4nes4snes/index.php

And this one for N64:
http://www.raphnet-tech.com/products/dual_n64_to_usb_adapter/index.php

[acris]

I need your archive (recalbox-support.sh)
In theory I think you need usb quirks or others things udev rules.

in recalbox.conf you can tested to switch auto driver in sdl2 or udev.

## If you don't have issues with your controllers, let auto
global.inputdriver=auto

reboot you raspberry if you modifed
sorry for my english.

[lackyluuk]

@acris Thank you for your help. I will do the modifications and the support file tomorrow amd let you know

Your english is quite good, mine is not really better, haha

[lackyluuk]

@acris
I have changed global.inputdriver=auto to sdl2 and udev. Same behaviour, SNES and NES controller still only work in ES.

Here are my support.sh files:

• Only adapterbox connected to recalbox (no controllers connected to box):
  http://www52.zippyshare.com/v/VAAnNWtd/file.html

• SNES controller connected to adapterbox (Works fine in ES):
  http://www52.zippyshare.com/v/hbrvTfUM/file.html

[acris]

@lackyluuk
try this idea :

mount -o remount,rw /

edit this file : /etc/modprobe.d./usbhid.conf

add theses lines at the end :

#raphnet.net 4nes4snes v1.5
options usbhid quirks=0x289b:0x0003:0x040

save and reboot your raspberry.
Try SNES gamepad.

but I think theses adapters need patch kernel.

[lackyluuk]

@acris
Thanks for your help. Unfortunately it does not work. I saw that the 4NES4SNES adapter is already in the /usbhid.conf file.
Could it be possible that the new version v1.5 is the problem?

Is there anything else I could try to figure out?

[acris]

@lackyluuk
not it s another
your id vendor and id product are differents, you need to add my informations and try if you didn t do it.

https://github.com/recalbox/recalbox-buildroot/blob/master/board/recalbox/fsoverlay/etc/modprobe.d/usbhid.conf#L5

oh not raphnet need a kernel patch too

@Substring , @ian57

[lackyluuk]

@acris yes I have tried your info, but no luck

[acris]

i think kernel patch is missing in recalbox 4.1

[Substring]

Ni idea if it requires a patch to the kernel, i don't think so as it works fine in es, right ?

[lackyluuk]

@Substring yes, in ES it does what it should. But no response at all in a game. This only occurs with the 4NES4SNES adapter. The one for N64 works fine.
I have connected these two adapters with a small usb hub.

[Substring]

@lackyluuk ok, this is what you should do :

• test pads with evtest, i think they should work
• same goes with sdl2-jstest
  => if both of them work, then it's a retroarch problem
• out of curiosity, try to remap the pads in retroarch so that we can see if retroarch can see them afterall

Give a try to https://github.com/recalbox/recalbox-os/issues/1244#issuecomment-2981808465 because it has an updated retroarch version, i know i had to rewrite 1 patch regarding inputs, so maybe that would do.

Still, if it works in ES, it means it works with SDL and linux kernel, so that is a retroarch problem. You could eventually try some non retroarch emulators with these pads (mupen scummvm, advancemame, reicast)

[lackyluuk]

@Substring thanks a lot! I will try these points and give a feedback then.

[lackyluuk]

@Substring I have found some patches for this problem I think. They are from raphnet itself. Do you think this could work?

http://www.raphnet-tech.com/support/retropie/

(And we should let him know about recalbox, haha ;))

[Substring]

@lackyluuk 4.4 kernel doesn't seem to require these patches. Anyway please test what I suggested. The quriks are not necessary (or were they already applied when you submitted your support archive ?).

So, still, i believe it's a RA problem.

[lackyluuk]

@Substring Yes of course, I will test it tonight when I am home.
The quirks from @acris were not implemented when I created the support archives.

Yes, the quirks from the second point are only for pre-4.2 kernel. But do you think that the first point "Issue with initial values" (the 3 patches) is also covered through the updated kernel?
http://www.raphnet-tech.com/support/retropie/usbhid_iostart.diff
http://www.raphnet-tech.com/support/retropie/usbhid_start_before_connect.diff
http://www.raphnet-tech.com/support/retropie/jsdev_initial_value.diff