From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.93; helo=mga11.intel.com; envelope-from=benjamin.you@intel.com; receiver=edk2-devel@lists.01.org Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (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 3E18421A10973 for ; Sat, 25 Nov 2017 08:17:02 -0800 (PST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Nov 2017 08:21:22 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,454,1505804400"; d="scan'208";a="177694125" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga005.jf.intel.com with ESMTP; 25 Nov 2017 08:21:22 -0800 Received: from fmsmsx118.amr.corp.intel.com (10.18.116.18) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sat, 25 Nov 2017 08:21:21 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx118.amr.corp.intel.com (10.18.116.18) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sat, 25 Nov 2017 08:21:21 -0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.218]) with mapi id 14.03.0319.002; Sun, 26 Nov 2017 00:21:19 +0800 From: "You, Benjamin" To: "You, Benjamin" , Cameron Craig , "'edk2-devel@lists.01.org'" Thread-Topic: [edk2] Enabling boot menu via serial & PXE boot in CorebootPayloadPkg Thread-Index: AdNlBD3q6DwwM9CkT6qbFZhY/CoH9AA90NYAAANAmTA= Date: Sat, 25 Nov 2017 16:21:18 +0000 Message-ID: References: <0d20f24d08a7499fb124769eb277a7bc@exterity.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiODU2YjljNDgtY2E1ZC00NjBkLTgxNjEtZjRiZmIzNTA3ZWQ0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJnNlRMY2hqRnNhdFZFZGI3OTVcL2FoeDJ3Wm52TEcwSzFKZVwvbmpPN2tUT2hHdXRram03QTZIZ0tvNXl1U2dnYUEifQ== dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 16:17:03 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Cameron, 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. Thanks, - ben > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Yo= u, > Benjamin > Sent: Saturday, November 25, 2017 11:25 PM > To: Cameron Craig ; 'edk2-devel@lists.01.org' > > Subject: Re: [edk2] Enabling boot menu via serial & PXE boot in > CorebootPayloadPkg >=20 > Hi Cameron, >=20 > CorebootPayloadPkg does support serial output as user interface. To enabl= e > serial, the CorebootPayloadPkg retrieves serial information from Coreboot > through CorebootModulePkg\Library\CbParseLib\CbParseLib.c =3D> > CbParseSerialInfo(), which is called by CorebootPayloadPkg\Library\ > PlatformHookLib\PlatformHookLib.c =3D> PlatformHookSerialPortInitialize()= , > which is in turn called by CorebootModulePkg\Library\BaseSerialPortLib165= 50 > \BaseSerialPortLib16550.c =3D=3D> SerialPortInitialize(). >=20 > Have you seen serial output info during Coreboot? If the answer is no, th= en > Coreboot should be tweaked. If the answer is yes, but you cannot see seri= al > output in Coreboot Payload, then probably the above call sequence needs t= o > 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. 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 b= e > automatically supported. >=20 > On networking, you might refer to the Minnow Board v3 source tree, at > https://github.com/tianocore/edk2-platforms/tree/devel-MinnowBoard3- > UDK2017 >=20 > 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. >=20 > Thanks, >=20 > - ben >=20 > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > > Cameron Craig > > Sent: Friday, November 24, 2017 5:16 PM > > To: 'edk2-devel@lists.01.org' > > Subject: [edk2] Enabling boot menu via serial & PXE boot in > CorebootPayloadPkg > > > > Hi all, > > > > I'm new to this list and new to edk2 integration. > > Currently I'm working on an Intel Leaf Hill CRB, attempting to produce = a > > coreboot payload consisting of a Tianocore EDKII UDK 2017 UEFI boot > manager. > > > > I have basic functionality, but a few useful features are currently mis= sing from > > my build: > > > > 1. User interface via serial. > > We will not have the luxury of a video output so need to be able to nav= igate > the > > boot menu etc. via serial. > > In an ideal world I would be looking for a Boolean value to toggle :) B= ut I > > imagine there might be a little more to it. > > > > 2. PXE Boot. > > So far I have sources and built an UNDI driver and pinged a local netwo= rk > device. > > I have also attempted to enable the necessary features for PXE boot [1]= . > > But I get an error message: > > ``` > > $ ipconfig > > MAC Address: > > Broadcast MAC: FF FF FF FF FF FF > > ipconfig: Locate protocol error: 'PXE base code protocol' > > ``` > > So I'm thinking some drivers are not being loaded? > > > > Any suggestions for enabling these features would be greatly appreciate= d. > > > > [1] https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg- > > Getting-Started-Guide -> FEATURES ENABLING > > > > 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 > > > > Exterity is a leading provider of IP Video and Digital Signage solution= s that > helps > > organizations to harness the power of video to communicate, educate and > > entertain. Our end-to-end solutions enable you to take TV and video con= tent > > directly from any source and manage its delivery, live or on demand, to= any > > connected device via your existing network. For more information or to > > schedule a product demonstration, contact Exterity on +44(0)1383 828 25= 0 or > > visit www.exterity.com > > > > Legal Notice > > Unless expressly stated otherwise, this message is confidential and may= be > > privileged. It is intended for the addressee(s) only. Access to this e-= mail by > > anyone else is unauthorized. If you are not an addressee, any disclosur= e or > > copying of the contents of this e-mail or any action taken (or not take= n) in > > reliance on it is unauthorized and may be unlawful. If you are not an a= ddressee, > > please inform the sender immediately. > > > > Exterity Limited is registered in Scotland under No. 225313 with its re= gistered > > office at Ridge Way, Hillend Industrial Park, Dalgety Bay, KY11 9JD. > > > > > > > _________________________________________________________________ > > _____ > > This email has been scanned by the Symantec Email Security.cloud servic= e. > > For more information please visit http://www.symanteccloud.com > > > _________________________________________________________________ > > _____ > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel