Re: coreboot meets apollolake

[Christian Gmeiner]

Hi
> Hi,
>
> I do not see anything obviously wrong with your configuration.
> Does the flash you use is 16mb or 8mb? IFD defines its own regions and FMAP must match IFD.

The flash is 8mb. If IFD gets dump with ifdtool then I have this:

00000000:00000fff fd
 00001000:00100fff res1
 00101000:0010ffff pd
 00110000:007fffff bios
> One common issue is that people have IFD that uses 16mb and use FMAP that uses 8mb.
> you can find some sample ifds in mainboard/intel/leafhill

ifds == *.fmd file that gets processed?
> > Afterwards we tried to open the aforementioned coreboot.rom in
> > FIT.exe. This was not possible however as the tool gave the error
>
> This sounds like image was not stitched correctly, which is probably the root cause of the problem.

If I fit.exe could be more verbose about the problem I would knew where to dig.
> Unfortunately I do not have time to help you debug this issue.
>
> My only recommendation would be to post on coreboot mailing list https://www.coreboot.org/Mailinglist
> Please post there, somebody will help you out.

Lets hope for the best.
> Hope that helps.
> Andrey
> On Tue, Jan 15, 2019 at 3:52 AM Christian Gmeiner  wrote:
> > Hi Andrey
> >
> > Me and a colleague of mine are busy replacing the stock vendor BIOS on
> > a board our employer gave us with coreboot. The board is equipped with
> > an Apollolake CPU.
> >
> > I have found your presentation regarding coreboot and Apollolake
> > (hxxps://www.coreboot.org/images/2/23/Apollolake_SoC.pdf) and did run
> > into some problems.
> >
> > Let me give you a quick outline of what we did:
> >
> > We took an image from the stock vendor BIOS, removed the OEM signing
> > stuff. We then replaced this with a key pair we created and were able
> > to boot it.
> >
> > Attached to this email you can find the settings XML file we created
> > in the process.
> >
> > We then took the outimage.bin created by the FIT.exe tool and
> > configured it as the IFWI in the coreboot build process, as can be
> > seen below:
> >
> > CONFIG_IFD_BIN_PATH="3rdparty/blobs/mainboard/$(MAINBOARDDIR)/descriptor.bin"
> > CONFIG_NEED_IFWI=y
> > CONFIG_IFWI_FMAP_NAME="IFWI_CORE"
> > CONFIG_IFWI_FILE_NAME="3rdparty/blobs/mainboard/$(CONFIG_MAINBOARD_DIR)/ifwi.bin"
> > CONFIG_HAVE_IFD_BIN=y
> >
> > We also took the first 4k from the image as the "descriptor.bin".
> >
> > The fmd file we came up with is visible below.
> >
> > 00000000:00000fff fd
> > 00001000:00100fff res1
> > 00101000:0010ffff pd
> > 00110000:007fffff bios
> >
> > FLASH 8M {
> >         SI_DESC@0x0 0x1000
> >         DEVICE_EXTENSION@0x1000 0x10EFFF
> >         IFWI@0x110000 0x6f0000 {
> >                 IFWI_CORE@0x0 0x2ff000
> >                 FMAP@0x2FF000 0x1000
> >                 RW_MRC_CACHE@0x300000 0x10000
> >                 COREBOOT(CBFS)@0x310000 0x100000
> >                 UNUSED_HOLE
> >                 NOT_MEMORY_MAPPED@0x6B0000 0x40000
> >         }
> > }
> >
> > When generating a coreboot.rom image and flashing it to our BIOS flash
> > chip, it wouldn't boot though. We didn't see any post codes at all, so
> > the image is likely not even executed.
> >
> > Afterwards we tried to open the aforementioned coreboot.rom in
> > FIT.exe. This was not possible however as the tool gave the error
> >
> > Error 30: Failed to decompose Full Image.
> > Error 10: Failed to open with processed commands.
> > Unable to open file: U:\Apollo Lake Intel(R) TXE
> > 3.1.60.2280\Tools\FIT\WINDOWS\coreboot.bin. Reverting to default
> > configuration.
> >
> > It seems that we made an error in process. Would you be so kind to
> > have a look at this and point us in the right direction?
> >
> > https://christian-gmeiner.info