public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Janne Heß" <jannehess@gmail.com>, edk2-devel@ml01.01.org
Subject: Re: Configuring Tianocore Logging
Date: Mon, 14 Nov 2016 19:58:00 +0100	[thread overview]
Message-ID: <5b905333-5b86-9a72-f277-61071a2594d3@redhat.com> (raw)
In-Reply-To: <16e73134-0917-5615-f1d8-93f9119f88ae@gmail.com>

On 11/14/16 19:27, Janne Heß wrote:
> Hello everyone,
> 
> I'm currently trying to get Tianocore running as a coreboot payload, but
> it just resets the machine, so I tried to increase the log level.
> As a EDK II newbie, it's really hard to figure out where to raise the
> log level.
> I found  the Debug FAQ which tells me about PcdDebugPropertyMask and
> PcdDebugPrintErrorLevel.
> So I looked the values up and found that they are set in MdePkg/MdePkg.dsc.
> After setting these to 0xff... I rebuilt but there is still no output at
> all. I also switched the TARGET to DEBUG, but it doesn't help.
> So what am I missing here?
> I tried building both Ovmf and the Coreboot payload, but neither of them
> logs anything.

Generally:

You need a DebugLib library instance that logs to a device that you can
observe.

The most common such DebugLib instance is

MdePkg/Library/BaseDebugLibSerialPort/BaseDebugLibSerialPort.inf

which writes to the serial port.

In turn that depends on "SerialPortLib", which is really
platform-specific. Two examples are:

PcAtChipsetPkg/Library/SerialIoLib/SerialIoLib.inf
ArmPlatformPkg/Library/PL011SerialPortLib/PL011SerialPortLib.inf

Specifically:

- For capturing the OVMF debug log with QEMU, please look at OvmfPkg/README.

- For CoreBoot*Pkg, I guess
<https://github.com/tianocore/tianocore.github.io/wiki/Coreboot_UEFI_payload>
is the documentation.

Thanks
Laszlo



      reply	other threads:[~2016-11-14 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 18:27 Configuring Tianocore Logging Janne Heß
2016-11-14 18:58 ` Laszlo Ersek [this message]

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=5b905333-5b86-9a72-f277-61071a2594d3@redhat.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