public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@nxp.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
	Pankaj Bansal <pankaj.bansal@nxp.com>
Subject: Re: Persistent Variable Storage and PlatformBootTimeOut
Date: Tue, 6 Sep 2016 12:20:19 +0100	[thread overview]
Message-ID: <CAKv+Gu_h-Ue4CyUQusbKtSFasm06Ar9joVa8UZ+uJxZaAuU7Cg@mail.gmail.com> (raw)
In-Reply-To: <AM4PR0401MB22895995BACB5D8C8436102488F90@AM4PR0401MB2289.eurprd04.prod.outlook.com>

On 6 September 2016 at 12:13, Bhupesh Sharma <bhupesh.sharma@nxp.com> wrote:
> Hi EDK2 experts,
>
> We have recently added the support for storing UEFI run-time variables on underlying NOR
> Flash slave on our ARMV8 NXP board.
>
> We are successfully able to change the values of variables like boot-order using the latest
> MdeModulePkg BDS:
>
>         MdeModulePkg/Universal/BdsDxe/BdsDxe.inf
>
> and retrieve them on next board boot.
>
> While this works almost on all the places, we see that the Auto Boot Time we have set using the
> following PCD:
>         gEfiMdePkgTokenSpaceGuid.PcdPlatformBootTimeOut|20
>
> Doesn't work when one enters the BIOS screen and enters the Boot Maintenance Manager to change this
> value from say 20 to 10.
>
> On the next board boot, the PlatformBootTimeOut value is still 20.
>
> The same issue is replicable on latest EDK2 (master branch) on qemu for aarch64.
>
> Is this a known issue or are we missing something here?
>

You should declare it as

[PcdsDynamicHii.common.DEFAULT]
  gEfiMdePkgTokenSpaceGuid.PcdPlatformBootTimeOut|L"Timeout"|gEfiGlobalVariableGuid|0x0|10
# Variable: L"Timeout"

to connect the dynamic PCD to the EFI variable.


      reply	other threads:[~2016-09-06 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 11:13 Persistent Variable Storage and PlatformBootTimeOut Bhupesh Sharma
2016-09-06 11:20 ` Ard Biesheuvel [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=CAKv+Gu_h-Ue4CyUQusbKtSFasm06Ar9joVa8UZ+uJxZaAuU7Cg@mail.gmail.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