From: "You, Benjamin" <benjamin.you@intel.com>
To: Cameron Craig <Cameron.Craig@exterity.com>,
"'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>
Subject: Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
Date: Sat, 25 Nov 2017 15:25:03 +0000 [thread overview]
Message-ID: <E748835C6D8DB54B8E8AF33091ECC57C62130E90@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <0d20f24d08a7499fb124769eb277a7bc@exterity.com>
Hi Cameron,
CorebootPayloadPkg does support serial output as user interface. To enable
serial, the CorebootPayloadPkg retrieves serial information from Coreboot
through CorebootModulePkg\Library\CbParseLib\CbParseLib.c =>
CbParseSerialInfo(), which is called by CorebootPayloadPkg\Library\
PlatformHookLib\PlatformHookLib.c => PlatformHookSerialPortInitialize(),
which is in turn called by CorebootModulePkg\Library\BaseSerialPortLib16550
\BaseSerialPortLib16550.c ==> SerialPortInitialize().
Have you seen serial output info during Coreboot? If the answer is no, then
Coreboot should be tweaked. If the answer is yes, but you cannot see serial
output in Coreboot Payload, then probably the above call sequence needs to
be checked. If you do not have a debugger, one way to trace code flow is to
insert raw serial outputs in the code flow. This should be doable since
Coreboot already does serial output. Once the serial output functions
correctly in the Coreboot Payload, Boot Menu / UI through serial should be
automatically supported.
On networking, you might refer to the Minnow Board v3 source tree, at
https://github.com/tianocore/edk2-platforms/tree/devel-MinnowBoard3-UDK2017
Minnow Board v3 uses the same SOC as Leaf Hill. You might look at
Platform/BroxtonPlatformPkg/PlatformPkg.fdf file for a reference on which
components are used for network / PXE.
Thanks,
- ben
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Cameron Craig
> Sent: Friday, November 24, 2017 5:16 PM
> To: 'edk2-devel@lists.01.org' <edk2-devel@lists.01.org>
> Subject: [edk2] Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
>
> Hi all,
>
> I'm new to this list and new to edk2 integration.
> Currently I'm working on an Intel Leaf Hill CRB, attempting to produce a
> coreboot payload consisting of a Tianocore EDKII UDK 2017 UEFI boot manager.
>
> I have basic functionality, but a few useful features are currently missing from
> my build:
>
> 1. User interface via serial.
> We will not have the luxury of a video output so need to be able to navigate the
> boot menu etc. via serial.
> In an ideal world I would be looking for a Boolean value to toggle :) But I
> imagine there might be a little more to it.
>
> 2. PXE Boot.
> So far I have sources and built an UNDI driver and pinged a local network device.
> I have also attempted to enable the necessary features for PXE boot [1].
> But I get an error message:
> ```
> $ ipconfig
> MAC Address: <valid MAC addr>
> Broadcast MAC: FF FF FF FF FF FF
> ipconfig: Locate protocol error: 'PXE base code protocol'
> ```
> So I'm thinking some drivers are not being loaded?
>
> Any suggestions for enabling these features would be greatly appreciated.
>
> [1] https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg-
> Getting-Started-Guide -> FEATURES ENABLING
>
> Cheers,
> Cameron
>
>
> Cameron Craig | Graduate Software Engineer | Exterity Limited
> tel: +44 1383 828 250 | fax: | mobile:
> e: Cameron.Craig@exterity.com | w: www.exterity.com
>
> Exterity is a leading provider of IP Video and Digital Signage solutions that helps
> organizations to harness the power of video to communicate, educate and
> entertain. Our end-to-end solutions enable you to take TV and video content
> directly from any source and manage its delivery, live or on demand, to any
> connected device via your existing network. For more information or to
> schedule a product demonstration, contact Exterity on +44(0)1383 828 250 or
> visit www.exterity.com
>
> Legal Notice
> Unless expressly stated otherwise, this message is confidential and may be
> privileged. It is intended for the addressee(s) only. Access to this e-mail by
> anyone else is unauthorized. If you are not an addressee, any disclosure or
> copying of the contents of this e-mail or any action taken (or not taken) in
> reliance on it is unauthorized and may be unlawful. If you are not an addressee,
> please inform the sender immediately.
>
> Exterity Limited is registered in Scotland under No. 225313 with its registered
> office at Ridge Way, Hillend Industrial Park, Dalgety Bay, KY11 9JD.
>
>
> _________________________________________________________________
> _____
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> _________________________________________________________________
> _____
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-11-25 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 9:15 Enabling boot menu via serial & PXE boot in CorebootPayloadPkg Cameron Craig
2017-11-25 15:25 ` You, Benjamin [this message]
2017-11-25 16:21 ` You, Benjamin
2017-11-30 14:11 ` Cameron Craig
2017-12-01 0:31 ` You, Benjamin
2017-12-01 10:23 ` Cameron Craig
2017-12-01 10:26 ` Cameron Craig
2017-12-02 3:02 ` You, Benjamin
2017-12-04 15:29 ` Cameron Craig
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=E748835C6D8DB54B8E8AF33091ECC57C62130E90@SHSMSX103.ccr.corp.intel.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