From: Blibbet <blibbet@gmail.com>
To: Anatol Pomozov <anatol.pomozov@gmail.com>
Cc: edk2-devel@lists.01.org
Subject: Re: Extracting vendor blobs from edk2-coreboot payload
Date: Thu, 17 May 2018 12:30:55 -0700 [thread overview]
Message-ID: <384e133e-7c59-8382-7449-6fbf98cf69e6@gmail.com> (raw)
In-Reply-To: <CAOMFOmUJbMouNRNY8ebEXgi3dcvxDGR2CYhjtzfopPK1dML-2g@mail.gmail.com>
On 05/15/2018 03:36 PM, Anatol Pomozov wrote:
> [...] Is there a simple tool that allows to extract these Intel blobs from
> Build/CorebootPayloadPkgX64/RELEASE_GCC5/FV/UEFIPAYLOAD.fd ?
I expect most Tianocore tools focus on creating blobs, not reversing
them. If EDK2 has tools like this, I'd also like to learn about them. :-)
Have you tried UEFITool's UEFIExtract? If that doesn't work out, perhaps
CHIPSEC or UEFI Firmware Parser, all 3 of those tools have libraries to
parse UEFI blobs. Some phases of UEFIReverse might also help. The
freeware-based non-open source UEFI BIOS Updater (UBU) tool may also help.
https://github.com/LongSoft/UEFITool
https://github.com/jethrogb/uefireverse
https://github.com/theopolis/uefi-firmware-parser
https://github.com/chipsec/chipsec
HTH,
Lee Fisher
next prev parent reply other threads:[~2018-05-17 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 22:36 Extracting vendor blobs from edk2-coreboot payload Anatol Pomozov
2018-05-17 19:30 ` Blibbet [this message]
2018-05-17 19:34 ` Andrew Fish
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=384e133e-7c59-8382-7449-6fbf98cf69e6@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