From: scott.iveland at calix.com <scott.iveland@calix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot efi
Date: Tue, 9 Aug 2016 11:12:19 -0700 [thread overview]
Message-ID: <57AA1D03.4090808@calix.com> (raw)
I am trying to use u-boot-efi on a board that has an Intel D-1500 series
processor and 64-bit UEFI ROM.
As per the information in doc/README.efi I built a u-boot-payload.efi
with CONFIG_EFI_STUB_64BIT and installed it onto a USB drive I am
booting with.
The UEFI loads/runs the u-boot but quickly goes into the weeds. I have
very limited debug facilities as this is a 3rd party board.
I was able to track down the failure to the following using calls to
post_code():
lib/efi/efi_stub.c:efi_main()
lib/efi/efi_stub.c:jump_to_uboot()
arch/x86/cpu/call32.S:cpu_call32()
arch/x86/cpu/start.S:start()
common/init/board_init.c:board_init_f_alloc_reserve() -> fails
upon return.
This is the first "call" instruction after control is transferred to the
start() of the 32-bit u-boot image.
I also tried adding a call to a do-nothing function and the results were
the same (failure upon return).
The CPU goes the weeds and I guess it is in some exception code (no JTAG
debugger available).
This is the first time I have used u-boot in this mode and my first time
working with the x86 architecture.
Any suggestions would be most appreciated.
Thanks,
Scott
reply other threads:[~2016-08-09 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=57AA1D03.4090808@calix.com \
--to=scott.iveland@calix.com \
--cc=u-boot@lists.denx.de \
/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