TBH there is no need to reveal anything. As you mentioned... a brain and a wire will do the job.
You gave enough hints to pretty much exactly find out what you're doing. At least for me and a colleague.
Congrats and good job.
Hey, as I didn't expected an answer anytime soon (I'm very surprised and thankfull) I haven't made clear what additional Information I would need.
So some of the caps are totaly burned and (may?) need to be replaced (I may work without?) But I don't have the neccessary values. Or could I also solder bigger caps on the board?
I'm also thinking of soldering the Mosfet Dead-Bug style? Or does someone of you have another Idea? This would be my somewhat biggest challenge so far.
As because of the Mosfet is...
Yeah there is a hole in the board under the destroyed Mosfet.
There were some kind of vias within the board layers? like 3 PINS directly under the mosfet but this was another layer. The 3 (somewhat) Pins beneath the Mosfet belong to some other rail. I put UV curing stuff to fill the whole. Only the part of the mosfet from drain to 1R0 is shorted (gate seems to work) I would just like to try if I can get this fixed. If not... not soo bad, but I like the challenge. But currently I just need info about the area to continue...
I'm looking obviously for the schematic and or better boardview.
At the very least I need at least some pictures from one area but documents would be way much better.
The needed area with a high resolution picture I would need is from the back of the CPU where PU901 is located as marked in the picture. The mosfet meltet down and it was impossible the read which IC this was. I need the info.
Re: OpenBoardData Project - Making the diagnostics measurements open for repairs
Yeah I think I got it right the first time but did some (too) fast assumptions.
I understand that it's open and only just data. The CURRENT "Problem" I see is that only your tools may can use this data. - Which is totaly fine, but which CURRENTLY makes it not so much attractive to work on other boards that use a different file-format than .brd as the data might not contribute so much into the general where you constantly compare schematic with boardview (without the data).
i should have found the issue way more earlier but I did some mistakes.
I thought I messured CPU POWER GOOD but this was enable signal (missed the Testpoint) and I didn't thought about an Inductor for the VCCSA input voltage (blown). VIN was present for all chips except the VCCSA creating one. (but obviously I did not check - as i thought connection from VIN is directly without such a components in between.
hey thanks i found and fixed the problem. i was kind of distracted by the plastic layers on the board and missed one destroyed inductor. i replaced the inducter and the cap next to it (short but no visual signs) and that fixed it.
So in short this time: I have somewhat similar Issue, but I'm missing all rails: CPUCORE, SA, GFX.
For every of the 3 Chips/Rails:
DRVON is present (4,7v)
PWM is present (2v)
20v Input is present
CPUCORE_PWRGD is NOT present.
I tried another bios but it didn't work out, same behavior. After a very short rise in powerdraw it sits in at 48mA.
Do you have any recommendations? Output of every IC/rail controlled by NCP81208 is 0V. But as said,...
EC (with MEC) programming methode is very risky and involes soldering several very tiny resistors while soldering to very narrow traces (testpoints if you're lucky). So this is nothing you can do in 5min.
BTW: All this TPM and multiple location stuff that is claimed on some sites is BS.
Password in the secret area (mostly 2kb) is stored on the last "page" in the EC.
Leave a comment: