Tool to Insert/Replace SLIC in Phoenix / Insyde / Dell / EFI BIOSes

Dear,
I dont understand what you are talking about. i asking for H61M-P20 bios. You are talking about Z77?
Please explain.
Regards
Manu

 

You need to login to view this posts content.

 

Whenever a module is replaced/inserted MMtool will set byte 0x17 (EFI_FFS_FILE_STATE) to 0xF8 replicating this may
prevent a few bricks.

 

You need to login to view this posts content.

 

Are Biostar UEFI users out of luck getting support from the developers?

 

GenFfs.exe sets the file state field to

Code:

FfsFileHeader.State = EFI_FILE_HEADER_CONSTRUCTION | EFI_FILE_HEADER_VALID | EFI_FILE_DATA_VALID;

on line 869 of GenFfs.c which is 0x07 it could be set to 0xF8 when GenFv.exe is used, I haven't dug that deep
into it yet.

EDIT:

found it in GenFvInternalLib.c line 381

Code:

VOID
UpdateFfsFileState (
  IN EFI_FFS_FILE_HEADER          *FfsFile,
  IN EFI_FIRMWARE_VOLUME_HEADER   *FvHeader
  )
/*++

Routine Description:

  This function changes the FFS file attributes based on the erase polarity
  of the FV. Update the reserved bits of State to EFI_FVB2_ERASE_POLARITY. 

Arguments:

  FfsFile   File header.
  FvHeader  FV header.

Returns:

  None

--*/
{
  if (FvHeader->Attributes & EFI_FVB2_ERASE_POLARITY) {
    FfsFile->State = (UINT8)~(FfsFile->State);
    // FfsFile->State |= ~(UINT8) EFI_FILE_ALL_STATE_BITS;
  }
}

 

You need to login to view this posts content.

 

chose no.
only modify 3 modul
acpi 16D0A23E-C09C-407D-A14A-AD058FDD0CA1_1_189.ROM (RSDT, XSDT)
69009842-63F2-43DB-964B-EFAD1C39EC85_0_312.ROM (maker)
996AA1E0-1E8C-4F36-B519-A170A206FC14_0_314.ROM (Pubkey)
(manufacturer: chose other, no select Msi)
----------
It's guide H61M-P20.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I'm sorry I think there is a misunderstanding, I did not mean to imply that there is a bug in Phoenix tool, or that you are
using any of the open source tools or code.

the point I am trying to make is that since MMTool.exe sets the state field in the FFS header that it would also be
desirable if Phoenix tool also set the state field. If an individual were developing a firmware module using the official
build tools they would stop the build after GenFfs.exe completed and not continue to build a firmware volume using
GenFv.exe if they then use Phoenix tool to add the module into the firmware without setting the state field to 0xF8
they would experience a brick.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.