@SoniX

I was about to post the same thing. The problem is between OEMs (for adding an unnecessary attribute to already fixed files) and MMTool for not being able to work with such files. If you remove that fixed attribute (change EFI_FFS_FILE_ATTRIBUTES from 0C to 08) MMTool will work. I don't see how you could do this in UBU, as MMTool can't touch such volumes with fixed files. Maybe if Fernando would add a guide to first post, with my help if needed?

You also said that MMTool can't replace files in A032--- GUID. What is the general problem? I tried with one file and it worked, but maybe there are certain conditions in which it fails?

Zitat von lordkag im Beitrag #1823

---

You also said that MMTool can't replace files in A032--- GUID. What is the general problem? I tried with one file and it worked, but maybe there are certain conditions in which it fails?

---

I'm trying to mod a gigabyte bios (Z97M-DS3H) with this tool and there is something i don't understand abou the microcode.

When i load the bios on UBU it shows two CPU microcode one for haswell processors and one for broadwell processors

7 Update Intel CPU MicroCode Haswell/Broadwell
     CPU Microcode 040671 BDW   - 0D
     CPU Microcode 0306C3 HSW   - 1C
 

But when i update any of them, the other disappears so i'm not sure how to proceed and if it is safe to use this bios with any of the microcodes updated. Let's say i got a haswell CPU but i update the bios with the broadwell microcode (since they seem to be more up to date) and the haswell microcode is "gone", my question is, will i be able to use this modded bios with my haswell CPU?, thanks!.

Just FYI, as the UBU tool wanted me to report and upload this microcode modded by Svet in the MSI HQ Forum: E7885IMS.195 beta.
I updated it with the latest RST UEFI ROM using UBU.130.1 and flashed it.
This beta BIOS has more extensive OC settings, a newer Intel UEFI LAN ROM and works like a charm.
Just to let you know ...:-)

@ quetzalin
Because now targeted microcode read from _FIT_.
And if you do not correct the address for the second microcode, in _FIT_, it will not work.

Zitat von plutomaniac im Beitrag #1828

---

@ SoniX:
I will change the message slightly when run via -ubu to make it more clear for UBU users.

---

@ plutomaniac:
Yes, that's what I mean. All BIOS content is "microcode" to me, and ME Firmware is thus part thereof ...
I am not a coder by profession, so please bear with me whenever I use wrong terminology ...

There is a proposal. We probably confusion in words.
All as MEI write Firmware or FW. This is what is in the BIOS (SPI Image).
Microcode or uCode - write only for CPU
I think that this will solve some not understanding. :)

Hello, i would like to ask if it's also possible to update the cpu microcode for mobile platforms like Core M.
The Bios shows Microcode Revision 1f, i guess it's Platform C0 that is used for mobile Broadwell processors.

Zitat von SoniX im Beitrag #1827

---

@ quetzalin
Because now targeted microcode read from _FIT_.
And if you do not correct the address for the second microcode, in _FIT_, it will not work.

---

@ Wootever
You have the latest version of the CPU microcode. More new I have not. Do not change anything.

@ quetzalin
If it is short
In UEFITool look for a file containing _FIT_ and "Extract it as body". Open in hex-editor. Example for Asus Z97-Pro

The addresses are specified for the BIOS (SPI Image) 16MB, 8MB to be 40 FB 63, first microcode, and etc.
Opwn in hex-editor file BIOS (SPI Image) and looking for some new microcode address. And introduces new addresses in _FIT_.
The modified file _FIT_ back into the BIOS (SPI Image).
In general, solid handmade.
So it is easier to update only one correct microcode.

Zitat von SoniX im Beitrag #1834

---

@ quetzalin
If it is short
In UEFITool look for a file containing _FIT_ and "Extract it as body". Open in hex-editor. Example for Asus Z97-Pro

The addresses are specified for the BIOS (SPI Image) 16MB, 8MB to be 40 FB 63, first microcode, and etc.
Opwn in hex-editor file BIOS (SPI Image) and looking for some new microcode address. And introduces new addresses in _FIT_.
The modified file _FIT_ back into the BIOS (SPI Image).
In general, solid handmade.
So it is easier to update only one correct microcode.

---

If the file size of the microcode was always constant, there is no problem. However, with each new version of the size it may change, and therefore will offset the address for second microcode.
For the first microcode address is usually always remains unchanged.

@ all
Seeking OOROM Intel LAN Boot Agent GE version 1.5.63 on 1.5.69.