Hello!

Reading through a lot of postings I still couldn't find out if I have a problem here.
I updated ME from v7 to v8 on my rev 1.00 HP Z820, doing the following steps:
- ME enabled, v7 FWUpdLcl to latest v7 version
- ME override, v8 fpt -ME from HP downloaded firmware (v3.96)
- ME enabled, v8 FWUpdLcl to latest v8 version
(I didn't fpt to latest, because it has ~7MB size and the bios versions all have 5MB)

then:
- I wasn't able to close Manufacturing Mode yet (closemnf says some bit couldn't be set, didn't make photo of this)
- fpt back to v3.96 bios ME, still Manufacturing Mode not closed, BUT:
- I don't know if I even should retry it now because meinfo -FWSTS says
"No valid OEM data, ICC not programmed"

As I read somewhere, variables are only written when Manufacturing Mode is disabled, that might be a bad idea.
FIT finds one ICC profile in every ME region I applied, so why does it tell me that?
(I did not use FIT for transferring anything, only for viewing)

Apart from that everything looks fine.
oem id and oem tag are zeroes, but I think, that doesn't matter(?)

Many thanks for help!



-----------------------------

Although all relevant config seems to be present in ME of the downloaded bios, I will read more about the FIT tool and try my luck with that. FIT also has an option regarding the Manufacturing Mode.
I hope I don't make it worse

@maaax - Not sure of anything here, but generally end user cannot and should not update major ME FW version (ie v7 to V8) due to many other BIOS modules also need modified at same time and only manufacturer can do all these changes.
You will have to wait on reply from Plutomaniac about the specific ME FW questions above. I assume you will need to program back in original ME v7 FW region from stock BIOS or backup

plutomaniac

Many thanks, I will wait then!

Some infos:
I exported the ME region with uefitool from the HP BIOS upgrade package. It includes, according to FIT, a "Descriptor Region" and a "ME Region". Both have the same structure and most of the values are the same. As they are included in the 5MB image, they should now also be applied.
EDIT: I ask myself, why does FIT show a Descriptor Region in the 5MB part. These may be some default values? Then of course I haven't applied it, as I didn't use FIT for manipulating the image. And I only used fpt -ME, no fpt -DESC

The two v8 versions in BIOS:



meinfo output:



-----------------------------------

I just compared my (before any changes) dumped flash and the downloaded J63_0396.bin.

Descriptor Region (not applied by my fpt run)
The only differences:
Number of PROC straps 0 -> 1 in J63_0396.bin
All access is set to 0xFF in J63_0396.bin
There is now one more Flash device in the VSCC table in J63_0396.bin
and the VSCC Table Length increased from 0x06 to 0x08

ME region (applied by my fpt run):
Error Filter: All -> Error
Logging Interface - Flash: false -> true
in ICC Profile 0 / Processor or Platform DMICLK (DIV2-5):
- Clock Div Min: 0x0BFA -> 0x0C00
- Clock Div Max: 0x0C0E -> 0x0C00
in ICC Profile 0 / PCH DMICLK (DIV3):
- Clock Div Max: 0x0C0E -> 0x0C00

New parameters in J63_0396.bin:
M3 Autotest Enabled (false)
Independent Firmware Recovery Enable (true)
BIOS Secure boot (false)

Parameters missing in J63_0396.bin:
in Setup and Configuration:
- MEBx password policy (was 0)
- Remote Configuration Enabled (was false)
- a lot of "Hash" parameters, they were set to false

UPDATE:
I let J63_0396.bin run through FIT, extracted ME region via uefitool and applied via fpt -ME, rebooted via fpt -GRESET.
Still Manufacturing Mode and no ICC profile.
fpt -CLOSEMNF says cpu has no access to ME region, even with ME override. Maybe I'll have to check current access settings in Descriptor Region..

I guess you missed my first sentence??

plutomaniac will have to help you, but he may not waste time trying to sort or fix issue here, due to what I said (you can't, and should not do this, only update to latest V7 ME FW, unless you have BIOS for this system that originally comes with V8 ME FW)

HP already added support for ME8 and started to ship firmware with ME8 as they noticed that no hardware change is necessary for ivy bridge support.
So I upgraded to latest BIOS (which supports ME7 and ME8) first.
RGN is "Intel to OEM" and all parameters are already set in the extracted ME, so shouldn't it be EXTR?

I did not miss any sentence and shouldn't seem disrespecting that I continued working on it!
Of course I'm no BIOS expert but I read a lot about it to get a clue what I might try :D
If it doesn't work: soic-clip is on the way ;)

Sorry for bothering you and many thanks for your assistance!
I really don't want to waste your time, so we can stop here.

@maaax - sorry, I didn't mean to offend if I did, and didn't think you were disrespecting me either, I only meant to make you look again at what I said in case you missed it (Some people get in hurry, don't read, don't care etc, so I was trying to guide you along to read back over what I mentioned )
If HP is shipping BIOS with ME 8 FW for this model, then properly flash to that BIOS using standard HP update method, this would update ME FW and BIOS at same time, properly.
You said they "added support for ME8" that's not a thing, they either send out BIOS with ME 8 FW or not, if BIOS does not contain ME8 FW then it doesn't support ME 8 FW
If they are shipping this model with ME 8 FW BIOS, but are not offering that BIOS on site to download, you will need to find a copy, it's not going to be the one on-site with ME 7 FW in it.

And no, RGN meant clean/bare/stock, no direct settings for your specific model are there, you must transfer them using the guide from your original FW
[Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization

Zitat von Lost_N_BIOS im Beitrag #7

---

@maaax - sorry, I didn't mean to offend if I did, and didn't think you were disrespecting me either, I only meant to make you look again at what I said in case you missed it (Some people get in hurry, don't read, don't care etc, so I was trying to guide you along to read back over what I mentioned )

---

Zitat von Lost_N_BIOS im Beitrag #7

---

this would update ME FW and BIOS at same time, properly

---

Zitat von Lost_N_BIOS im Beitrag #7

---

And no, RGN meant clean/bare/stock, no direct settings for your specific model are there, you must transfer them using the guide from your original FW

---

Transferring ME FW settings is done via following the guide as it's written, but yeah, not sure about V7 to V8, you may have to set things one by one manually since you can't work with V7 FW in V8 tools or V8 FW is V7 tools....
Or do above, Plutomaniac beat me to it, I hadn't even checked stock FW since you said it only contained ME 7

Yes, if you have unlocked FD already via jumper or pinmod then do as noted above, this will update bootblock too, it's all in the BIOS.

Thank you!

@plutomaniac
BIOS is on 3.96 already.
I already tried that extracted version (same md5sum) and also tried the extracted version after FIT of the whole HP FW.
Still Manufaturing Mode (although FIT should set the close-bit (?)) and the "no valid OEM data". (everything else seems fine :D )

@Lost_N_BIOS
FD and ME are open via jumper but on early revision mainboards there is no jumper for boot block so a pinmod will be necessary.

The Firmware tools for ME 8 are availale here, a hardware programmer isn't the problem, and there are reports of people who did solve the issue (link). Why not building a clean ME (following this thread), creating a new bios image with ME8, copy the new Bootblock into the image and flash the whole thing back? It seems there's no way updating the boot block by software, anyway?

Do you have a backup of your old ME7 and 'updated' ME8 bios?

@lfb6 I'm aware of the HP threads, but I couldn't find anyone doing ME7->ME8 only.
With updated BIOS, I'd like to do ME upgrade first and have it in a clean state with old boot block.
Next would be boot block via pinmod. Unfortunately my mainboard revision doesn't have the E14 jumper yet.

Steady hand, tweezers, and electric tape and then you are the jumper If you can't solder I mean
Provided the pads are there for the pins I mean, of course. Tape on end of tweezers for you, and tape off areas on the board in case you slip, then all OK
That, or do the E.1 pinmod from the unlock guide thread here [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing

The pins of the Realtek chip are visible. Steady hand, well.. no :D but it will work! Somehow..

Zitat von Lost_N_BIOS im Beitrag #14

---

tape off areas on the board in case you slip

---