harkaz

@DLoa Try every seller you can find and hurry, the item will soon be unavailable everywhere. Order 2-3 of them and test them expect ~ 1/3 defective. Remember to remove the protective films from the ribbon cable and stick to the back of the keyboard. rtdparts: ordered 2, 1/2 with a defect (F6 key extremely sensitive). Seller informed it is out of stock.

If your model is P751TM (not P751TM1): https://repo.palkeo.com/clevo-mirror/P7xxTMxG/P7xxTM(G)_B10729.zip If your model is P751TM1: https://repo.palkeo.com/clevo-mirror/P7xxTMxG/P7xxTM1(G)_B10729.zip EC seems ok. There are 2 EC chips, as a matter of fact. If EC did not function at all, keyboard lights would not come up at all. You can also test the Fn+1 key combination - as long as EC is functional it should make fans spin at 100% even without a CPU! From posts online, I suspect the PCH is malfunctioning (probably after thermal damage). This is a guess. Not the most likely explanation if this happened after power failure. NOTE: The SPI flash you refer to is used for automatic flashing of the EC. However, if EC is malfunctioning, low-level programming tools have to be used (i.e. https://ioprogrammer.com/).

Always use protective cover for these keyboards. Also, the ribbon cable is very sensitive to bending.

Most likely a motherboard issue. EC appears to be working fine. Use Clevo BIOS with your i7-8086K processor from https://repo.palkeo.com/ In any case the device should be professionally tested with proper equipment (i.e. microscope, multimeter, oscilloscope) to understand the root cause.

I suppose so, I got it in 2020. The Thunderbolt firmware for P775TM1 must be signed with a special key for Clevo OEM by Intel. So firmwares for other OEMs or even Clevo laptops should not work.

You're welcome. Also, don't forget to update the EC firmware to its latest version, so that everything is running as intended. (Make sure the proper EC for your model has been chosen)

I have a TBT firmware for my own P775TM1. I have attached the files below. P750TM_TBT_FW_C1rev40_TI11204_ECN_0103.7z

I am not talking about the drivers, but the TBT firmware. Thunderbolt has its own Intel closed source firmware on an SPI flash. A tool to update this can be seperately requested from your reseller. Also, the EC firmware is not current, 1.07.16

Change Thunderbolt security level to DP++ and try again. Also, consider updating Thunderbolt firmware to the latest version (request the latest TBT firmware version for your device from your reseller).

Yes, the OEM's EC firmware should be tested then. Probably the old chip can be desoldered re-programmed and resoldered.

It might be easier to just replace the board. The ITE8587 chip (U44) must come from another P775TM1 and the firmware version should be appropriate for the BIOS version. Success is not guaranteed (resoldering may cause damage, there may be other defective components on the motherboard).

Yes, the 8MB BIOS.ROM from the stock Clevo BIOS should be flashed to U16. Reflashing EC1 is the last step. JFLASH1 most likely requires tools that are part of ITE8587 firmware sources. Note: In the past, in order to disable ME from the unlocked BIOS without a problem similar to the one you described, I have run the Clevo's meset tool first.

Try reflashing the original BIOS dump to the U16 as well, along with the second EC (U15). If nothing changes, then a reflash of the first EC should be attempted.

No, that was the wrong firmware. You need another file. Search for "2nd_EC10702.zip" Padding. Simply put, means explicitly defining the empty space in the firmware. A firmware file that is intended for Windows/UEFI shell programming may not contain this empty space, so it must be manually added before flashing with a low-level programmer. Padding is done in hex editor. If you need help with that, I can prepare and upload a padded file for you.

For BIOS 1.07.27 (or later), it is EC 1.07.16 Padding may be necessary for proper execution of the firmware machine code though (even if the programmer can properly read/write/erase). I had a similar experience with Thunderbolt firmware - padding was necessary for the firmware to be properly initialized. If you take a look at the primary EC fw with a hex editor, you will notice the padding.