Zitat von OgUrecheK89 im Beitrag #5670

---

......When opening the firmware from the manufacturer using FIT, error 229 and 9 are displayed.
I need to open the firmware from the manufacturer in order not to lose the configuration for the updated firmware......

---

Zitat von lfb6 im Beitrag #5671

---

Zitat von OgUrecheK89 im Beitrag #5670

---

When opening the firmware from the manufacturer using FIT, error 229 and 9 are displayed.
I need to open the firmware from the manufacturer in order not to lose the configuration for the updated firmware......

---

Your ME configuration is in your own ME firmware in your PC, not in the update image! And in addition: update- images ca't be opened in FIT.

---

Zitat von OgUrecheK89 im Beitrag #5670

---

.... Please help me update the ME 15 firmware modules. When opening the firmware from the manufacturer using FIT, error 229 and 9 are displayed.
.....

---

Zitat von OgUrecheK89 im Beitrag #5672

---

FIT opens the ME 12 image for updating without any problems. ME 12.0.81 MSI.

---

Zitat von lfb6 im Beitrag #5671

---

Your ME configuration is in your own ME firmware in your PC, not in the update image! And in addition: update- images ca't be opened in FIT.

---

for my question nobody cant help me?

Zitat von Kolich im Beitrag #5674

---

for my question nobody cant help me?

---

Zitat von MeatWar im Beitrag #5667

---

EDIT: By the Intel ME repository gathered by Plutomaniac, seems that ur using the latest available CON H A (15.0.30.1902) and not CON H B (15.0.35.1932).

---

Zitat von lfb6 im Beitrag #5675

---

Can't even see what you were trying to do with the information you gave...

---

Yes u did, u only didnt get some1 to do it for u, its ur task only. Cleaning it or upgrade its the same version u have now CON H A (15.0.30.1902), no new available.
Dont like the answer wait for others opinion.

EDIT: Yeah u got that rigth, ITS ANSWERED, didnt needed to know even if u posted witch u didnt, ur version 15.x.xx.1706

no. you wrong. right now i have a version 1716, not like you said 1902, i want will upgrade from 1716 to 1902 :)

Zitat von MeatWar im Beitrag #5678

---

Yes u did, u only didnt get some1 to do it for u, its ur task only. Cleaning it or upgrade its the same version u have now CON H A (15.0.30.1902), no new available.
Dont like the answer wait for others opinion.

---

Give more information like MEA output of bios firmware you want to upgrade, all firmware files you used, machine/board you're working on, link to a firmware, post your own ME region, pull an update file of your existing ME region with fwupdlcl -save and post it/attach it, whatever.
You should present your problem in a proper way with all the details available to make people answer...
And as written: With the information you posted it's impossible to give you a proper answer....

Zitat von lfb6 im Beitrag #5681

---

Give more information like MEA output of bios firmware you want to upgrade, all firmware files you used, machine/board you're working on, link to a firmware, post your own ME region, pull an update file of your existing ME region with fwupdlcl -save and post it/attach it, whatever.
You should present your problem in a proper way with all the details available to make people answer...
And as written: With the information you posted it's impossible to give you a proper answer....

---

@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 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 #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 ;)

---