From: "Alireza Banejad" <alibanejad1376@gmail.com>
To: devel@edk2.groups.io
Subject: [edk2-devel] Transition from DxeIpl to DxeCoreLoad
Date: Mon, 4 Dec 2023 14:06:31 +0330 [thread overview]
Message-ID: <CADH3hnJ=+A+2w0y=b2PfrNhEfs-9R3GNm1iw+axXR5SdXabKYQ@mail.gmail.com> (raw)
Hello everyone,
I am building the wilsonCity Rvp From the whitleyLake package inside
edk2-platforms. unfortunately i wasn't able to get the debug running
even though I tried everything but that isn't my problem right now
since I use POST codes on each part of code and check to see if the
codes are displayed on the motherboard. my main problem is I put a
post code right before dxeipl to see if it reaches this point:
IoWrite8(0x80,0x7b);
Status = TempPtr.DxeIpl->Entry (
TempPtr.DxeIpl,
&PrivateData.Ps,
PrivateData.HobList
);
and so the motherboard shows me 0x7b but it doen't go inside the
DxeloadCore function since I put a Post code at the very beginning of
this function and its still stuck on the 0x7b code:
EFI_STATUS
EFIAPI
DxeLoadCore (
IN CONST EFI_DXE_IPL_PPI *This,
IN EFI_PEI_SERVICES **PeiServices,
IN EFI_PEI_HOB_POINTERS HobList
)
{
...
//
// if in S3 Resume, restore configure
//
IoWrite8(0x80,0x3a);
BootMode = GetBootModeHob ();
IoWrite8(0x80,0x22);
...
I dont have any better debug approaches to check the stack or
registers that is why i can only send POST codes as evidence that
execution has reached to that point. I dont know why it doesn't
execute the DxeLoadCore properly and I assume the CPU halts since it
just stays stuck on the previous post code from before calling DxeIpl
(I mean 0x7b). I also checked if any arguments being passed to
TempPtr.DxeIpl->Entry are NULL but it seemed none were NULL.
Thanks,
Alireza
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112030): https://edk2.groups.io/g/devel/message/112030
Mute This Topic: https://groups.io/mt/102968005/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2023-12-04 10:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CADH3hnJ=+A+2w0y=b2PfrNhEfs-9R3GNm1iw+axXR5SdXabKYQ@mail.gmail.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