mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-09-23 16:11:54 +00:00
e74d0ec80b
Add information about memory usage when U-Boot is started from coreboot. This is useful when debugging. Also, since coreboot takes a chunk of memory in the middle of SDRAM for use by PCI devices, it can help avoid overwriting this with a loaded kernel by accident. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
73 lines
3 KiB
ReStructuredText
73 lines
3 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0+
|
|
.. sectionauthor:: Bin Meng <bmeng.cn@gmail.com>
|
|
|
|
Coreboot
|
|
========
|
|
|
|
Build Instructions for U-Boot as coreboot payload
|
|
-------------------------------------------------
|
|
Building U-Boot as a coreboot payload is just like building U-Boot for targets
|
|
on other architectures, like below::
|
|
|
|
$ make coreboot_defconfig
|
|
$ make all
|
|
|
|
Test with coreboot
|
|
------------------
|
|
For testing U-Boot as the coreboot payload, there are things that need be paid
|
|
attention to. coreboot supports loading an ELF executable and a 32-bit plain
|
|
binary, as well as other supported payloads. With the default configuration,
|
|
U-Boot is set up to use a separate Device Tree Blob (dtb). As of today, the
|
|
generated u-boot-dtb.bin needs to be packaged by the cbfstool utility (a tool
|
|
provided by coreboot) manually as coreboot's 'make menuconfig' does not provide
|
|
this capability yet. The command is as follows::
|
|
|
|
# in the coreboot root directory
|
|
$ ./build/util/cbfstool/cbfstool build/coreboot.rom add-flat-binary \
|
|
-f u-boot-dtb.bin -n fallback/payload -c lzma -l 0x1110000 -e 0x1110000
|
|
|
|
Make sure 0x1110000 matches CONFIG_SYS_TEXT_BASE, which is the symbol address
|
|
of _x86boot_start (in arch/x86/cpu/start.S).
|
|
|
|
If you want to use ELF as the coreboot payload, change U-Boot configuration to
|
|
use CONFIG_OF_EMBED instead of CONFIG_OF_SEPARATE.
|
|
|
|
To enable video you must enable these options in coreboot:
|
|
|
|
- Set framebuffer graphics resolution (1280x1024 32k-color (1:5:5))
|
|
- Keep VESA framebuffer
|
|
|
|
At present it seems that for Minnowboard Max, coreboot does not pass through
|
|
the video information correctly (it always says the resolution is 0x0). This
|
|
works correctly for link though.
|
|
|
|
64-bit U-Boot
|
|
-------------
|
|
|
|
In addition to the 32-bit 'coreboot' build there is a 'coreboot64' build. This
|
|
produces an image which can be booted from coreboot (32-bit). Internally it
|
|
works by using a 32-bit SPL binary to switch to 64-bit for running U-Boot. It
|
|
can be useful for running UEFI applications, for example.
|
|
|
|
This has only been lightly tested.
|
|
|
|
|
|
Memory map
|
|
----------
|
|
|
|
========== ==================================================================
|
|
Address Region at that address
|
|
========== ==================================================================
|
|
ffffffff Top of ROM (and last byte of 32-bit address space)
|
|
7a9fd000 Typical top of memory available to U-Boot
|
|
(use cbsysinfo to see where memory range 'table' starts)
|
|
10000000 Memory reserved by coreboot for mapping PCI devices
|
|
(typical size 2151000, includes framebuffer)
|
|
1920000 CONFIG_SYS_CAR_ADDR, fake Cache-as-RAM memory, used during startup
|
|
1110000 CONFIG_SYS_TEXT_BASE (start address of U-Boot code, before reloc)
|
|
110000 CONFIG_BLOBLIST_ADDR (before being relocated)
|
|
100000 CONFIG_PRE_CON_BUF_ADDR
|
|
f0000 ACPI tables set up by U-Boot
|
|
(typically redirects to 7ab10030 or similar)
|
|
500 Location of coreboot sysinfo table, used during startup
|
|
========== ==================================================================
|