From: Nikolay Bodunov <nikolay.bodunov@gmail.com>
To: edk2-devel@lists.01.org, laurie.jarlstrom@intel.com
Subject: HII UEFI driver from Intel's lab training crashes
Date: Tue, 14 Mar 2017 19:55:16 +0300 [thread overview]
Message-ID: <CANqPu1+pwG1KBc6hT=meX967FTHHzYAC9PFAo4ft16o753SXLQ@mail.gmail.com> (raw)
Hello
I tried to repeat creating HII UEFI driver (well-known MyWizardDriver) in
Nt32Pkg, as in Intel's July 2013 training lab 9, from Laurie Jarlstrom, but
after compilation and run under qemu-ovmf my driver craches. I cannot make
it work. Win7x64 platform.
Messages that I got in command window:
ASSERT!: [HiiDatabase] c:\fw\edk2\MdePkg\Library\BaseLib\String.c (172):
String != ((void *) 0)
Failed to execute command
.\SecMain [c:\fw\edk2\Build\NT32IA32\DEBUG_VS2010x86\IA32]
What I tried (of course, I added [Components.IA32] in Nt32Pkg.dsc file):
1. Compile it under VS2010 and VS2015. Same results.
2. DEBUG and RELEASE versions. Same results.
3. Installed VS2010SP1. Same results (BTW, to avoid "Unresolved symbol"
messages in build process all that required is to run build in VS2010
command window, not VS2010 64-bit command window).
4. My files created during the lab and files from the lab that were already
provided by Intel. Same results.
5. EDK II source tree included in the lab materials and latest version from
github. Same results.
All .NET frameworks were removed from computer, then framework 4.0 was
installed again.
Before that, I compiled and run same driver, without real actions with HII
(templates only fron DriverWizard, from previous lesson 8). All worked
good, before I started to work with newly created HII options.
Could anyone help? I suppose it's typical error beause of some tools
settings, because I saw training video on youtube where all were worked
good on Laurie's PC.
--
With best regards,
Nikolay Bodunov
next reply other threads:[~2017-03-14 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 16:55 Nikolay Bodunov [this message]
2017-03-15 2:19 ` HII UEFI driver from Intel's lab training crashes Dong, Eric
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='CANqPu1+pwG1KBc6hT=meX967FTHHzYAC9PFAo4ft16o753SXLQ@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