#Select button won't work on funnyplaying replacement motherboard GBA

1 messages · Page 1 of 1 (latest)

lone horizon
#

I have built a new GBA using the replacement motherboard from Funnyplaying, along with their laminated IPS screen and ribbon cable. I got plenty of modding and soldering experience, but did take a few goes to get the CPU stuck down to the new board correctly. I did lift one of the solder pads for one cpu pin on the right hand side. That trace goes to the last pin on the bottom left of the ram chip. I have run a fine jumper wire and insulated it away from the other pins with kapton tape and tested thoroughly, its all working fine. I have quadurple checked all pins on the CPU and RAM. Nothing is loose, they are all soldered down well.

Everything works great EXCEPT the select button. It won't work in games.... However it works fine for the hotkey functionality. I've manually soldered wires to the SEL, L, and R pads on the motherboard in order to bring up the OSD that way instead of using the touch sensor. It works no problem! Holding select for a second brings up the OSD menu, and you can tap select the go between the options, then hold select the close the menu. You can use the other built in combos for putting the board into sleep mode, and changing the LED brightness (all which use the SEL button) no problem!

The button just won't work in games though. For example mapping an item to select in a Pokémon game won't work. On boot the GBA holding start and select won't make the Nintendo logo disappear. But the button works for the OSD! I have desoldered the wire from the SEL pad on the motherboard just in case that was causing some sort of weird conflict. But no same issue.

I've used GBA DPAD test tool and all buttons show working except select.
I've tested continuity between the select button pad and its test point nearby and its fine. Ive also tested the trace from the select button to the CPU, thats fine too.
Just trying to think of what else to test or check... I appreciate any input or ideas! I'm starting to think the board is faulty?

glacial carbonBOT
#

Please remember to provide as much information as possible including all troubleshooting steps you have already taken. If this is a hardware issue, please provide clear in-focus images of the issue, PCB (circuit board), installation, and any soldering you have done. Help us help you, posts with insufficient information will be deleted

gritty ice
#

is the cpu pin making a good connection to the pad? is the cpu pin shorted to pins next to it? that's what I'd check next given your explanation.
your cpu seems a bit skewed/misaligned

#

also, what is going on here?

#

" I did lift one of the solder pads for one cpu pin on the right hand side. That trace goes to the last pin on the bottom left of the ram chip. I have run a fine jumper wire and insulated it away from the other pins with kapton tape and tested thoroughly, its all working fine. "
I read this, but it looks like you've bridged 2 pins on the CPU

lone horizon
#

It looks like that in the photo, but its not bridged. the pin has been lifted up slightly with kapton tape under it and then over top to isolate it. 100% its all good, probably just the angle of the photo.

yeah it does look at little missalighned at the bottom, but ive been over the pins multiple times checking to make sure they are solid and in place and not touching. can't hurt to check again though!

otherwise no ideas why select is working for combo keys but not in game? not any other traces i can check?

civic pecan
#

Without the OSD wires attached, what's the voltage on the select pad?

lone horizon
#

WIll check that when home. Whats the expected voltage?

civic pecan
#

The AGB CPU has in internal pull-up to 3.3V. I'm not sure if the IPS driver board has its own pull-up but it could rule out one of the issues by isolating the AGB CPU and seeing if it is pulling up the select input correctly.

lone horizon
#

Cheers will try that at home. Will dissconnect IPS screen and test voltage on the sel pad

lone horizon
#

@atomic loom

lone horizon
copper merlin
#

Sounds like your select pin may be floating on the cpu to me, try seeing if you have any loose pins in the bottom 10 or so, I don’t remember exactly which one it is but it’s in that area

civic pecan
#

Normally I wouldn’t suggest this, but if you’re keen on trying and don’t have any other options, bridge the select input pin and start input pin. Then check to see if the select and start inputs trigger together when pressing either button. If they both trigger simultaneously, there might be a solution

lone horizon
#

Yes seems to be a cpu issue! It was off a faulty/corroded board.

Yeah bridging them will probably work. But what would be the solution if so?

copper merlin
#

bridging them is to test the supposed issue.

#

if it doesnt trigger while bridged we can likely confirm its the pull up resistor

#

doing it this way will give the select input the voltage it needs to trigger, so if it does, we can work our way outward to find the issue

lone horizon
#

Thanks! I will test this when home. If it does trigger, that means the internal pull-up resistor isnt toast?

lone horizon
#

Ok with a bridge the select pad now gets 3.3v, but button testing only triggers start, not both 😦

#

I guess that means bad cpu on the inside?

#

I do have another cpu I harvested awhile ago. Its clean looking but there is a slight bump on the bottom of it. Like a visible lump on the bottom. Not sure if that's normal or not...

#

Hopefully you can see that circular outline.

copper merlin
#

It’s not a great sign but it might work just fine

steep spear
#

Did you use hot air? It looks like the chip popcorned

lone horizon
#

I did use hotair. Usually its not a problem, but it came from a corroded board. Looks like it might have had some mousture in it still. I've learn't now if you suspect water damage then bake the board in an over first at low temp.

lone horizon
#

The solution is to harvest another gba cpu when I come across a cheap working unit. Thanks for all the help! I have learnt a lot.

copper merlin
#

If you are getting inputs at all then it’s not really the same issue, but feel free to open another troubleshooting ticket, this one appears to have run its course

lone horizon
#

Just to follow up on this, used a different CPU and all buttons worked fine 🙂