From: Rafael Machado <rafaelrodrigues.machado@gmail.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Sec and Reset vector
Date: Sat, 22 Oct 2016 16:28:15 +0000 [thread overview]
Message-ID: <CACgnt78v37DqtJ-QYv=sc8XkhNN96XicnUOj7f9=ixbOpoKyqQ@mail.gmail.com> (raw)
Hi eveyrone
I'm doing some studies on edk2 and coreboot, but I'm having some questions
that I believe you can help.
On the journey to try to understand things since the beginning, so they
make sense in future, I'm trying to understand how does the Initial phases
of UEFI / PI firmware work. To do that I got a bios image and start to
reverse it to check the modules and everything present at that bios. Now I
understand, at least the basics, about DXE and PEI phase.
The main question that I have now is about the SEC phase.
To try to understand the SEC phase I tried to reverse this firmware so I
could check the reset vector's first jump or something like that.
The surprise I have is that I was not able to find this code.
To be sure I was reversing on the correct way I generated a coreboot image.
On the image below we can see the initial code of a firmware generated
using coreboot
[image: pasted1]
But at the UEFI firmware I'm studying I'm not able to find anything similar
to that.
My guess before starting this was that at least the SEC initial code should
be similar to the legacy way of doing things, a jmp at 0xfff:fff0
and after that the magic should get started with all uefi phases.
Could someone please give me some light on that?
Thanks and Regards
Rafael R. Machado
next reply other threads:[~2016-10-22 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 16:28 Rafael Machado [this message]
2016-10-22 17:03 ` Sec and Reset vector Marvin H?user
2016-10-22 18:19 ` Andrew Fish
2016-11-04 17:48 ` Rafael Machado
2016-11-04 17:50 ` Rafael Machado
2016-11-04 18:50 ` Andrew Fish
2016-11-04 19:33 ` Rafael Machado
2016-11-04 19:59 ` Laszlo Ersek
2016-11-04 21:18 ` Andrew Fish
2016-11-04 21:28 ` Kinney, Michael D
2016-11-04 22:19 ` Rafael Machado
2017-03-29 19:05 ` Rafael Machado
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='CACgnt78v37DqtJ-QYv=sc8XkhNN96XicnUOj7f9=ixbOpoKyqQ@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