harkaz

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.

Try erasing the second EC flash (U15), and flash the secondary firmware again, after padding the file (ie. adding an appropriate number of 0xFF bytes to the end of the firmware), so the file reaches the exact size of 128 KB. If this has already be done, and the BIOS has been reflashed, then the primary EC firmware must be reflashed with specialized equipment on the primary chip. If that is not cheap, the motherboard should be replaced. EDIT: Padding with 0xFF could be preferable.

That must be is the secondary EC. I see this is flashable via SPI, so you are in luck. Flash the secondary EC firmware. The primary EC may be flashable with the controller I referred to the previous link (via the keyboard connector).

I see. Version 1.07.16 is appropriate for the primary EC. There is also a secondary EC (latest firmware for secondary EC is 1.07.02). I assume you programmed the primary EC. EC must be flashed first, then the BIOS (before rebooting the system), as the BIOS can be easily reflashed. If the EC firmware is damaged, then the motherboard should be replaced, short of trying this programmer (for the primary EC chip) - not guaranteed that it will work: https://alexlaptoprepair.com/en/svod-programmer-kbc-ene-spi-i2c-mec-ite-smsc/. There are also two JFLASH connectors (JFLASH1 and JFLASH2) that may allow programming of the 2 EC chips. Interface seems to be I2C (1 clk and 1 data lane), but I am not sure about the tools needed.

Boot is halted before Intel Management Engine is completely loaded. 1. First of all, make sure processor is properly seated and cooled. Reapply thermal paste if needed. 2. Reflash BIOS from the SPI interface with a clip: First erase the BIOS flash chip (U16) via a 3.3V SPI flasher (this clears NV items as well), then flash the full 8,192 KiB* image. May I recommend the P775TM1-G BIOS v 1.07.27, even if it is not latest. Ensure that there are no errors. Voltage supply of the flasher must be stable and configured at the appropriate level (3.3V), do NOT operate from battery. 3. If options 1 and 2 fail, then the entire motherboard needs to be tested to find if a semiconductor has gone faulty. The CPU can be removed and tested on another device. In practice, because JTAG is disabled on commercial devices, a new motherboard may be needed.