From: "Tomas Pilar (tpilar)" <tpilar@solarflare.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Problems with FDF for OptionROM when using GCC
Date: Tue, 2 Oct 2018 14:09:47 +0100 [thread overview]
Message-ID: <a46d0ca0-41cf-6a4e-0458-204b18152137@solarflare.com> (raw)
Hi,
I am trying to move the OptionROM flash specification in my package to a FDF file. I use the following snippet to define the OptionROM:
[Defines]
FDF_VERSION = 0x00000100
FDF_SPECIFICATION = 0x0001001B
[OptionROM.SfcNicDriver]
INF USE = $(ARCH) SfcPkg/SfcNicDriver/SfcNicDriver.inf {
PCI_VENDOR_ID = 0x1924
PCI_DEVICE_ID = 0x0903
PCI_CLASS_CODE = 0x02 # Network Controller
PCI_REVISION = 0x00 # Vendor defined Revision ID
PCI_COMPRESS = TRUE
}
which results in a
error F003: Don't Find common rule RULE.COMMON.UEFI_DRIVER for INF SfcPkg/SfcNicDriver/SfcNicDriver.inf
so then I cargo cult copy an example rule from FDF:
[Rule.Common.UEFI_DRIVER]
FILE DRIVER = $(NAMED_GUID) {
COMPRESS PI_STD {
GUIDED {
PE32 PE32 $(INF_OUTPUT)/$(MODULE_NAME).efi
UI STRING = "$(MODULE_NAME)" Optional
VERSION STRING = "$(INF_VERSION)" Optional BUILD_NUM=$(BUILD_NUMBER)
}
}
}
which results in the following error:
GenFds.py...
: error C0DE: Tools code failure
Please send email to edk2-devel@lists.01.org for help, attaching following call stack trace!
Traceback (most recent call last):
File "/usr/lib64/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/local/sauce/uefi/BuildTree/BaseTools/Source/Python/GenFds/GenFds.py", line 735, in <module>
r = main()
File "/local/sauce/uefi/BuildTree/BaseTools/Source/Python/GenFds/GenFds.py", line 356, in main
RaiseError=False
File "/home/tp/sauce/uefi/BuildTree/BaseTools/Source/Python/Common/EdkLogger.py", line 203, in error
raise FatalError(ErrorCode)
Common.BuildToolError.FatalError: 49374
build.py...
: error 7000: Failed to execute command
GenFds -f /home/tp/sauce/uefi/BuildTree/SfcPkg/SfcPkg.fdf --conf=/home/tp/sauce/uefi/BuildTree/Conf -o /home/tp/sauce/uefi/BuildTree/Build/SfcPkg/DEBUG_GCC49 -t GCC49 -b DEBUG -p /home/tp/sauce/uefi/BuildTree/SfcPkg/SfcPkg.dsc -a X64 -D "EFI_SOURCE=/home/tp/sauce/uefi/BuildTree/EdkCompatibilityPkg" -D "EDK_SOURCE=/home/tp/sauce/uefi/BuildTree/EdkCompatibilityPkg" -D "TOOL_CHAIN_TAG=GCC49" -D "TOOLCHAIN=GCC49" -D "TARGET=DEBUG" -D "FAMILY=GCC" -D "WORKSPACE=/home/tp/sauce/uefi/BuildTree" -D "EDK_TOOLS_PATH=/home/tp/sauce/uefi/BuildTree/BaseTools" -D "ARCH=X64" -D "ECP_SOURCE=/home/tp/sauce/uefi/BuildTree/EdkCompatibilityPkg" [/local/sauce/uefi/BuildTree]
- Failed -
Build end time: 14:07:26, Oct.02 2018
Build total time: 00:00:04
Help?
next reply other threads:[~2018-10-02 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 13:09 Tomas Pilar (tpilar) [this message]
2018-10-02 13:43 ` Problems with FDF for OptionROM when using GCC Tomas Pilar (tpilar)
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=a46d0ca0-41cf-6a4e-0458-204b18152137@solarflare.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