Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
button does not work
#1
The button in the default B button position of GBA will no longer work

There is no sign of cure even after reboot or driver update. I thought it was a poor button contact, but I examined it with a tester, but it was not a poor contact.
When it was the same in the past, it was cured, but I don't know the fundamental solution.
Thank you.
Reply
#2
Hey mimi3. Is this with a Freeplay Zero or a Freeplay CM3?
Also, please see http://freeplaytech.com/troubleshooting for some tests.
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply
#3
(10-22-2019, 04:51 AM)Flavor Wrote: Hey mimi3.  Is this with a Freeplay Zero or a Freeplay CM3?
Also, please see http://freeplaytech.com/troubleshooting for some tests.

I'm sorry.

・ Free play CM3
・ Freeplay CM3 L2R2 ADC add-on board
・ Soft rubber feel X / Y button
・ Freeplay_CM3_19061802.img

Last time, when a similar symptom occurred, I tried to re-install the driver etc. via SSH and tried various things, but it improved, but it was not a fundamental solution.
How can I make the button recognized again?
Thank you
   
Reply
#4
We have to figure out why it's like this. My first guess is that the rubber itself is either poorly conductive OR it is off-center. This can be tricky to test, but you can test things outside of the shell.

First, remove the rubber pad, and use some isopropyl alcohol to clean all the button pads. If there is any debris, flux from soldering, or anything on the button contacts, it can cause this behavior.

See if that helps. If not...

If you spin the AB rubber pad 180-degrees so that the A and B are swapped, does the problem "follow" the rubber? Is the problem now with the A button?

Maybe you already tested that, but I feel like this is different than having tested with a tester. Sometimes, if you just measure conductivity with a volt meter, it can give different results than how the Raspbery Pi will react.

To test, if you are using SSH, you can run
jstest /dev/input/js0
or
evtest

If you use one of these test software tools, then you can try different button pads over the B contacts. You can even use START/SELECT rubber on the B contacts.
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply
#5
(10-22-2019, 08:59 AM)Flavor Wrote: We have to figure out why it's like this.  My first guess is that the rubber itself is either poorly conductive OR it is off-center.  This can be tricky to test, but you can test things outside of the shell.  

First, remove the rubber pad, and use some isopropyl alcohol to clean all the button pads.  If there is any debris, flux from soldering, or anything on the button contacts, it can cause this behavior.

See if that helps.  If not...

If you spin the AB rubber pad 180-degrees so that the A and B are swapped, does the problem "follow" the rubber?  Is the problem now with the A button?

Maybe you already tested that, but I feel like this is different than having tested with a tester.  Sometimes, if you just measure conductivity with a volt meter, it can give different results than how the Raspbery Pi will react.

To test, if you are using SSH, you can run
jstest /dev/input/js0
or
evtest

If you use one of these test software tools, then you can try different button pads over the B contacts.  You can even use START/SELECT rubber on the B contacts.

I tried replacing the AB rubber pad, but the result was the same and there was no reaction on the B button side.
I cleaned the button pad but there is no response.

It is a symptom that is troubled because there is a time to recover.
Reply
#6
There is another command you can try : 'gpio allreadall'
You may need to install Wiringpi package : 'sudo apt-get update' then 'sudo apt-get install wiringpi'

I don't remember what pin is used for B but it's 100% sure under 40.

If nothing happen when pressing B, you can try to remove and reinstall the compute module (battery removed), there is maybe just a false contact.
Reply
#7
I have also heard of some weird behavior being fixed by just removing the green Raspberry Pi Compute Module and then re-inserting it to make sure it's fully seated.

Also, could you post some photos of your circuit board? That could, potentially, help us figure out a problem.

Did you try the evtest or jstest?

Porcinus is right, gpio readall (or gpio allreadall) would also be a good test.

Try this.

Release all buttons
Run 'gpio allreadall' and take a screenshot, photo, copy/paste, or whatever of the output.
Hold the A button
Run 'gpio allreadall' and take a screenshot, photo, copy/paste, or whatever of the output.
Release the A button
Run 'gpio allreadall' and take a screenshot, photo, copy/paste, or whatever of the output.
Hold the B button
Run 'gpio allreadall' and take a screenshot, photo, copy/paste, or whatever of the output.
Release the B button

Let us know the output from that. Perhaps this will also help us understand the problem.

Thanks!
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply
#8
Sorry for the late report.

As I was told, I was able to recover after removing and re-installing the compute module!

Thank you very much.
Reply
#9
Great Wink
Reply
#10
Good news. Thanks for the update.
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)