public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Janne Heß" <jannehess@gmail.com>
To: edk2-devel@lists.01.org
Subject: Building and integrating CorebootPayloadPkg
Date: Mon, 31 Oct 2016 14:07:40 +0100	[thread overview]
Message-ID: <de2bc234-28eb-0cd8-aa44-ab69807e62a7@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

Hello everyone,

I'm currently trying to build CorebootPayloadPkg to integrate it into my
coreboot.
I follewed the instructions in
CorebootPayloadPkg/BuildAndIntegrationInstructions.txt to build
UEFIPAYLOAD.fd.
The instructions tell me to add choose this file as an executable elf
payload in the coreboot configuration.
Now, when building coreboot, I end up with the following output:

> Performing operation on 'COREBOOT' region...
> E: The stage file is not in ELF format!
> E: skipping 32 bytes of FV padding
> E: skipping 28 bytes of section padding
> E: Could not add [UEFIPAYLOAD.fd, 852750 bytes (832 KB)@0x0]; too big?
> E: Failed to add 'UEFIPAYLOAD.fd' into ROM image.
> E: Failed while operating on 'COREBOOT' region!
> E: The image will be left unmodified.
> make: *** [build/coreboot.pre] Error 1

As the script tells me to check if the payload is too big, I set my BIOS
chip size to 12 MB in the config just to make sure this is not a problem.
This didn't help.
I also asked on #coreboot, where I was told to use the cbfstool to
include my payload which failed with the same message.

So to me it looks like whatever UEFIPAYLOAD.fd is, it is not a Coreboot
payload.
Are there any commands missing from the documentation that I need to
build a valid payload?

Thanks in advance.

Regards
Janne



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2016-10-31 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 13:07 Janne Heß [this message]
2016-11-01  5:13 ` Building and integrating CorebootPayloadPkg Scott Duplichan

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=de2bc234-28eb-0cd8-aa44-ab69807e62a7@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