Lenovo NM-D562 v2.0 main EC programming help needed

[davidebeatrici]

Only the BIOS (UB2) or the EC firmware (UG10) as well?

UU137 is the USB hub's firmware. Do you see activity on it?

[m1ch43lzm]

Sorry but UG10 is GPU VBIOS for RTX 3060 PCI ID 10DE:2560

[questore]

Only the BIOS (UB2) or the EC firmware (UG10) as well?

UU137 is the USB hub's firmware. Do you see activity on it?

Unfortunatelly i cannot flash EC my programmers software will only have i2c protocol support on the next upcomimg update. (Only BIOS flashed)

[questore]

Sorry but UG10 is GPU VBIOS for RTX 3060 PCI ID 10DE:2560

This board has a 3060 Rtx

[davidebeatrici]

Sorry but UG10 is GPU VBIOS for RTX 3060 PCI ID 10DE:2560

Oops... thank you for checking. I just verified both boardview and schematics, UG10 is indeed the GPU BIOS and there is no separate chip for the EC unfortunately.

For reference, there is no activity on the CS (Chip Select) pin when the CPU doesn't initialize, despite the GPU gradually warming up.

[questore]

It is possible that i f*cked up.the hole thing.
i'm on a holliday now and wanted to check out my orders and remembered that this laptop came with it8227e-256 chip and i have replaced it with a 192 one. Could this be a problem? Or the ec firmware for 2.0 board is still 192kbyte? I have asked for the seller tomsend me the ec firmware that he flashed maybe it will give us some light on what could be the problem

[questore]

Reading a few articles and forums I think 192kb chip is OK as long as the original was 192kb firmware.

Altought Trying different bios i have encountered something very strange i have never seen until now.
When trying to program the BIOS while it is on the board it is literraly impossible.
Every pin is connected to the bios but when i try to detect the BIOS IC, the CH341 reader frozes (10/10) 1 time from every 10 i can detect the bios type but then the neoprogrammer frozes.
If i transfer the BIOS IC to a programming bord then its no problem to read/write the BIOS.
Is it possible that there is some interference on the board that messes up the bios communication and that is why it is not posting?
How could we figure this out?

[reformatt]

The board will load down the programmer, rarely does onboard dumping work with my SVOD. Sometimes you can plug in the power adapter to provide volts to the chip and it works. Depends on the model. Most of the time it's too much stuffing around and I remove it. Doesn't take long with hot air.

[davidebeatrici]

I had no problems whatsoever programming the chip on the board with an Xgecu T48.

[questore]

I had no problems whatsoever programming the chip on the board with an Xgecu T48.

I also never ever had a problem readin onboard BIOS chips with my ch341a thats why im asking.

[questore]

more digging around the board:
- I have noticed that PU2002 GPU mosfet is way to hotter then the rest (57C degree when others after turned on are 46Celsius, coil also hotter then the rest)
- BIOS SPI_CLK pin has a capacitor next to it that is missing CB21 (maybe for filtering and that is why i cannot read onboard with the clip only 1/20 times?)
I only have a boardview for REV0.4 and its optional but who knows in REV2.0 maybe its mandatory and that is why the board cannot boot because EC cannot communicate with it properly?

[davidebeatrici]

I think I have reached your situation now.

After removing the CPU (and cleaning all pads) CPU_RST_R_N and CPU_PWROK became high (1.8V) and VCORE increased from ~0.8V to ~1.1V.
I then installed a 100-000000295-40 (ES 5800H) and it gets warm as opposed to the original CPU which stayed completely cold.

Unfortunately still no POST whatsoever and no activity on SPI_CS for BIOS and VBIOS.
Interestingly:

1. When on battery it just turns off after the first attempt.
2. When connected to AC it turns on automatically and then reboots infinitely. Keeping the power button pressed results in the board turning off, but it immediately turns back on again!

Can you confirm the behavior?

[questore]

I think I have reached your situation now.

After removing the CPU (and cleaning all pads) CPU_RST_R_N and CPU_PWROK became high (1.8V) and VCORE increased from ~0.8V to ~1.1V.
I then installed a 100-000000295-40 (ES 5800H) and it gets warm as opposed to the original CPU which stayed completely cold.

Unfortunately still no POST whatsoever and no activity on SPI_CS for BIOS and VBIOS.
Interestingly:

1. When on battery it just turns off after the first attempt.
2. When connected to AC it turns on automatically and then reboots infinitely. Keeping the power button pressed results in the board turning off, but it immediately turns back on again!

Can you confirm the behavior?

When the original EC with corrupted firmware was on the board then behaviour was following:
- (with battery connected) when charger plugged in the laptop autostarted and every 20 second the laptop restarted.
durring this time if I keept long pressed the power button hold for 1 minute then nothing changed. (every power rail except CPU and GPU was u and running OK) pressing simply the power button did nothing.
- if i removed the charger plugin after this (battery still connected) then the laptop could be turned off by long pressing the power button

After replacing the EC to a preprogrammed one (cannot verify the firmware is good or bad on it) the behaviour is the following:
- (with battery connected) when charger plugged in the laptop autostarts and stays on.
durring this time if I press the power button the laptop turns off and it can be also turned on by pressing it again.

CPU_PWROK is 3.3
I have not checked SPI_CS activity but I will

[davidebeatrici]

I can confirm the behavior you noticed with the corrupt firmware, with one difference: keeping the button pressed with the charger connected actually turns it off, but it then turns back on immediately. It happens so fast that I only noticed it through the LED on the button.

Are you 100% sure CPU_PWROK is 3.3V? I usually check it through one of the pins on the debug port (JHDT1):

[davidebeatrici]

more digging around the board:
- I have noticed that PU2002 GPU mosfet is way to hotter then the rest (57C degree when others after turned on are 46Celsius, coil also hotter then the rest)
- BIOS SPI_CLK pin has a capacitor next to it that is missing CB21 (maybe for filtering and that is why i cannot read onboard with the clip only 1/20 times?)
I only have a boardview for REV0.4 and its optional but who knows in REV2.0 maybe its mandatory and that is why the board cannot boot because EC cannot communicate with it properly?

I don't have CB21 either. I also don't see it in this video.

[davidebeatrici]

I measured all UB2 (BIOS SPI) pins:

VCC: 1.8V
CS: 1.8V
CLK: 1.8V
D0: Clean square wave, like proper communication
D1: 1.8V
D2: 1.670V
D3: 1.695V

Maybe the EC is partially faulty? Or its firmware is corrupt?

I have an XZZ IT8390 programmer, I could try to reflash the firmware if I can find it somewhere.

[questore]

I measured all UB2 (BIOS SPI) pins:

VCC: 1.8V
CS: 1.8V
CLK: 1.8V
D0: Clean square wave, like proper communication
D1: 1.8V
D2: 1.670V
D3: 1.695V

Maybe the EC is partially faulty? Or its firmware is corrupt?

I have an XZZ IT8390 programmer, I could try to reflash the firmware if I can find it somewhere.

I got a firmware. Try it.

If XZZ IT8390 can program trought I2C then tell me how and i buy one

[davidebeatrici]

Thank you, I'll try and let you know!

According to both schematics and boardview the EC chip should be a IT8227E-192, but here it's a IT8227E-256, I'm assuming the firmware is still 192 KB.

[davidebeatrici]

Great news: the programmer is indeed able to read and write the chip through I2C with ITEEC_WinFlash 4.0.1.0!

1. Run the program.
2. Press on Setup and check the "Internal Clock for KBS" and "Dual-Flash" options.
3. Solder GND, SDA and SCL on the motherboard.
4. Connect the programmer to the computer that is running the program.
5. Power the motherboard.
6. Press on "Internal-Flash" at the top.
7. Press on "Read Twice to Verify" before performing a Read (optional, but recommended).

I can confirm the firmware that was installed is 192 KB (or even less), despite the internal memory being 256 KB. This means that replacing an IT8227E-256 with an IT8227E-192 should be perfectly fine.

Unfortunately I still get no POST after flashing the firmware you provided me, but I immediately noticed something weird:

1. Powering the board right after the flash results on CS activity on BIOS SPI, which initially made me believe the issue was fixed.
2. Powering the board a second time results in no CS activity on BIOS SPI anymore!

And the crazy part is that a binary diff of the dump(s) reveals several differences, I attached three of them as an archive.

[questore]

Great news: the programmer is indeed able to read and write the chip through I2C with ITEEC_WinFlash 4.0.1.0!

1. Run the program.
2. Press on Setup and check the "Internal Clock for KBS" and "Dual-Flash" options.
3. Solder GND, SDA and SCL on the motherboard.
4. Connect the programmer to the computer that is running the program.
5. Power the motherboard.
6. Press on "Internal-Flash" at the top.
7. Press on "Read Twice to Verify" before performing a Read (optional, but recommended).

I can confirm the firmware that was installed is 192 KB (or even less), despite the internal memory being 256 KB. This means that replacing an IT8227E-256 with an IT8227E-192 should be perfectly fine.

Unfortunately I still get no POST after flashing the firmware you provided me, but I immediately noticed something weird:

1. Powering the board right after the flash results on CS activity on BIOS SPI, which initially made me believe the issue was fixed.
2. Powering the board a second time results in no CS activity on BIOS SPI anymore!

And the crazy part is that a binary diff of the dump(s) reveals several differences, I attached three of them as an archive.

Thenk you for sharing. I think I order XZZ IT8390 and give it a try.
Maybe you also have a BIOS problem too.
Can you read the BIOS with a direct clip or is yours the same as mine, that i have to desolder the IC to read and write?
This one I have to figure out myself also since my board have came to me after a repair attempt and all the BIOS info were empty (not even sure this is the correct one)