Re: [edk2] Pacing UEFI Shell Application in firmware volume

Subject: Re: [edk2] Pacing UEFI Shell Application in firmware volume

From: "Brian J. Johnson" <>


Date: 2014-10-31 00:22:21

On 10/30/2014 03:10 PM, Scott Duplichan wrote:
> Calvin (Hao) Guan [] wrote:
> ]Hi,
> ]
> ]FDF file allows EFI application to be placed in firmware volume but I cant
> ]seem to find what to do with these apps if placed in the FV. Because they are
> ]apps, they wont be dispatched. How do I invoke such an application from the FV?
> ]
> ]Thanks,
> ]Calvin
> Hello Calvin,
> This question was asked earlier this year:
> I don't believe there is a mechanism to directly launch a UEFI app during boot.
> One reason might be that UEFI apps can use stdout/stdin, and those are might
> not be available if the UEFI shell is not running. There might be a way to
> automatically launch a shell and have it launch your app, then exit after the
> app exits, but I have never done that.

If you can build it as a driver rather than an app, you can arrange to 
have it run during build.  Or if you can put it on a file system such as 
a USB drive, you can set the shell as your default boot target, and 
write a startup.nsh script which launches your app when the shell starts.



    "There is the greatest practical benefit in making a few failures
     early in life."
                                            -- Thomas Henry Huxley

edk2-devel mailing list