820-00239 Critical update issue

leshuq

New member
Hello everyone.
Got some liquid spill on KB and on the housing, but none of it actually made it to the board.

Well, where to start...
Board slow boots, then asks for critical update.
That's all, I suppose.

What's done:
- Checked for corrosion everywhere, none found
- Checked PMU output voltages on main 4(?) Coils, seems fine to me, never checked the LDOs though.
- Checked diode readings from anywhere the T1 goes (touchid connector, touchbar connectors, lcd connector)
SPI/I2C lines seems fine, voltages seem to be fine too.
- Booted OS from safe mode, there is Apple Mobile Device (Recovery Mode) as expected, seems than it can't get out of recovery.
- Checked SPI data lines with oscope between T1 and its SPI, there is some life.
- Being out of options, swapped T1, it's SPI and SEP from donor board. Made no difference.
- Swapped touchbar to a "new" one. Never saw it working.
- Swapped T1's PMU from donor, again, no difference.
- Checked i2c/SPI pull-ups everywhere I can find, seems fine.
- Booted bare board with only usbc connector, external monitor and nothing else. Same thing here. Tries to update and then rolls back to same screen asking to update.

To make it clear: this is not the network issue, not the OS issue probably, as I tried wiping SSD clean and doing a clean install of Monterey, tried booting from external Catalina, tried different Wi-Fi network, nah.

So, 2 questions:
1) can it update T1 succesfully if there is nothing connected to it? (Touchbar, touchid, nfc, lcd, camera, als) what's the minimal setup? Anyone ever experimented?
2) what am I missing here? Maybe there is something that needs to be checked that I've missed?

Thx
 
Last edited:

2informaticos

Administrator
Staff member
First of all, welcome to the forum!

Tried all mentioned by dukefawks here?

Check DFR_TOUCH_LID and DFR_TOUCH_RESET_L levels.
 

leshuq

New member
First of all, welcome to the forum!
Thx
Tried all mentioned by dukefawks here?
Yep. Tried all combinations.
Check DFR_TOUCH_LID and DFR_TOUCH_RESET_L levels.
DFR_TOUCH_LID = 0.15V,
/Retried measuring, lid = 0v when board is only connected to power, booted./
SMC_LID = 3,3V
reset is 0V.
/Again, remeasured when board is laying flat on the table, reset= 1,8V, that's weird/

That is without touchbar connected at all.
_______________________________________________
Got diode readings under berkellium from actually working board, compared with mine, the same
 
Last edited:

2informaticos

Administrator
Staff member
SMC_LID must be high and DFR_TOUCH_LID low (0V), when lid is open.
DFR_TOUCH_RESET_L must be high.
Also be sure PMU_TO_SOC_RESET_L is high.
 

leshuq

New member
SMC_LID must be high and DFR_TOUCH_LID low (0V), when lid is open.
DFR_TOUCH_RESET_L must be high.
Also be sure PMU_TO_SOC_RESET_L is high.
Well, you're right;
DFR_TOUCH_RESET seemed to be the issue.
Got it booted up on the table and flashed with TB connected.
______
It refused to flash-boot T1 without TB attached
When flashed successfully, board can boot without TB.
______
Thx y'all
 

Attachments

  • IMG_20211201_234023_673.jpg
    IMG_20211201_234023_673.jpg
    243.4 KB · Views: 0

2informaticos

Administrator
Staff member
What was the reason of incorrect DFR_TOUCH_RESET_L?

BTW, write directly into reply box, instead of clicking Reply button.
No real reason to quote an entire post, visible few centimeters above.
We try to maintain forum aesthetic, thanks.
 

leshuq

New member
Well, that's surely something to dig more into, I guess.
I don't exactly figured out the real reason by now.
When board was in the housing, it was below 1,8.
Then when I took the board out again for some additional measurings, I checked it again, and it was there. You know the rest of the story.

For now I suspect pullup resistor to 1,8. There are two options that come to mind right now, either it was shorted to gnd cause it was touching some shielding below or maybe it was some solder crack or other defect, but i triple checked under microscope, and it looks fine to me.

Anyway, it's getting late, I'll continue to work on this tomorrow. Maybe I find the real reason.
 

2informaticos

Administrator
Staff member
Liquid spilled on keyboard may affects SMC_LID; check it w/ and w/ trackpad connected.
Also check HALL_SENSOR_LEFT/RIGHT, both connected; the pull-up resistor is near the sensors, not on MLB.
 
Top