From: Hristo Mihaylov <hristo.mihaylov@prodrive-technologies.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: DxeIpl module cannot find DXE entry point
Date: Thu, 9 Aug 2018 12:14:39 +0000 [thread overview]
Message-ID: <d923ab5cecac4533bab39fd48a246c9c@prodrive-technologies.com> (raw)
Hello,
This is my first time posting to a mailing list. I am building a custom platform that fails when handing off control from PEIM to DXE.
Here's the error:
```
ASSERT_EFI_ERROR (Status = Not Found)
ASSERT c:\users\hrimih\documents\work\scalable\bios\MdeModulePkg\Core\DxeIplPeim\DxeLoad.c(480): !EFI_ERROR (Status)
```
In the platform only the DXE phase is compressed, using LZMA. I suspect that it's not being decompressed and the module cannot find the DXE entry point.
This is the relevant .FDF part.
```
[FV.FVMAIN]
BlockSize = 0x10000
FvAlignment = 16
ERASE_POLARITY = 1
MEMORY_MAPPED = TRUE
STICKY_WRITE = TRUE
LOCK_CAP = TRUE
LOCK_STATUS = TRUE
WRITE_DISABLED_CAP = TRUE
WRITE_ENABLED_CAP = TRUE
WRITE_STATUS = TRUE
WRITE_LOCK_CAP = TRUE
WRITE_LOCK_STATUS = TRUE
READ_DISABLED_CAP = TRUE
READ_ENABLED_CAP = TRUE
READ_STATUS = TRUE
READ_LOCK_CAP = TRUE
READ_LOCK_STATUS = TRUE
FvNameGuid = CDBB7B35-6833-4ed6-9AB2-57D2ACDDF6F0
....
INF modules
....
[FV.FVMAIN_COMPACT]
FvAlignment = 16
ERASE_POLARITY = 1
MEMORY_MAPPED = TRUE
STICKY_WRITE = TRUE
LOCK_CAP = TRUE
LOCK_STATUS = TRUE
WRITE_DISABLED_CAP = TRUE
WRITE_ENABLED_CAP = TRUE
WRITE_STATUS = TRUE
WRITE_LOCK_CAP = TRUE
WRITE_LOCK_STATUS = TRUE
READ_DISABLED_CAP = TRUE
READ_ENABLED_CAP = TRUE
READ_STATUS = TRUE
READ_LOCK_CAP = TRUE
READ_LOCK_STATUS = TRUE
FvNameGuid = 27A72E80-3118-4c0c-8673-AA5B4EFA9613
FILE FV_IMAGE = 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 {
SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRED = TRUE {
SECTION FV_IMAGE = FVMAIN
}
}
```
Then in the .DSC I have:
```
MdeModulePkg/Core/DxeIplPeim/DxeIpl.inf {
<LibraryClasses>
NULL|MdeModulePkg/Library/LzmaCustomDecompressLib/LzmaCustomDecompressLib.inf
}
```
And for the DXE Main:
```
MdeModulePkg/Core/Dxe/DxeMain.inf {
<LibraryClasses>
DevicePathLib|MdePkg/Library/UefiDevicePathLib/UefiDevicePathLib.inf
NULL|MdeModulePkg/Library/DxeCrc32GuidedSectionExtractLib/DxeCrc32GuidedSectionExtractLib.inf
NULL| MdeModulePkg/Library/LzmaCustomDecompressLib/LzmaCustomDecompressLib.inf
<PcdsFixedAtBuild>
gEfiMdePkgTokenSpaceGuid.PcdMaximumLinkedListLength|0
}
```
I expect that this PEIM module will decompress the DXE partition and find the entry point:
```
DxeCoreEntryPoint|MdePkg/Library/DxeCoreEntryPoint/DxeCoreEntryPoint.inf
```
Any advice on how I can debug/fix this?
Regards,
Hristo Mihaylov
next reply other threads:[~2018-08-09 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 12:14 Hristo Mihaylov [this message]
2018-08-09 16:40 ` DxeIpl module cannot find DXE entry point Laszlo Ersek
[not found] ` <c98dc9df50b045a19439a255319a8d63@prodrive-technologies.com>
2018-08-14 13:17 ` Laszlo Ersek
[not found] ` <0C09AFA07DD0434D9E2A0C6AEB0483103BBAD3DE@shsmsx102.ccr.corp.intel.com>
2018-08-15 10:26 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d923ab5cecac4533bab39fd48a246c9c@prodrive-technologies.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox