your firmware's name.bin = 9.1.40.1000_1.5MB_PRD_EXTR.bin
So this;
C:\Users\yourname\Downloads\Intel ME System Tools v9.1 r7\FWUpdate\WIN64> FWUpdLcl64 -f your firmware’s name.bin
Will look like this in your case;
F:\Intel ME System Tools v9.1 r7\Intel ME System Tools v9.1 r7\FWUpdate\WIN64>FWUpdLcl64 -f 9.1.40.1000_1.5MB_PRD_EXTR.bin
don't forget to check the repo if it contains more suitable firmware for you device

@plutomaniac

Thank you for all your efforts.

It does look somewhat better, but remember that you and I already know what is going on, so we can figure out what the instructions stand for.
I only used the word "somewhat", because I see very basic questions popping up even lately, and for people posting such questions I have no doubt that the instructions will still be confusing.

I am fine with it as it is, but I would like to give you some suggestion (if you do not mind) on how to possibly eliminate even more confusion:

Current instructions:
For example, a hypothetical CSME 13.30 LKF S v10 system must use LKF_S_10.xxx.xxx.xxxx firmware, a hypothetical CSME 15.0 TGP P v12 system must use TGP_P_12.xxx.xxx.xxxx firmware etc

I would write this (and similar) part(s) as following (highlighting my additions):
For example, a hypothetical CSME 13.30 LKF S PHY v10 system must use PHY LKF_S_10.xxx.xxx.xxxx firmware, a hypothetical CSME 15.0 TGP P PHY v12 system must use PHY TGP_P_12.xxx.xxx.xxxx firmware etc

The reason for that is that we are already talking about 2 binary versions (the CSME and PHY in this case), and believe me, it is confusing, and this is pretty much why I wrote you in the first place.
The more explicit you are, the less questions will arise and users are prone to less mistakes as well.

I would also restructure the description for all the CSME versions.
For me (and I am sure for some others as well) having to read different sections for applicable information only adds to the confusion.
What I would do is to separate everything by CSME version and write everything that belongs to that specific CSME version so that all information is available at one place.
I do understand that this would add redundancy and length to the post, however, the other, not relevant descriptions would not need to be reviewed and people would not even notice the redundancy therefore.

If I work with CSME v15 for instance, I only would like to read about v15, unless the steps are exactly the same for other versions as well, but they are not as far as I can tell.
With the instructions available currently, I should review at least the following:
- Warning for CSME v13+
- Warning for CSME v13.30, v14.1 & v15.0 H
- How to use CSME v13.0, v13.50, v14.0, v14.5, v15.0 LP & v15.40 FWUpdate Tool
- How to use CSME v13.30 & v15.0 H FWUpdate Tool

Every time the post gets updated, I would need to review them most likely (and definitely should actually) before performing an update.

So I would just segregate everything by the main CSME version (e.g. 12.x, 13.x, 14.x, 15.x - assuming there is no real difference between the sub versions) like I said.
Should there be actually notable difference for the sub versions, I would just explicitly refer to them under the main version.
Every important information in one place, no need to look around elsewhere and potentially miss out something important.
For the targeted audience it will greatly increase the experience, for you and experienced users it would be just a bit more lengthy post.

Professionals would rarely consult the instructions anyway, whereas for newcomers it would be much more helpful in my opinion.
Not too much additional effort, as the text is mostly already there, you just need to re-organize (copy-paste) it should you go for it.
All these "build yourself" parts add a lot to the complexity of the process already, and if the tools do not cover every scenario, people might end up damaging the system.

Again, for me it is fine as it is right now, especially that you are here to help me out.

Forgot to mention last time, that if you do go for collecting the errors and instructions for them, they should be put in a separate section (e.g. Common Errors).

For your information, I did not perform the update this time.
The image was built, but the FWUpdate tool gave me an error:
Error 328: Full FW Update using same version is not allowed. Include -allowsv in command line to allow it.

I decided not to go for the update as it looks to be a minor change (PMC FW Version 150.1.20.1028 --> PMC FW Version 150.1.20.1030) in this case, and I am sure a new CSME binary will be out soon enough anyway.
It would also be nice to see some instructions for such scenarios (where the CSME version is already the latest) and you need to use the -allowsv switch.
Comments here get buried rather too soon with new pages being created.

I personally am rather hesitant when it comes to performing a task first time, as I have no idea what needs to happen and therefore if any minor step is not listed it is difficult to verify whether things are exactly as they should be.
This (listing everything and every possible scenario explicitly) is pretty much key in having the perfect documentation in my opinion.

Thank you for all your hard work once again.

Zitat von onuracengiz im Beitrag #5371

---

your firmware's name.bin = 9.1.40.1000_1.5MB_PRD_EXTR.bin

---

5mb ones are not for you :)
You can change their names that does not matter

Hi @plutomaniac,

I think you did manage to make the most out of it at first sight - I am yet to read thoroughly.
Of course, if the the steps are exactly the same for the different versions, they should be merged together.
I already made this remark in my previous post as you may remember, I just had no real oversight of how many of them do belong together based on the previous structure of the post.

I might send you a PM primarily for some visual tweak (readability) related suggestions.
It is fine if you do not plan to make any of the proposed modifications, and therefore I do not wish to spam the comment section with them.
I am already very happy with how the content turned out.

One a side note, I have noticed that the v15 tools do not have the binaries (FWUpdLcl64 and MEInfoWin64) you provided me the last time.
Should they (and their 32-bits counterparts I suppose) not be included as soon as possible?
I am not sure what impact this might have as I have been using the files attached by you for the first update.

@plutomaniac

I forgot to mention previously that the machine is not with me since the update, it was a present for someone else.
I do have on-demand remote access to it pretty much any time.
I will get you the HWInfo details probably a bit later today.

I will share the ideas here then as per your preference.
I wanted to do it in PM, because I actually wanted to prepare the whole content for you so you can just do a side-by-side comparison to make your decision easier.
Especially that I know now how limited your time is for such things.
Also, these are rather very specific things - some might say nitpicking, and I have no intentions in opening a lengthy debate.
The key changes are already there, feel free to reject all suggestions from this post.
I will try to keep this as short as possible, but long enough to make a point for each case.

So, a few suggestions for additional content to the post, but not related to the steps already in place:

1. It would be nice to have a changelog to see what has been modified since last time.
Anyone pretty much besides you will not be able to point out exactly what has changed since the last time.
A short (but specific) indication of the changes would be most welcome by many, I have no doubt about it.
People would not need to reread everything to figure out what was going on, especially that it would still be difficult to point out what has change since the last time.
It is also a good summary of your efforts (donations!).

Just an fictional example how it could be from content point of view:

2021.02.02: Replaced CSME 12.0 Consumer LP C v12.0.71.1681 with CSME 12.0 Consumer LP C v12.0.72.1689
2021.02.01: Updated instructions for "How to use FWUpdate Tool at CSME v14.1 H"
2021.01.30: Updated Intel CSME System Tools v15.0 r3 to v15.0 r4
2021.01.28: Minor changes to the instructions from B1 section

This could be in "spolier" tags or just linking to an external .txt file.
If it would be a link, keep it in the "Last Updated: xxx-xx-xx" line as clickable (link in a new tab to not go away from the site), maybe adding the word "changelog" to be the link itself.

2. Right below "Last Updated: xxx-xx-xx" (basically after the changelog reference) you should put in a few sentences how any newcomer should be using this guide
What they must do in order to successfully update the firmware.
Pretty what you wrote in your last response:

The goal of section B1 is for the end user to read all the red parts, one after the other, in that order.
If something does not apply, it can be skipped.

Maybe adding a little extra to it (explanation and other common question related stuff):
This is a prerequisite for performing a successful update.
The name of the files does not matter when building the firmware or performing the updates.

Do not worry about how basic things may sound, anyone who has no experience might be eventually resorting to asking these basic questions.
All these ("changelog", "introduction") should be on the top in my opinion, before the user begins to read the instructions, so they know exactly what they should expect from your article.

Visual (readability) related adjustments (I will include small examples):

1. I think it would add a lot to the experience if the content would be split on each small heading as well as at each sentence.
I personally have a lot of trouble reading (not writing) a wall of text, and maybe other would appreciate it, too.
It would also be much more easier to pick up where you left off (mostly when rereading while also performing the steps).

I wanted to prepare this myself based on the current content to see if it actually makes sense in this case as well.
Basically this is how I write e-mails and comments in scripts and never ever have anyone complained about it
The text also would not get too crowded even on smaller screens or screen resolutions.

If you do not like that some lines would go into multiple lines (as it may not be as appealing), you could manipulate the content a bit:

The mandatory regions are the Flash Descriptor, the (Converged Security) Management Engine and the BIOS.
Flash Descriptor (FD) controls read/write access between the regions among other things, (Converged Security) Management Engine (CSME/ME or Engine), holds the system's Engine firmware.

2. The choice of colors (normal text, bold, blue and red) is perfect as it is.
If there is one thing I would like to have changed, it is the placeholder part - which I think should also be red.
Again, not something important to begin with, but they would still be standing out and you would have 1 less color based on the principle of "less is more".

3. Text formatting suggestions
You are using bold text a bit sparingly in my opinion.
A lot more key words could be highlighted (bolded) to draw our attention to the critical steps or information, which is certainly an issue in my case.
Quotes would be redundancy in this case, they could be removed.
Try to be consistent as much as possible (e.g., "&" vs "and" - to me the latter just looks more professional, which should reflect your expertise, and this is some serious business after all)
Suggestions, comments/hints/remarks and alternatives could be italic.
This is how it would look like with the first point combined (ignore the bullet point changes, I do not know how to make them to be the same):

Here is what the combined efforts from points 1 and 3 would look like for one part of the current content:

How to use FWUpdate Tool at CSME v13.0, v13.50, v14.0, v14.5, v15.0 LP and v15.40:
At CSME v13.0, v13.50, v14.0, v14.5, v15.0 LP and v15.40, FWUpdate tool requires CSME firmware which have been combined/stitched with the equivalent PMC and PCHC IUP firmware via Flash Image Tool (FIT).
To generate the correct FWUpdate compatible CSME + PMC + PCHC firmware combination for your system via FIT, you must first know your system's Chipset Series (ICP, JSP, CMP, TGP, EHL), Chipset Platform (H, LP, N, V), Chipset Type (Consumer, Corporate, Slim, Server, Atom) and Chipset Stepping/Revision (A, B, C, D etc).

• Download the latest Intel CSME System Tools (Section C) as well as the ME Analyzer tool.
• Acquire the Chipset Platform and Chipset Stepping information.
  From Intel CSME System Tools, run MEInfo command line tool:
  Under Intel(R) ME code versions > FW Version you will find your system's Chipset Platform as well as Type (i.e. H Consumer etc).
  Under PCH Information > PCH Step Data you will find your system's Chipset Stepping which starts with a letter (Ax, Bx, Cx etc).
  Alternative method for the above:
  Drag and drop your system's SPI/BIOS image at ME Analyzer tool and find SKU field which shows your system's Chipset Type and Platform (i.e. Consumer H).
  Find Chipset Stepping field which lists one or more supported Chipset Steppings in the form of letters (A, B, C etc).
• Based on your system's Chipset Series, Platform, Type and Stepping, choose the correct CSME, PMC and PCHC firmware (Section B).
• Input the chosen CSME firmware into the 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 fit.exe and vsccommn.bin are present, otherwise delete everything else.
• Run Flash Image Tool (FIT) and adjust the Chipset Platform drop-down menu at the top to match your system's Chipset Platform (either H series (without RocketLake), LP series, N series or V series).
  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.
• Go to FW Update Image Build tab on the left and input PMC Image > PMC Binary File and PCHC Image > PCH Configuration File fields with the chosen PMC and PCHC firmware images accordingly.
• Click the green Build Image For FWUpdate (not the Build Image) button at the top 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.

@plutomaniac

I have attached the HWInfo report as per your request.
Let me know if it is fine this way or if you need anything else.

@plutomaniac

I think it gets better and better with each of your modification.

Hopefully others will like it as well.

lol
9.1.40.1000 = 9.1, Build 1000, Hot Fix 40
congratulations,it is done :)
@vegzos

I have Asus B85M-G, with latest BIOS 3602 and Win 10 Pro x64
I cannot install Intel Management Engine downloaded from Asus website. I've already installed Intel Chipset Driver, but when trying to install IMEI, got Fatal Error Message.

Thanks in advance for any help