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/Capsule/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/PlatformCapsule.dsc POSTBUILD = Vlv2TbltDevicePkg/Feature/Capsule/GenerateCapsule/GenCapsuleAll.bat This specific platform has some extra steps that need to be 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 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- > boun...@lists.01.org] On Behalf Of Ashish Singhal > Sent: Tuesday, January 29, 2019 1:09 PM > To: Gao, Liming <liming....@intel.com>; Kinney, Michael > D <michael.d.kin...@intel.com> > Cc: edk2-devel@lists.01.org > Subject: [edk2] Fmp Payload Header Usage > > Hello Michael/Liming, > > 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? > > Thanks > Ashish > > -------------------------------------------------------- > --------------------------- > 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 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel