Is there a way to dump a boot "log" into a file on the device during boot?
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? 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
