[coreboot] coreboot with GRUB2 for ARM Chromebook (veyron_jaq)

[Martin Wohlert]

Looking through the web I found some posts about GRUB2 is not ARM
compatible, but GRUB2 2.02 has ARM support. Now I also found this
https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB:

Both ARM and ARM64 are now supported in upstream GRUB - both are
available in the grub 2.02 betas, and included in several Linux
distributions. The ARM port supports U-Boot (but should shortly support
also UEFI), and the ARM64 port supports UEFI.

So officially u-boot and UEFI are supposed to work. But in the git
repository is also an arm_coreboot branch. But the make command always
fetches the HEAD branch which is 2.02 beta 3.

Maybe I need to edit the Makefile to use that arm_coreboot branch. Will
try that, but if anyone still has other ideas I will appreciate that.

Thanks
Martin

Am 19.12.2016 um 09:28 schrieb John Lewis:
> I don't think Grub2 is ARM compatible, so you will need to build another
> payload (uboot maybe). Others around here will have a better idea of how
> to achieve that but you should also look for documentation first to see
> how far you can get on your own.
> 
> Cheers,
> 
> John.
> 
> Sent from BlueMail <http://www.bluemail.me/r>
> On 19 Dec 2016, at 08:22, Martin Wohlert <martin at b-root-force.de
> <mailto:martin at b-root-force.de>> wrote:
> 
>     Hello everybody!
> 
>     I have a Chromebook (Medion Akoya S2013) which is the german version of
>     the Haier Chromebook 11 (veyron_jaq).
> 
>     And I fail to build the coreboot.
> 
>     Here what I've done so far (which you can reproduce yourself):
> 
>     1. like told me on https://www.coreboot.org/Build_HOWTO
>     $ git clone http://review.coreboot.org/p/coreboot
>     $ cd coreboot
>     $ git submodule update --init --checkout
> 
>     2. $ make menuconfig
>     There I only changed "Mainboard" > "Mainboard vendor" & "Mainboard
>     model" to Google / Haier Chromebook 11 (veyron_jaq). The ROM size of 4
>     MB is also correct. I read the flash chip and got a 4 MB image.
> 
>     3. Still in menuconfig I selected GRUB2 in "Payload" > "Add a Payload".
> 
>     4. $ make crosstools-arm
>     succeeded without errors
> 
>     5. $ make
>     Fails with error:
> 
>         HOSTCC    
>     cbfstool/xxhash.o
>         HOSTCC     cbfstool/linux_trampoline.o
>         HOSTCC     cbfstool/cbfs-payload-linux.o
>         HOSTCC     cbfstool/cbfstool (link)
>     Performing operation on 'COREBOOT' region...
>     Created CBFS (capacity = 4062936 bytes)
>     Performing operation on 'BOOTBLOCK' region...
>     W: Written area will abut bottom of target region: any unused space will
>     keep its current contents
>     Performing operation on 'COREBOOT' region...
>     Performing operation on 'COREBOOT' region...
>         CBFS       fallback/romstage
>     Performing operation on 'COREBOOT' region...
>         CBFS       fallback/ramstage
>     Performing operation on 'COREBOOT' region...
>         CBFS       config
>     Performing operation on 'COREBOOT' region...
>         CBFS       revision
>     Performing operation on 'COREBOOT' region...
>         CBFS       fallback/payload
>     Performing operation on 'COREBOOT' region...
>     Performing operation on 'COREBOOT' region...
>     ERROR: Ramstage region _ramstage overlapped by:
>     fallback/payload
>     make: *** [Makefile.inc:992: check-ramstage-overlaps] Error 1
> 
>     See full log here: https://files.b-root-force.de/coreboot.txt
> 
>     What I find a bit suspicious is the output:
>     ...
>     GRUB2 will be compiled with following components:
>     Platform: i386-coreboot
>     ...
>     Cause I am building for ARM.
> 
>     So, does anyone have an idea what I can try next?
> 
>     Kind regards
>     Martin
> 
>     -- 
>     coreboot mailing list: coreboot at coreboot.org
>     https://www.coreboot.org/mailman/listinfo/coreboot
> 
> 
>