From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9D53A81E02 for ; Mon, 14 Nov 2016 10:57:58 -0800 (PST) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id AFE933D957; Mon, 14 Nov 2016 18:58:02 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-50.phx2.redhat.com [10.3.116.50]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id uAEIw12Z007360; Mon, 14 Nov 2016 13:58:02 -0500 To: =?UTF-8?Q?Janne_He=c3=9f?= , edk2-devel@ml01.01.org References: <16e73134-0917-5615-f1d8-93f9119f88ae@gmail.com> From: Laszlo Ersek Message-ID: <5b905333-5b86-9a72-f277-61071a2594d3@redhat.com> Date: Mon, 14 Nov 2016 19:58:00 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <16e73134-0917-5615-f1d8-93f9119f88ae@gmail.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Mon, 14 Nov 2016 18:58:02 +0000 (UTC) Subject: Re: Configuring Tianocore Logging X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 18:57:58 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 is the documentation. Thanks Laszlo