MSOA replacment module

Discussion in 'MDL Projects and Applications' started by nononsence, May 18, 2012.

  1. nononsence

    nononsence MDL Addicted

    Aug 18, 2009
    809
    804
    30
    #1 nononsence, May 18, 2012
    Last edited by a moderator: Apr 20, 2017

    Attached Files:

  2. nononsence

    nononsence MDL Addicted

    Aug 18, 2009
    809
    804
    30
    #2 nononsence, May 21, 2012
    Last edited: May 22, 2012
    (OP)
    this module works on ASUS P8Z77 WS but bricks ASUS P8P67-Pro, ASUS F1A75-M Pro
    I suspect an dependency issue, but cant develop further until I purchase/build a chip
    programmer.

    again this module is experimental use caution.

    EDIT:
    looking at the MSOA module from the 2 bricked motherboards, they have the older OA2 version,
    without the EFI_LEGACY_BIOS_PROTOCOL dependency, I would avoid trying to substitute this
    module for the OA2 version of MOSA for the time being.
     
  3. nononsence

    nononsence MDL Addicted

    Aug 18, 2009
    809
    804
    30
    The cause of the bricking is byte 0x17 must be set to 0xF8 when inserted in to the firmware, MMTool does this automatically
    but Andyp's Phoenix tool does not. I will modify GenFfs.exe to generate a module ready to insert into the firmware.
     
  4. nononsence

    nononsence MDL Addicted

    Aug 18, 2009
    809
    804
    30
    #4 nononsence, May 27, 2012
    Last edited: May 28, 2012
    (OP)
    updated with modified GenFfs.exe to correctly set byte 0x17, to use Andy's tool to insert you must also
    select "Insert gap if module shrinks (EFI)" to avoid a brick.

    more info about byte 0x17 can be found in header file PiFirmwareFile.h

    EDIT:
    also added copying OemId & OemTableId to all Acpi Tables that match Rsdt/Xsdt OemId + OemTableId
     

    Attached Files:

  5. nononsence

    nononsence MDL Addicted

    Aug 18, 2009
    809
    804
    30
    added a failsafe to the module, if main() fails to complete module becomes inactive.