[coreboot] UEFI Payload in coreboot for Intel Minnowboard or Bayley bay

[Mayuri Tendulkar]

Hi Martin

Yes, I have looked at below links and working on it , but facing some issues both in windows and Linux.
Anyway hopefully will sort on those issues soon.

Keep me posted once u integrate payload in coreboot.

Regards
Mayuri

-----Original Message-----
From: Martin Roth [mailto:gaumless at gmail.com]
Sent: 16 May 2016 20:43
To: Mayuri Tendulkar <mayuri.tendulkar at aricent.com>
Cc: Zoran Stojsavljevic <zoran.stojsavljevic at gmail.com>; coreboot at coreboot.org
Subject: Re: [coreboot] UEFI Payload in coreboot for Intel Minnowboard or Bayley bay

Hi Mayuri,
  As of right now, the coreboot build doesn't have a way to build tianocore/CorebootPayloadPkg into coreboot automatically, but I'm working on integrating it.  I had hoped to have my initial push ready last week, but didn't get it finished.

That said, it's not difficult to build it outside of coreboot, then add it as an elf payload.

In case you haven't found these pages with the instructions, here they are:
https://github.com/tianocore/tianocore.github.io/wiki/Using-EDK-II-with-Native-GCC
https://svn.code.sf.net/p/edk2/code/trunk/edk2/CorebootPayloadPkg/BuildAndIntegrationInstructions.txt

Last time I tested, I had some issues with the debug version of the rom hitting an assert and dying, but the release build booted successfully.

Martin

On Mon, May 16, 2016 at 6:29 AM, Mayuri Tendulkar <mayuri.tendulkar at aricent.com> wrote:
> Hi Zoran
>
>
>
> I have checked that site and downloaded EDK2 code. I am trying to
> build it on Linux but facing some issues.
>
> But if I generate payload file separately, I need to integrate it in
> coreboot separately.
>
>
>
> So I am checking if there is way to build the payload in coreboot itself.
>
>
>
> Regards
>
> Mayuri
>
>
>
> From: Zoran Stojsavljevic [mailto:zoran.stojsavljevic at gmail.com]
> Sent: 16 May 2016 17:57
> To: Mayuri Tendulkar <mayuri.tendulkar at aricent.com>
> Cc: coreboot at coreboot.org
> Subject: Re: [coreboot] UEFI Payload in coreboot for Intel Minnowboard
> or Bayley bay
>
>
>
> Hello Mayuri,
>
>
>
> You should check payload called: Tiano Core (true UEFI payload).
>
>
>
> Zoran
>
>
>
>
>
> On Mon, May 16, 2016 at 2:12 PM, Mayuri Tendulkar
> <mayuri.tendulkar at aricent.com> wrote:
>
> Hi
>
>
>
> Is there any mechanism to build UEFI payload directly in coreboot
> similar like seabios?
>
>
>
> Regards
>
> Mayuri
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying,
> altering, or disclosing the contents of this message. Aricent accepts
> no responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying,
> altering, or disclosing the contents of this message. Aricent accepts
> no responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
> --
> coreboot mailing list: coreboot at coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."