You mean you have to remove the bios CHIP to program it ? Is that the only way?
Didn’t write that.
I ended up getting myself a programmer and dumped the first chip. The system has dual-chips, with the second one containing just the BIOS region. The second is a WSON so I would rather not try to desolder/solder it.
I extracted the BIOS region from a Dell firmware update and glued it to the dumped file as a placeholder. Without it, MFIT can’t build and UEFITool gives an error.
I opened the file in MFIT and enabled the AMT settings, then built the image. I plan on flashing this tomorrow with flashrom, using the file descriptor flag to only flash the ME region.
Am I missing anything? As far as I know, this was the way to do it for CSME versions <16.
Sorry, I just made the assumption that the only way to do it was to remove the chip
Hi,
Which programmer did you end up buying? How can I identify which chips are the bios?
Do you have any photos of the board to help identify the bios etc…
Sounds OK, but I never did a partial flash with a programmer and I don’t use flashrom, so no idea if this might work (no idea why one would try not to flash a complete chip, either).
After flashing and booting into MEBx, it still only shows Standard Manageability.
I tried a partial flash, full flash, and using NeoProgrammer as well. If I dump the image after the computer has gone through a reboot, I can see that parts of the ME region have changed from what was flashed. Specifically, these portions when seen in UEFITool:
So it seems like it is resetting the ME settings when it boots and detects they are different from what they were originally (possibly by comparing to parts of the BIOS region?).
Post/attach the image you dumped after the reboot.
Thanks! Please upload both the image you dumped and the revised image you flashed for comparison.
amt_enabled.bin.zip (6.5 MB)
backup.bin.zip (6.5 MB)
The amt_enabled was the first attempt after changing the settings in MFIT. The latest flashed image (the one before after_reboot) had some additional changes in MFIT to try to get it to stick.
@lfb6, if/when @LiberaVeritas gets this working as he seems much closer then I am.
Could I just use his bios updated version to flash mine? As it is also 7010.
There’s a lot of more or less meaningfull changes but none of these configurations has AMT enabled! Seems you mixed some configurations / dumps in addition with different hardware configurations (these settings are most probably saved in FD):
In addition ‘AMT enabled’ shows in MEA ‘Initialized’, should read ‘Configured’ after a fresh MFIT build process.
I recommend just to have the files that are needed in the MFIT directory, and to delete all other files and folders in …\Modular Flash Image Tool\WIN32.
In addition run the files you flash through MFIT, save config as xml and compare to config for backup!
As written just now: There seem to be different hardware configurations og these machines!
-
Don’t use an ME region initialized on another machine.
-
Don’t ever overwrite your SPI before having done at least valid dumps (100% bitwise identical and structure in UEFIToolNE!)
Since you have to compare the configuration with your machine anyway it’s just the same amount of work.
You’re right, I was mixing up files in the MFIT directory. I cleaned it up and did it from scratch. Now it’s working, thanks!
Thanks for the feedback!
Do you mind summarising the steps, software etc…
My programmer should arrive today and I will be giving this a go.
I just read many of the posts in this forum about enabling AMT and using a programmer.
The process is identical to cleaning/ reinitializing a ME firmware described here for CSME versions 2 - 15 with changing the settings for AMT in addition before saving yje original configuration.
CSME 16 looks a little different, but it’s practically just the same.
I am just reading through that link as you posted.
I have ran the following commands:
FPTW64.exe -D 7010-FPT-BIOS-1.bin -BIOS
FPTW64.exe -D 7010-FPT-ME-1.bin -ME
FPTW64.exe -D 7010-FPT-FD-DESC-1.bin -DESC
So I have extracted the Bios, ME and FD.
I also ran the command
FPTW64.exe -i
The output was as follows:
Intel (R) Flash Programming Tool Version: 16.1.25.2049
Copyright (C) 2005 - 2022, Intel Corporation. All rights reserved.
Reading HSFSTS register... Flash Descriptor: Valid
--- Flash Devices Found ---
ID:0xC84018 Size: 16384KB (131072Kb)
ID:0xC84019 Size: 32768KB (262144Kb)
--- Flash Image Information --
Signature: VALID
Number of Flash Components: 2
Component 1 - 16384KB (131072Kb)
Component 2 - 32768KB (262144Kb)
Regions:
DESC - Base: 0x00000000, Limit: 0x00000FFF
BIOS - Base: 0x01000000, Limit: 0x02FFFFFF
CSME - Base: 0x00103000, Limit: 0x00A70FFF
GbE - Base: 0x00101000, Limit: 0x00102FFF
PDR - NOT PRESENT
EC - Base: 0x00001000, Limit: 0x00100FFF
Master Region Access:
BIOS - ID: Read: 0x000F, Write: 0x000A
CSME - ID: Read: 0x000D, Write: 0x0004
GbE - ID: Read: 0x0009, Write: 0x0008
EC - ID: Read: 0x0101, Write: 0x0100
Total Accessible SPI Memory: 49152KB, Total Installed SPI Memory: 49152KB
Since I have the software tools I need now, ill read the that doc and go through the steps.