The quote seems to say that not only the ME uses the SPI VSCC table. So wondering if BIOS is using the descriptor for flash updates but then makes a change in SPIBAR where it wants to use 2019 for ME runtime. So I will try and swap on a new SPI chip that supports 2019 and change the descriptor to match.

Too bad I can't figure out where the 2019 setting is inside the BIOS region to edit.

This BIOS is Phoenix legacy so not UEFI, is there a similar legacy software? Neat that it does tell me the Gbe ver in the legacy BIOS (0.07 vs 0.10)

Edit: Actually loading the Full SPI dump did allow for use of the UEFI tool.

Ok so got some progress with swapping the SPI.

Now just the Runtime Partition Coded is corrupted but now the ME is not sleeping but active!
No idea why it defaulted to VSCC 0x201D below. Changing the Descriptor VSCC seems to have no effect and defaults to mbw setting. (going to set desc as 0x201D to match)

vsccommn.bin was created on 00:29:16 07/16/2009 GMT
  Ignition FW Status(FAD_IDX):      Using Data from Factory Default Image
  Ignition FW Status(BOOT_IMAGE):   FW booted from Factory Default Image
  Ignition FW Status(EVENT_LOG):    Event Log is empty
  Ignition FW Status(ICC_STS):      Clock programming successful
  Ignition FW Status(CF):           Processor feature configuration successful
  Ignition FW Status(SWC):          SWC application successful
  Ignition FW Progress:             Intel(R) ME is active
 
 
Factory Default Partition Data is validated and healthy.
Runtime Partition Data is validated and healthy.
Factory Default Partition Code is validated and healthy.
Runtime Partition Code is corrupted.
SPI Flash ID #1 BIOS VSCC value is 0x201D
SPI Flash ID #1 (ID: 0x1F4700) BIOS VSCC value checked
FPBA value is 0x0
 

So now that the ME is active, can I repair the runtime code somehow with a tool like FWUpdfLci? I still get the error ME fw corrupted at BIOS boot which I want to go away.

Edit: Hrm seems still shows ME sometimes sleeping. But at least that 0x2019 error went away. Still not solved, need to remove ME boot error message

Tried a few times to follow the clean-up procedure with same failure. Frustrating as the FITC tool should output the "corrected" ME region and I can just use fptw, right? Or do I need to do the entire SPI via external programmer? Could you offer any tips or generate one for me from the posted image?

Tried but same result. Perhaps since B0 chipset I should use the attached ME ver? (took a while to locate)