820-3435, no TP/KB

jpadie

New member
Hi

this board has been working fine in a chassis after a keyboard swap a month ago. a daily driver for a client.

Brought to me again as the external display/thunderbolt port stopped working. This is not yet fixed although I did find U3210 literally half of its pads and a couple of passives also pushed off their pads. I've reseated this, thunderbolt still not detected. I will replace the chip before diagnosing that further (although there was green sticky corrosion all around the shield over U2800 as well).

The problem is since putting the board back in the chassis the keyboard and trackpad have stopped functioning. Working fine when I was testing the machine yesterday. Turn it on this morning and there was nothing. I've tried three known good trackpads and three different cables (one known good and one new). All exhibit the same behaviour.

There was gunk under the keyboard connector which I have cleaned out (the latest batch of amtech flux does not seem to get cleaned away by my ultrasonic, or even by brushing with alcohol); and I've verified that the connector pins are firmly seated on the board.

is there something obvious to check on this? I've got an hour later that I've slated to have a look at it.

thanks in advance.
Justin
 

JohnB8812

New member
As far as Thunderbolt, forget that don?t even bother if U3210 is bubbling on the board that?s bad....

For the tpad, measure voltages at the trackpad connector3v42 5v 3.3 volt etc
 

2informaticos

Administrator
Staff member
Did you try to acces boot menu?
Working way is different in OSX than before login.

Check at least if all voltages are OK at J4800.
Test all corresponding resistors and post voltages for U4810.
 

jpadie

New member
2informaticos - seemingly pressing any keyboard button (even alt) pushes the machine into the recovery menu. KB and TP are not active.
removing the SSD and using an ubuntu drive loads ubuntu but no KB or TP either.

voltages on J4800 are as follows:


1 From 0 to 1.02 escalating slowly then bouncing back
2 2mv
3 0
4 3.06
5 20mv
6 0
7 0
8 0
9 3.8mv
10 3.32
11 3.3
12 0
13 3.3
14 5.1
15 3.32
16. 3.32
17 3.32
18. 3.39
19 3.42
20 3.42

the lid was propped about 2cm open. R5171 is ok and when the lid is closed the value is 3.42v

U4810 voltages (measured with case closed, board semi-out and kb/tp connected to J4800)

PMSLP_S4_L 3.32
TPAD_USB_IF_EN . 3.29
TPAD_SPI_IF_EN_CONN 0v
GND
PMSLP_S4_L 3.32
TPAD_SPI_IF_EN 9mv
TPAD_USB_IF_EN_CONN 3.32v
PP3v3_S4 3.32v

R1630 has 23mv on pin 2 and 0 on pin 1
 

jpadie

New member
with the board out of the chassis completely SMC_LID is at 3.4v and is present at R6961 but not at the connector. That's odd.

time passes...

Thanks 2informaticos - turns out that the pad under pin 1 had slightly corroded and subsequently got pushed up but the toffee remnants of the new batch of amtech flux I got delivered ten days ago. They must have changed the formula ...

case closed ...

now on to another much more interesting 820-3435.
 

jpadie

New member
Spoke too soon.
board back in chassis and no kB or tp. Board only boots into recovery.

Will leave it for the night and see whether any other pins are lifted in the morning.
 

jpadie

New member
this board is a troll ....


repaired the trackpad connector and strung a jumper from smc_lid for security. connection good now.

ultrasonic for 10 mins and then plug back in - no fan spin!

visual inspection shows that traces from U5450 to R5669 and R5667 (both no stuffed) and U5660 have burned out. These are the current sensing lines from ppbus_g3H and PPBUS_S5_HS_COMPUTING_ISNS.

no shorts on either PPBUS_G3H and PPBUS_S5_HS_COMPUTING_ISNS.

The current sense resistor R5450 has bare copper on 3 and 4. It is measuring a little higher than I'd expect to, at 0.5Ohm. But this is the same reading as R7320 gives, and that's supposed to be 750uOhm. so I think this is most likely to be a limitation of my DMM.

U5800 is visually fine.

I'm a little uncomfortable about just replacing U5450 and R5450 and string jumpers around the board (the via has burned out I think) without understanding what could have caused the burn out to start with, and investigating that. I thought at first that i may have caused the short whilst testing the kb connector, but PPBUS is nowhere near there.

All a bit confusing as this board's been working fine for a year (other than a keyboard problem which led to a direct replacement, then a mic problem and keyboard connector problem probably associated with the KB swap-out.

But, some good news --- thunderbolt was working after I reseated U3210 again!

tia
justin
 
Top