[coreboot] Problems changing payload on Intel Leaf Hill

Tue Nov 7 08:32:50 CET 2017

Hi Mario, Cameron, coreboot folks,

Thank you all so much for the help!! I managed to get SeaBIOS to work
(technically it was running all along, there was just no output and hence
no evidence to believe it ran.)

As I mentioned previously, I am not running coreboot master branch, instead
using the Intel-distributed variant based on an outdated coreboot commit
(Apollo_Lake_CB_MR1). So my config might not be useful to all who are using
coreboot master. But it is attached nonetheless.

I had previously tried including the bxt_1003.dat, when this didn't work I
tried using vbt.dat, but I think I might have configured them in the wrong
places. It works when I include both.

Also, Craig, thanks! I previously used the wrong bootloader image to try
and extract the VBIOS with the UEFItool (tried using Intel's precompiled
coreboot image with UEFI payload, named "coreboot.release.SPI.Bx.Win.bin",
which does not contain any VBIOS image, for some reason). It does work when
I extract it from Intel's UEFI image, named
"APLI_IFWI_X64_R_113_40E_SPI.bin".

On my build, it was not necessary to manually update the CBFS locations for
SeaBIOS.

But it was necessary to update the MMIO mapping for debug UART output.
Brilliant, I would never have figured this out.

In which document do I find the MMIO mapping again? I think I did read it
at some point but it got lost between the mass of information! (I'm new to
Intel architecture, coreboot, all payloads, and bootloader development in
general! Massive learning curve, too much information to absorb at once!)

I suspect similar changes would be required to witness output from
Tianocore, will try that soon.

Thanks to all again, I really really appreciate it! (Would send virtual
beer by manner of thanks, is that acceptable?)

Tahnia

On Mon, Nov 6, 2017 at 11:32 AM, Scheithauer, Mario <
Mario.Scheithauer at siemens.com> wrote:

> Hi all,
>
>
>
> > •        Are you able to boot Yocto with the current combination you
> have?
>
> We haven’t tested Yocto, but we can boot a Lubuntu.
>
> > Where did you obtain a VBIOS file?
>
> Intel provides the VBIOS in its MRx packages for the CRBs. You need to
> contact Intel for this.
>
> > •        Is it specifically VBIOS, or is it a VBT.dat file? Or are you
> running SeaVGABIOS?
>
> I think you need a complete VBIOS bxt_1003.dat (64kB) for SeaBios.
>
> The vbt.dat (5kB) is need by GOP driver. But we haven’t done anything with
> that yet.
>
>
>
> Mario
>
>
>
>
>
> *Von:* Tahnia Lichtenstein [mailto:unlich at gmail.com]
> *Gesendet:* Freitag, 3. November 2017 13:46
> *An:* Scheithauer, Mario (DF MC MTS R&D SWRT 4); coreboot at coreboot.org
> *Betreff:* Re: [coreboot] Problems changing payload on Intel Leaf Hill
>
>
>
> Hi Mario,
>
>
>
> Thank you very much for sharing, that already helps a lot!! I can spot
> quite a lot of differences to my own build settings.
>
>
>
> I've been pursuing a Grub2 payload in the meantime (no success so far),
> will now return to SeaBIOS and try and incorporate the necessary changes
> you suggested.
>
>
>
> Just a couple of questions so far:
>
>    - Are you able to boot Yocto with the current combination you have?
>    - I have all the blobs around coreboot, except the VBIOS... I have
>    tried all the options in https://www.coreboot.org/VGA_support, but I
>    suspect the reference bootloader images provided by Intel does not use a
>    VBIOS file. I also cannot find a suitable VBIOS on Intel's website. (By the
>    way, thanks for the FIT decomposition tip, I did not know this was
>    possible... I took great pains to find the correct blobs on Intel's
>    website, would have been much easier to just use FIT!) Where did you obtain
>    a VBIOS file?
>    - Is it specifically VBIOS, or is it a VBT.dat file? Or are you
>    running SeaVGABIOS?
>
> Many thanks again!
>
>
>
> Best regards,
>
> Tahnia
>
>
>
> On Fri, Nov 3, 2017 at 2:01 PM, Scheithauer, Mario <
> Mario.Scheithauer at siemens.com> wrote:
>
>
> Hi Cameron,
>
> > Did you modify the FSP blobs at all?
> Yes, we made some adjustments for our mainboard (mc_apl1).
> But they shouldn’t play a decisive role (power states, PCIe settings).
>
> > The reason I ask is that my coreboot build hangs in the FspSiliconInit().
> Then you will get pretty far.
> We are currently still using the MR2 FSP package for APL-I.
> As IFWI template we use the BIOS version v178.10 for the CRBs.
> These components are provided by Intel.
> That’s it. The CRB should boot with this combination.
>
> Mario
>
> > -----Ursprüngliche Nachricht-----
> > Von: Cameron Craig [mailto:Cameron.Craig at exterity.com]
> > Gesendet: Freitag, 3. November 2017 11:51
> > An: Scheithauer, Mario (DF MC MTS R&D SWRT 4); ahW at n
> > Cc: coreboot at coreboot.org
> > Betreff: Re: [coreboot] Problems changing payload on Intel Leaf Hill
>
> >
> > Hi Mario,
> >
> > I've been attempting to build coreboot(master) for the Leaf Hill CRB,
> with no
> > success so far.
> >
> > Did you modify the FSP blobs at all?
> > I had a look at your config, the filenames "FSP_MR2_M_ECC_MOD" caught my
> > eye.
> >
> > The reason I ask is that my coreboot build hangs in the FspSiliconInit().
> >
> > Cheers,
> > Cameron
> >
> >
> >
> > Cameron Craig | Graduate Software Engineer | Exterity Limited
> > tel: +44 1383 828 250 | fax:  | mobile:
> > e: Cameron.Craig at exterity.com | w: www.exterity.com
> >
> >
> >
> > ____________________________________________________________________
> > __
> > This email has been scanned by the Symantec Email Security.cloud service.
> > For more information please visit http://www.symanteccloud.com
> > ____________________________________________________________________
> > __
> --
> coreboot mailing list: coreboot at coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20171107/9ef12df0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: coreboot_seabios_vga_working.config
Type: application/xml
Size: 17692 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20171107/9ef12df0/attachment.wsdl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: seabios.config
Type: application/xml
Size: 1617 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20171107/9ef12df0/attachment-0001.wsdl>