Zitat von lfb6 im Beitrag #5685

---

Zitat von Kolich im Beitrag #5684

---

i have this problem when i building image for FWupdate.
can you provide to me this image for flashing my notebook? :)
may be problem in win11 which i use ;)

---

I don't think that's the reason. And if you do really think the ME tools work differently on Win11 you shouldn't use FWUpdLcL either until it's confirmed working properly on Win11

And I'm sorry, that was just proof of concept that things do indeed work as expected- I deleted the files already again.

---

Zitat von lfb6 im Beitrag #5685

---

Zitat von Kolich im Beitrag #5684

---

i have this problem when i building image for FWupdate.
can you provide to me this image for flashing my notebook? :)
may be problem in win11 which i use ;)

---

I don't think that's the reason. And if you do really think the ME tools work differently on Win11 you shouldn't use FWUpdLcL either until it's confirmed working properly on Win11

And I'm sorry, that was just proof of concept that things do indeed work as expected- I deleted the files already again.

---

i think i found problem, you used another samples, i attached screenshot, in the manual said i need just use Tiger H chipset without others.....

Zitat von lfb6 im Beitrag #5683

---

@Kolich If I follow Intel (Converged Security) Management Engine: Drivers, Firmware and Tools => How to use FWUpdate Tool at CSME v13+: precisely word for word I don't get any error messages when creating an update image.

I assume your error lies in choosing the correct chipset platform here or you make an error when loading the CSME firmware?

Zitat von plutomaniac im Beitrag #1

---

......
How to use FWUpdate Tool at CSME v13+:

At CSME 13 or newer, FWUpdate tool requires CSME firmware which has been combined/stitched with its equivalent IUP firmware (i.e. PMC, PCHC, PHY) via Flash Image Tool (FIT). To proceed, you must first learn your system's Chipset Family/Codename (i.e. ICP, LKF, JSP, CMP, TGP, EHL), Chipset Platform (i.e. H, LP, N, V), Chipset Type (i.e. Consumer, Corporate, Slim, Value, Atom, Server) and Chipset Stepping/Revision (i.e. A, B, C, D).

• Download the latest Intel CSME System Tools from Section C2 as well as ME Analyzer tool.
• From Intel CSME System Tools, run MEInfo command line tool and under "Intel(R) ME code versions" > "FW Version" you will find your system's Chipset Platform as well as Chipset Type (i.e. LP Consumer). Under "PCH Information" > "PCH Step Data" you will find your system's Chipset Stepping/Revision which starts with a letter (i.e. Ax, Bx, Cx). Alternatively, drag and drop your system's SPI/BIOS image (Flash Descriptor + Engine + BIOS) at ME Analyzer tool and find "SKU" field which shows your system's Chipset Type and Chipset Platform (i.e. Consumer LP). Next, find "Chipset Stepping" field which lists one or more supported Chipset Steppings in the form of letters (i.e. A, B, C).
• Based on your system's Chipset Family/Codename, Chipset Platform, Chipset Type and Chipset Stepping/Revision, consult the CSME/IUP Table above and choose the correct CSME, PMC, PCHC and/or PHY firmware from Sections B1-B4.
• Input the chosen CSME firmware into ME Analyzer tool and make sure that "FWUpdate Support" is not reported as "Impossible".
• From Intel CSME System Tools, go to Flash Image Tool folder and make sure that only two (2) files exist: fit.exe and vsccommn.bin. Otherwise, delete the rest.
• Run Flash Image Tool (FIT) and adjust the Chipset Platform drop-down menu at the top based on your system's Chipset Platform (i.e. H series, LP series, N series, V series, Lakefield, Jasper Lake, Elkhart Lake). At CSME 14.1, adjust to "H series (With RocketLake)". For the purposes of FWUpdate, there is no need to further adjust the actual Chipset SKU on the right.
• Load or drag and drop the chosen CSME firmware image anywhere at FIT and go to "FW Update Image Build" tab on the left.
• If your chosen CSME firmware requires PMC IUP, input its firmware at "PMC Image" > "PMC Binary File" field.
• If your chosen CSME firmware requires PCHC IUP, input its firmware at "PCHC Image" > "PCH Configuration File" field.
• If your chosen CSME firmware requires PHY IUP, input its firmware at "PHY Image" > "PHY Binary File" field.
• Click the green "Build Image For FWUpdate" button at the top right and a "FWUpdate.bin" file will be generated.
• Input "FWUpdate.bin" file into ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes".
• Use FWUpdate tool to flash the "FWUpdate.bin" image.

......

---

╔═══════════════════════════════════════════╗
║ ME Analyzer v1.253.0 r262 ║
╚═══════════════════════════════════════════╝

╔════════════════════════════════════════════╗
║ FWUpdate_2.bin (1/1) ║
╟─────────────────────────────┬──────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼──────────────╢
║ Version │ 15.0.30.1902 ║
╟─────────────────────────────┼──────────────╢
║ Release │ Production ║
╟─────────────────────────────┼──────────────╢
║ Type │ Extracted ║
╟─────────────────────────────┼──────────────╢
║ SKU │ Consumer H ║
╟─────────────────────────────┼──────────────╢
║ Chipset │ TGP/EBG-H A ║
╟─────────────────────────────┼──────────────╢
║ TCB Security Version Number │ 1 ║
╟─────────────────────────────┼──────────────╢
║ ARB Security Version Number │ 3 ║
╟─────────────────────────────┼──────────────╢
║ Version Control Number │ 11 ║
╟─────────────────────────────┼──────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼──────────────╢
║ OEM Configuration │ No ║
╟─────────────────────────────┼──────────────╢
║ FWUpdate Support │ Yes ║
╟─────────────────────────────┼──────────────╢
║ Date │ 2021-07-08 ║
╟─────────────────────────────┼──────────────╢
║ File System State │ Unconfigured ║
╟─────────────────────────────┼──────────────╢
║ Size │ 0x32C000 ║
╟─────────────────────────────┼──────────────╢
║ Flash Image Tool │ 15.0.35.1932 ║
╟─────────────────────────────┼──────────────╢
║ Latest │ No ║
╚═════════════════════════════╧══════════════╝
╔═════════════════════════════════════════════╗
║ Power Management Controller ║
╟─────────────────────────────┬───────────────╢
║ Family │ PMC ║
╟─────────────────────────────┼───────────────╢
║ Version │ 150.2.10.1019 ║
╟─────────────────────────────┼───────────────╢
║ Release │ Production ║
╟─────────────────────────────┼───────────────╢
║ Type │ Independent ║
╟─────────────────────────────┼───────────────╢
║ Chipset SKU │ H ║
╟─────────────────────────────┼───────────────╢
║ Chipset Stepping │ B ║
╟─────────────────────────────┼───────────────╢
║ TCB Security Version Number │ 0 ║
╟─────────────────────────────┼───────────────╢
║ ARB Security Version Number │ 0 ║
╟─────────────────────────────┼───────────────╢
║ Version Control Number │ 0 ║
╟─────────────────────────────┼───────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼───────────────╢
║ Date │ 2021-05-20 ║
╟─────────────────────────────┼───────────────╢
║ Size │ 0x26000 ║
╟─────────────────────────────┼───────────────╢
║ Manifest Extension Utility │ 15.0.10.1302 ║
╟─────────────────────────────┼───────────────╢
║ Chipset Support │ TGP ║
╟─────────────────────────────┼───────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧═══════════════╝
╔════════════════════════════════════════════╗
║ Platform Controller Hub Configuration ║
╟─────────────────────────────┬──────────────╢
║ Family │ PCHC ║
╟─────────────────────────────┼──────────────╢
║ Version │ 15.0.0.1021 ║
╟─────────────────────────────┼──────────────╢
║ Release │ Production ║
╟─────────────────────────────┼──────────────╢
║ Type │ Independent ║
╟─────────────────────────────┼──────────────╢
║ TCB Security Version Number │ 0 ║
╟─────────────────────────────┼──────────────╢
║ ARB Security Version Number │ 0 ║
╟─────────────────────────────┼──────────────╢
║ Version Control Number │ 0 ║
╟─────────────────────────────┼──────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼──────────────╢
║ Date │ 2021-04-28 ║
╟─────────────────────────────┼──────────────╢
║ Size │ 0x1000 ║
╟─────────────────────────────┼──────────────╢
║ Manifest Extension Utility │ 15.0.30.1716 ║
╟─────────────────────────────┼──────────────╢
║ Chipset Support │ TGP ║
╟─────────────────────────────┼──────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧══════════════╝
╔══════════════════════════════════════════════╗
║ USB Type C Physical ║
╟─────────────────────────────┬────────────────╢
║ Family │ PHY ║
╟─────────────────────────────┼────────────────╢
║ Version │ 12.14.214.2014 ║
╟─────────────────────────────┼────────────────╢
║ Release │ Production ║
╟─────────────────────────────┼────────────────╢
║ Type │ Independent ║
╟─────────────────────────────┼────────────────╢
║ SKU │ P ║
╟─────────────────────────────┼────────────────╢
║ TCB Security Version Number │ 0 ║
╟─────────────────────────────┼────────────────╢
║ ARB Security Version Number │ 0 ║
╟─────────────────────────────┼────────────────╢
║ Version Control Number │ 0 ║
╟─────────────────────────────┼────────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼────────────────╢
║ Date │ 2021-04-01 ║
╟─────────────────────────────┼────────────────╢
║ Size │ 0x6000 ║
╟─────────────────────────────┼────────────────╢
║ Manifest Extension Utility │ 15.0.0.7069 ║
╟─────────────────────────────┼────────────────╢
║ Chipset Support │ TGP ║
╟─────────────────────────────┼────────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧════════════════╝

---

Zitat von Kolich im Beitrag #5688

---

i think i found problem, you used another samples, i attached screenshot, in the manual said i need just use Tiger H chipset without others.....

---

Zitat von lfb6 im Beitrag #5690

---

Zitat von Kolich im Beitrag #5688

---

i think i found problem, you used another samples, i attached screenshot, in the manual said i need just use Tiger H chipset without others.....

---

Good to hear that you managed it! (Actually the manual doesn't say anything specific about TigerLake, but you're right, there are 2 choices for "H", difference is Mobile or Desktop chipsets.)

---

Hello everyone ,

I own a Z490E from Asus and I've installed 14.1.60.1790 on a fresh windows install , since then system doesn't feel responsive like it used to , my previous me firmware was 14.0.45.1389 .
It's the first time I encounter this problem and I don't want to broke my motherboard , I've already reed the thread explaining the procedure but it's seem complicated , could someone guide me here or pm me please ?

Zitat von Crawz im Beitrag #5692

---

...Z490E from Asus and I've installed 14.1.60.1790 on a fresh windows install , since then system doesn't feel responsive like it used to , my previous me firmware was 14.0.45.1389 . ....

---

I used a most recent one on the asus forum (can't post link here) and updated with FWUpdLcl64

Zitat von Crawz im Beitrag #5694

---

I used a most recent one on the asus forum (can't post link here) and updated with FWUpdLcl64

---

╔═══════════════════════════════════════════╗
║ ME Analyzer v1.253.0 r262 ║
╚═══════════════════════════════════════════╝

╔════════════════════════════════════════════╗
║ 14.1.60.1790.bin (1/1) ║
╟─────────────────────────────┬──────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼──────────────╢
║ Version │ 14.1.60.1790 ║
╟─────────────────────────────┼──────────────╢
║ Release │ Production ║
╟─────────────────────────────┼──────────────╢
║ Type │ Extracted ║
╟─────────────────────────────┼──────────────╢
║ SKU │ Consumer H ║
╟─────────────────────────────┼──────────────╢
║ Chipset │ CNP/CMP-H A ║
╟─────────────────────────────┼──────────────╢
║ TCB Security Version Number │ 1 ║
╟─────────────────────────────┼──────────────╢
║ ARB Security Version Number │ 10 ║
╟─────────────────────────────┼──────────────╢
║ Version Control Number │ 26 ║
╟─────────────────────────────┼──────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼──────────────╢
║ OEM Configuration │ No ║
╟─────────────────────────────┼──────────────╢
║ FWUpdate Support │ Yes ║
╟─────────────────────────────┼──────────────╢
║ Date │ 2021-08-18 ║
╟─────────────────────────────┼──────────────╢
║ File System State │ Configured ║
╟─────────────────────────────┼──────────────╢
║ Size │ 0x2DD000 ║
╟─────────────────────────────┼──────────────╢
║ Flash Image Tool │ 14.0.60.1790 ║
╟─────────────────────────────┼──────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧══════════════╝
╔═════════════════════════════════════════════╗
║ Power Management Controller ║
╟─────────────────────────────┬───────────────╢
║ Family │ PMC ║
╟─────────────────────────────┼───────────────╢
║ Version │ 140.2.01.1018 ║
╟─────────────────────────────┼───────────────╢
║ Release │ Production ║
╟─────────────────────────────┼───────────────╢
║ Type │ Independent ║
╟─────────────────────────────┼───────────────╢
║ Chipset SKU │ H ║
╟─────────────────────────────┼───────────────╢
║ Chipset Stepping │ A ║
╟─────────────────────────────┼───────────────╢
║ TCB Security Version Number │ 3 ║
╟─────────────────────────────┼───────────────╢
║ ARB Security Version Number │ 3 ║
╟─────────────────────────────┼───────────────╢
║ Version Control Number │ 0 ║
╟─────────────────────────────┼───────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼───────────────╢
║ Date │ 2021-02-22 ║
╟─────────────────────────────┼───────────────╢
║ Size │ 0xE000 ║
╟─────────────────────────────┼───────────────╢
║ Chipset Support │ CMP ║
╟─────────────────────────────┼───────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧═══════════════╝
╔════════════════════════════════════════════════════════╗
║ Platform Controller Hub Configuration ║
╟─────────────────────────────┬──────────────────────────╢
║ Family │ PCHC ║
╟─────────────────────────────┼──────────────────────────╢
║ Version │ 14.0.0.7002 ║
╟─────────────────────────────┼──────────────────────────╢
║ Release │ Production, Engineering ║
╟─────────────────────────────┼──────────────────────────╢
║ Type │ Independent ║
╟─────────────────────────────┼──────────────────────────╢
║ TCB Security Version Number │ 0 ║
╟─────────────────────────────┼──────────────────────────╢
║ ARB Security Version Number │ 0 ║
╟─────────────────────────────┼──────────────────────────╢
║ Version Control Number │ 0 ║
╟─────────────────────────────┼──────────────────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼──────────────────────────╢
║ Date │ 2020-06-12 ║
╟─────────────────────────────┼──────────────────────────╢
║ Size │ 0x1000 ║
╟─────────────────────────────┼──────────────────────────╢
║ Chipset Support │ CMP ║
╟─────────────────────────────┼──────────────────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧══════════════════════════╝
╔══════════════════════════════════════════════╗
║ USB Type C Physical ║
╟─────────────────────────────┬────────────────╢
║ Family │ PHY ║
╟─────────────────────────────┼────────────────╢
║ Version │ 12.14.214.2014 ║
╟─────────────────────────────┼────────────────╢
║ Release │ Production ║
╟─────────────────────────────┼────────────────╢
║ Type │ Independent ║
╟─────────────────────────────┼────────────────╢
║ SKU │ P ║
╟─────────────────────────────┼────────────────╢
║ TCB Security Version Number │ 0 ║
╟─────────────────────────────┼────────────────╢
║ ARB Security Version Number │ 0 ║
╟─────────────────────────────┼────────────────╢
║ Version Control Number │ 0 ║
╟─────────────────────────────┼────────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼────────────────╢
║ Date │ 2021-04-01 ║
╟─────────────────────────────┼────────────────╢
║ Size │ 0x6000 ║
╟─────────────────────────────┼────────────────╢
║ Chipset Support │ CMP ║
╟─────────────────────────────┼────────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧════════════════╝

I've the iCLS 1.63.1155.0

where can I found the latest intel iCLS v1.63.1155.1?

Google it & only found this link
https://github.com/intel/INTEL-SA-00086-Linux-Recovery-Tools

Zitat von SM03 im Beitrag #5697

---

I've the iCLS 1.63.1155.0

where can I found the latest intel iCLS v1.63.1155.1?

Google it & only found this link
https://github.com/intel/INTEL-SA-00086-Linux-Recovery-Tools

---

Zitat von westlake im Beitrag #5698

---

Zitat von SM03 im Beitrag #5697

---

I've the iCLS 1.63.1155.0

where can I found the latest intel iCLS v1.63.1155.1?

Google it & only found this link
https://github.com/intel/INTEL-SA-00086-Linux-Recovery-Tools

---

iclsClient_1.63.1155.1@2021.09.07

---

Zitat von Simple im Beitrag #5665

---

Hi,
I have a Dell Inspiron 5567, I bought a couple of 2.5 inch SSDs, Samsung 870 QVO and Crucial MX500 (both 1TB), I tried both of them. Alas, the BIOS does not detect either of them. However, if I run the Diagnostics at boot, the computer detect them and the tests pass successfully.

p.s. Both SSDs work fine on other Desktops and Laptops.

I tried all the various settings and watched lots of videos about this problem, I also tried various newly downloaded BIOSes (upgrade and downgrade); to no avail. But, if I add either of SSDs as a second drive (using the DVD bay, the BIOS will detect the SSD, and it works.

My questions are:

1- Would this situation be averted if I perform an ME region clean?
2- Do I need to extract the BIOS from the laptop and clean it, or can I clean a newly downloaded BIOS from DELL site?
3- Wouldn't a newly downloaded BIOS be already clean, I am not cure I understand this part!?

I would like to use one SSD in the 2.5 inch bay, and I hope to sort this issue.

Thanking you in anticipation.

---