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.120; helo=mga04.intel.com; envelope-from=michael.d.kinney@intel.com; receiver=edk2-devel@lists.01.org Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (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 3E02D211BD5F8 for ; Tue, 29 Jan 2019 13:42:36 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jan 2019 13:42:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,538,1539673200"; d="scan'208";a="129570409" Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by FMSMGA003.fm.intel.com with ESMTP; 29 Jan 2019 13:42:35 -0800 Received: from orsmsx121.amr.corp.intel.com (10.22.225.226) by ORSMSX103.amr.corp.intel.com (10.22.225.130) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 29 Jan 2019 13:42:34 -0800 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.240]) by ORSMSX121.amr.corp.intel.com ([169.254.10.77]) with mapi id 14.03.0415.000; Tue, 29 Jan 2019 13:42:34 -0800 From: "Kinney, Michael D" To: Ashish Singhal , "Gao, Liming" , "Kinney, Michael D" CC: "edk2-devel@lists.01.org" Thread-Topic: Fmp Payload Header Usage Thread-Index: AdS4FtSd6L94mGW3StadDBM18b73AQAAp7Lg Date: Tue, 29 Jan 2019 21:42:34 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.22.254.140] MIME-Version: 1.0 Subject: Re: Fmp Payload Header Usage X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2019 21:42:36 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Ashish, You do need to use the standalone tool called GenerateCapsule to convert a payload to a UEFI Capsule. Here is an example: https://github.com/tianocore/edk2/blob/master/Vlv2TbltDevicePkg/Feature/Cap= sule/GenerateCapsule/GenCapsuleMinnowMax.bat You can customize this script for your platform. This script is for dev/debug purposes only for use on a local dev system. It supports different keys and tools to generate a UEFI Capsule. You can simplify it for a specific tool/key option. You can integrate this into the standard build process by adding a script to the DSC file as a post build step. https://github.com/tianocore/edk2/blob/master/Vlv2TbltDevicePkg/PlatformCap= sule.dsc POSTBUILD =3D Vlv2TbltDevicePkg/Feature/Capsule/GenerateCapsule/GenCapsul= eAll.bat This specific platform has some extra steps that need to be=20 performed after the normal build of the FW image before the capsule is generated, so a 2nd DSC/FDF file is used. If you do not have=20 any extra steps, then you can add the POSTBUILD statement to the [Defines] section of your platform DSC file. Best regards, Mike > -----Original Message----- > From: edk2-devel [mailto:edk2-devel- > bounces@lists.01.org] On Behalf Of Ashish Singhal > Sent: Tuesday, January 29, 2019 1:09 PM > To: Gao, Liming ; Kinney, Michael > D > Cc: edk2-devel@lists.01.org > Subject: [edk2] Fmp Payload Header Usage >=20 > Hello Michael/Liming, >=20 > I am trying to use FmpDevicePkg for FMP based capsule > update and am failing in FmpPayloadHeaderLib while > verifying FMP payload header. I am building capsule and > payload using FDF file itself and not calling Capsule > tools explicitly from basetools. Is there a special > build flag I need to provide to add FMP payload header > to my payload? >=20 > Thanks > Ashish >=20 > -------------------------------------------------------- > --------------------------- > This email message is for the sole use of the intended > recipient(s) and may contain > confidential information. Any unauthorized review, use, > disclosure or distribution > is prohibited. If you are not the intended recipient, > please contact the sender by > reply email and destroy all copies of the original > message. > -------------------------------------------------------- > --------------------------- > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel