public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Cameron Craig <Cameron.Craig@exterity.com>
To: "'You, Benjamin'" <benjamin.you@intel.com>,
	"'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>
Subject: Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
Date: Thu, 30 Nov 2017 14:11:43 +0000	[thread overview]
Message-ID: <ce105ab51f2d451d8f0b7f7ad6281fc9@exterity.com> (raw)
In-Reply-To: <E748835C6D8DB54B8E8AF33091ECC57C62130F25@SHSMSX103.ccr.corp.intel.com>

Hi Benjamin,

Thanks for the pointers.

>> 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.

Network boot/PXE is now functioning, I just had to link in the UNDI driver in edk2 rather than loading via USB.

It's just the serial boot menu I'm trying to get working now.

>BTW, please use debug build for Coreboot Payload, such that debug
>information can be shown in serial console from the very early stage in the
>Payload's execution. This would help validating the functioning of serial.

Interestingly, my debug build was complaining that it ran out of room when attempting to fit everything in the UEFIPAYLOAD.
When I strip out the network additions and keep DEBUG on, Tianocore builds but errors at runtime:
```
Failed to add memory space :0xFEE00000 0x100000
```
I'm guessing I can increase the size of a region somewhere to avoid this issue?

>> 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.

I get serial output from coreboot and edk2, just not the boot menu.

>> 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.

That's not happening in my case. I'm currently trying to get the debug build to run.

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



______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

  reply	other threads:[~2017-11-30 14:07 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
2017-11-25 16:21   ` You, Benjamin
2017-11-30 14:11     ` Cameron Craig [this message]
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=ce105ab51f2d451d8f0b7f7ad6281fc9@exterity.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