You may try report the FVMAIN_COMPACT with the way like below. Then PeiCore's
FvInfo notification will decompress the FVMAIN_COMPACT and build FV HOB for
decompressed FVMAIN for DXE phase. FvInfo is the standard way, FvHob is produce
for DXE phase. PeiCore only processes FvHob when
PcdFrameworkCompatibilitySupport = TRUE.
//
// Let PEI know about the DXE FV so it can find the DXE Core
//
PeiServicesInstallFvInfoPpi (
NULL,
(VOID *)(UINTN) PcdGet32 (PcdOvmfDxeMemFvBase),
PcdGet32 (PcdOvmfDxeMemFvSize),
NULL,
NULL
);
Thanks,
Star
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Laszlo
Ersek
Sent: Tuesday, August 14, 2018 9:18 PM
To: Hristo Mihaylov <hristo.mihay...@prodrive-technologies.com>;
edk2-devel@lists.01.org
Subject: Re: [edk2] DxeIpl module cannot find DXE entry point
On 08/14/18 14:00, Hristo Mihaylov wrote:
> Hello, Laszlo,
>
> There is a PEIM that executes BuildFvHob with the FVMAIN_COMPACT address and
> size, the function also exits normally.
>
> The crash occurs here:
> https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/DxeIplPeim/DxeLoad.c#L469
> and the platform uses UDK2015 packages.
> I also updated the DxeIpl module to the latest UDK release, but that didn't
> fix the issue.
>
> Now I'm trying two approaches:
>
> 1. to use a decompressed DXE and see if the issue was in the compression.
> 2. to enable source level debugging and track execution.
>
> Any idea what else it could be, besides the BuildFvHob function? Or a way to
> see if the HOB was built successfully.
Sorry, adding fine-grained debug messages (or source level debugging, as you
say) is my only thought at this point.
Laszlo
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
