> On Nov 11, 2014, at 8:01 AM, Varad Gautam <varadgau...@gmail.com> wrote:
>
> Is there a way to dump a boot "log" into a file on the device during boot?
>
What do you mean by a boot “log”? Usually the DEBUG prints are sent to a serial
device. What configuration do you have?
> I've checked that the device path assigned to ConIn during runtime is
> same as the Pcd string supplied, but am not sure how to find if this
> path *is* the correct one. What determines the GUID used in
> `VenHw(Guid)` portion of a device path?
>
The GUID (UUID) defines what it means. It is an enumeration that can allocated
in a distributed way.
A quick git grep of the code shows that D3987D4B-971A-435F-8CAF-4967EB627241 is
the FILE_GUID for the EmbeddedPkg SerialDxe driver.
https://svn.code.sf.net/p/edk2/code/trunk/edk2/EmbeddedPkg/SerialDxe/SerialIo.c
SIMPLE_TEXT_OUT_DEVICE_PATH mDevicePath = {
{
{ HARDWARE_DEVICE_PATH, HW_VENDOR_DP, { sizeof (VENDOR_DEVICE_PATH), 0} },
EFI_CALLER_ID_GUID // Use the drivers GUID
},
{
{ MESSAGING_DEVICE_PATH, MSG_UART_DP, { sizeof (UART_DEVICE_PATH), 0} },
0, // Reserved
FixedPcdGet64 (PcdUartDefaultBaudRate), // BaudRate
FixedPcdGet8 (PcdUartDefaultDataBits), // DataBits
FixedPcdGet8 (PcdUartDefaultParity), // Parity (N)
FixedPcdGet8 (PcdUartDefaultStopBits) // StopBits
},
{ END_DEVICE_PATH_TYPE, END_ENTIRE_DEVICE_PATH_SUBTYPE, { sizeof
(EFI_DEVICE_PATH_PROTOCOL), 0 } }
};
Given VenHw(D3987D4B-971A-43
5F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenPcAnsi()
The SerialDxe driver is producing this bit on a handle:
VenHw(D3987D4B-971A-43 5F-8CAF-4967EB627241)/Uart(115200,8,N,1)
The terminal driver is produce via:
https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Universal/Console/TerminalDxe/
So the terminal driver should get connected by the BDS,
gBS->ConnectController() and the terminal driver should produce a child handle
the child handle will have the device path of the parent VenHw(D3987D4B-971A-43
5F-8CAF-4967EB627241)/Uart(115200,8,N,1), and the driver appends a node to
represent why the handle was created, VenPcAnsi().
Thanks,
Andrew Fish
This is an example from our debugger command to dump out GUIDs
(lldb) guid D3987D4B-971A-435F-8CAF-4967EB627241
SerialDxe = D3987D4B-971A-435F-8CAF-4967EB627241
SerialDxe = { 0xD3987D4B, 0x971A, 0x435F, { 0x8C, 0xAF, 0x49, 0x67, 0xEB, 0x62,
0x72, 0x41 } }
As you can see there is a string form for a GUID, and there is also a C
structure form. If you are searching the GUID you may need to grep for each
form.
The build also kicks out a cross references of the string form of the guid to
Cname. Look in your build output FV directory for the Guid.xref file. This is
how the debugger command knows about the GUID Cnames.
> Thanks,
> Varad
>
> On Thursday 06 November 2014 08:29 PM, Olivier Martin wrote:
>>
>> What I sometimes do when I have potential problem with EFI device
>> paths, I dump all the EFI device paths available.
>>
>> It is important they exactly match what you are expected to use.
>>
>>
>>
>>
>>
>> *From:*Varad Gautam [mailto:varadgau...@gmail.com]
>> *Sent:* 05 November 2014 14:01
>> *To:* edk2-devel@lists.sourceforge.net
>> *Subject:* Re: [edk2] BeagleBoneBlackPkg: Moving to Intel BDS
>>
>>
>>
>> I am now able to load the Intel BDS, but I'm having some trouble with
>> receiving console
>> input with ArmPlatformPkg BDS or Intel BDS. I've got
>>
>> gArmPlatformTokenSpaceGuid.PcdDefaultConOutPaths|L"VenHw(D3987D4B-971A-43
>> 5F-8CAF-4967EB627241)/Uart(115200,8,N,1)/VenPcAnsi()"
>> gArmPlatformTokenSpaceGuid.PcdDefaultConInPaths|L"VenHw(D3987D4B-971A-435F
>> -8CAF-4967EB627241)/Uart(115200,8,N,1)/VenPcAnsi()"
>>
>> as the default console paths [1], and have been digging around in
>> ArmPlatformPkg/Bds
>> to learn how the console devices are connected. The boot gets stuck at
>> the selection
>> prompt and does not register any input. Using the BeagleBoard BDS
>> (which connects
>> ConIn and ConOut by protocol guids rather than device paths [2]) works
>> alright. I need
>> some help to figure out how I can get ConIn working.
>>
>> [1]
>> https://github.com/varadgautam/edk2/blob/kern/TexasInstrumentsPkg/BeagleBoneBl
>> ackPkg/BeagleBoneBlackPkg.dsc#L309
>> [2]
>> https://github.com/varadgautam/edk2/blob/kern/TexasInstrumentsPkg/BeagleBoneBl
>> ackPkg/Bds/BdsEntry.c#L110
>>
>> Thanks,
>>
>> Varad
>>
>>
>>
>>
>>
>> On Tue, Oct 28, 2014 at 11:58 PM, Olivier Martin
>> <olivier.mar...@arm.com <mailto:olivier.mar...@arm.com>> wrote:
>>
>> I have not really checked the history and your recent changes in details.
>> But until recently Intel BDS was requiring SMBios support.
>> I sent a patch to fix this dependency:
>> https://github.com/tianocore/edk2/commit/6d5b88f372180dc3a8622fda19ae0ac1fb0
>> 76ae8
>> <https://github.com/tianocore/edk2/commit/6d5b88f372180dc3a8622fda19ae0ac1fb076ae8>
>>
>> I also added support for Intel BDS to ArmVirtualizationPkg (enabled by the
>> build flag INTEL_BDS).
>> You can easily see the Intel BDS requirements by looking for
>> 'INTEL_BDS' in
>> the DSC and FDF files of this platform:
>> https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/ArmVirtualizati
>> onPkg/ArmVirtualizationQemu.dsc
>> <https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/ArmVirtualizationPkg/ArmVirtualizationQemu.dsc>
>>
>> If you already have ArmPlatformPkg/Bds working on your platform, I would
>> recommend you to start with this implementation of PlatformBdsLib:
>> PlatformBdsLib|ArmPlatformPkg/Library/PlatformIntelBdsLib/PlatformIntelBdsLi
>> b.inf
>>
>>
>>
>>> -----Original Message-----
>>> From: Varad Gautam [mailto:varadgau...@gmail.com
>> <mailto:varadgau...@gmail.com>]
>>> Sent: 28 October 2014 17:57
>>> To: edk2-devel@lists.sourceforge.net
>> <mailto:edk2-devel@lists.sourceforge.net>
>>> Subject: [edk2] BeagleBoneBlackPkg: Moving to Intel BDS
>>>
>>> Hi,
>>>
>>> I'm configuring BeagleBoneBlackPkg [1] to use
>>> IntelFrameworkModulePkg/Universal/BdsDxe. The build, after adding the
>>> dependencies hangs at [2]. What does 291:`InstallProtocolInterface:
>>> 348C4D62-BFBD-4882-9ECE-C80BB1C4783B 0` mean? Is HiiDatabaseDxe
>>> expecting
>>> a VFR form to load? Or does this indicate a missing module dependency?
>>>
>>> [1]
>>> https://github.com/varadgautam/edk2/tree/kern/TexasInstrumentsPkg/Beagl
>>> eBoneBlackPkg
>>> [2] http://fpaste.org/145882/14517581/
>>>
>>> Thanks,
>>> Varad
>>>
>>
>>> -----------------------------------------------------------------------
>>
>>> -------
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.sourceforge.net
>> <mailto:edk2-devel@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.sourceforge.net <mailto:edk2-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
