From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Ashish Singhal <ashishsingha@nvidia.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Fmp Payload Header Usage
Date: Tue, 29 Jan 2019 21:42:34 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8B8B9DA@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <DM6PR12MB33245DCBD3807DFEF8C818E6BA970@DM6PR12MB3324.namprd12.prod.outlook.com>
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-
> bounces@lists.01.org] On Behalf Of Ashish Singhal
> Sent: Tuesday, January 29, 2019 1:09 PM
> To: Gao, Liming <liming.gao@intel.com>; Kinney, Michael
> D <michael.d.kinney@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
prev parent reply other threads:[~2019-01-29 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 21:09 Fmp Payload Header Usage Ashish Singhal
2019-01-29 21:42 ` Kinney, Michael D [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E92EE9817A31E24EB0585FDF735412F5B8B8B9DA@ORSMSX113.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox