Working on an A2991 board that had an overvoltage on 1v2_s2 which killed several components on that rail, including UG400, UG260, UG090, and UJ120. I restored power and the board seemed to work well; however, when I DFU restored it to install MacOS Tahoe, the board fails DFU with error 1 (no trackpad connected).
I found pin 9 of JT400 (IPD_SYS_AWAKE_CONN) completely missing (0v) and not shorted (.340 diode). This is a tiny circuit, and I found all inputs/vcc for UT320 to be present. Just to see how the board would act, I ran a wire from pin 1 to pin 3 just to see if having the 3.3v at the trackpad connector would allow DFU to complete, but it did not. I am missing IPD_SYS_AWAKE and it comes directly from the SOC. Is there any other signal that is in-sequence with IPD_SYS_AWAKE that I can piggy-back to UT320? Again, the unit worked perfectly (for a few weeks, even) before DFU-restore; the trackpad itself even works fine (during DFU), it just fails restore.
Is there anything I can check or try in this case, or has the SOC been damaged by the ripple on 1v2_s2 from the failed capacitor? The capacitor failed enough to kill components near it on the 1v2_s2 rail, so I am worried it reached the CPU/SOC.
Any input or thoughts appreciated!
I found pin 9 of JT400 (IPD_SYS_AWAKE_CONN) completely missing (0v) and not shorted (.340 diode). This is a tiny circuit, and I found all inputs/vcc for UT320 to be present. Just to see how the board would act, I ran a wire from pin 1 to pin 3 just to see if having the 3.3v at the trackpad connector would allow DFU to complete, but it did not. I am missing IPD_SYS_AWAKE and it comes directly from the SOC. Is there any other signal that is in-sequence with IPD_SYS_AWAKE that I can piggy-back to UT320? Again, the unit worked perfectly (for a few weeks, even) before DFU-restore; the trackpad itself even works fine (during DFU), it just fails restore.
Is there anything I can check or try in this case, or has the SOC been damaged by the ripple on 1v2_s2 from the failed capacitor? The capacitor failed enough to kill components near it on the 1v2_s2 rail, so I am worried it reached the CPU/SOC.
Any input or thoughts appreciated!
Last edited: