Build from Windows
Coreboot firmware is most often built from the linux environment. Because many bios developers are more familiar with Windows than linux, it is useful to know how to build coreboot on a Windows system.
Setup the coreboot build environment (long method)
The gnu tools needed to build coreboot have already been ported to Windows. They must be downloaded, customized, and installed. Here are the steps:
- Download and install a native msys+mingw environment on your Windows computer.
- Build and install cross compile versions of binutils and gcc that run on Windows and target 32-bit x86 bare metal hardware.
Step 1 involves downloading and decompressing mingw and msys, both of which contain several components. See mingw.org for details. You may need to gather utilities and commands from various locations in order to end up with everything needed for building coreboot projects.
Step 2: Once msys+mingw is installed, download and build cross compiler versions of gcc and binutils that produce elf output for 32-bit x86. Use util/crossgcc/buildgcc for this purpose. Use msys.bat to start the msys+mingw environment, then execute these commands:
Administrator@M3A78 ~ $ mkdir /gcc450
Administrator@M3A78 ~ $ cd /gcc450/
Administrator@M3A78 /gcc450 $ /d/tmp/xgcc/coreboot/util/crossgcc/buildgcc Welcome to the coresystems cross toolchain builder v1.01 (May 18th, 2010)
Downloading tar balls ... * gmp-5.0.1.tar.bz2 (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
* mpfr-2.4.2.tar.bz2 (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
* mpc-0.8.2.tar.gz (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
* libelf-0.8.13.tar.gz (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
* gcc-core-4.5.0.tar.bz2 (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
* binutils-2.20.1.tar.bz2 (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
* gdb-7.1.tar.bz2 (downloading)SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = D:\tmp\xgcc\msys/etc/wgetrc
Downloaded tar balls ... ok Unpacking and patching ... * gmp-5.0.1.tar.bz2 * mpfr-2.4.2.tar.bz2 * mpc-0.8.2.tar.gz * libelf-0.8.13.tar.gz * gcc-core-4.5.0.tar.bz2 * binutils-2.20.1.tar.bz2 * gdb-7.1.tar.bz2 Unpacked and patched ... ok Building GMP 5.0.1 ... ok Building MPFR 2.4.2 ... ok Building MPC 0.8.2 ... ok Building libelf 0.8.13 ... ok Building binutils 2.20.1 ... ok Building GCC 4.5.0 ... ok Building GDB 7.1 ... ok Cleaning up... ok
You can now run your i386-elf cross toolchain from /gcc450/xgcc.
Setup the coreboot build environment (shortcut method)
Getting through steps 1 and 2 from scratch takes a bit of work. As a shortcut, a coreboot-ready msys+mingw is included in the sample project. Decompress the sample project into any directory on your Windows computer. Note: Avoid the use of spaces in the project path and directory name. In the top level of the sample project is directory msys. This is the complete coreboot-ready msys+mingw. The msys.bat file in this directory starts the msys+mingw build environment. Use the standard tool names (gcc, ld, as, ...) to generate output that targets the local Windows environment. To produce the i386-elf output used by coreboot, use the tools in the gcc452 directory. For example, gcc -c hello.c builds a Windows object, while /gcc452/xgcc/bin/i386-elf-gcc hello.c builds an i386-elf object.
In addition to the coreboot ready msys+mingw build environment, the sample project contains:
- coreboot directory. Replace this sample coreboot source code with the one you want to build.
- simnow directory. Sample helper files for testing the AMD Serengeti Cheetah (Fam10) project on the AMD simnow simulator.
- go.bat. This batch file sets up environment variables needed for cross compiling, and switches to the coreboot directory.
Build the coreboot project
Here are step-by-step instructions for building a coreboot based bios on a windows machine using the shortcut build environment setup method:
- 1. Decompress the sample project into any directory. Note: Avoid the use of spaces in the project path and directory name. Use 7-zip for decompression.
- 2. Replace the sample coreboot source code (rev 5775) with your own. The directory must be named coreboot.
- 3. Using Windows explorer, click on go.bat to start the build environment. It will look something like this:
Administrator@M3A78 /D/tmp/win-build-env-002/coreboot $ _
- 4. First, build the seabios payload:
$ cd ../seabios/seabios-for-coreboot
Administrator@M3A78 /D/tmp/win-build-env-002/seabios/seabios-for-coreboot $ make Compiling whole program out/ccode.16.s Compiling to assembler out/asm-offsets.s Generating offset file out/asm-offsets.h Compiling (16bit) out/code16.o Compiling whole program out/ccode32flat.o src/coreboot.c: In function 'ulzma': src/coreboot.c:329:9: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int' Compiling whole program out/code32seg.o Building ld scripts (version "0.6.1-20100928_165201-m3a78") Fixed space: 0xe05b-0x10000 total: 8101 slack: 2 Percent slack: 0.0% 16bit size: 37760 32bit segmented size: 2416 32bit flat size: 50752 Linking out/rom16.o Stripping out/rom16.strip.o Linking out/rom32seg.o Stripping out/rom32seg.strip.o Linking out/rom.o Prepping out/bios.bin Total size: 90928 Free space: 40144 Percent used: 69.4% (128KiB rom)
- 5. Now configure coreboot:
$ cd ../../coreboot
Administrator@M3A78 /D/tmp/win-build-env-002/coreboot $ make oldconfig
Answer the configuration questions. For this example, defaults were used for all questions except:
mainboard vendor : 3 AMD mainboard model : 9 Serengeti Cheetah (Fam10) rom chip size : 3 512 KB add a payload : 2 An ELF executable payload Payload path and filename: ../seabios/seabios-for-coreboot/out/bios.bin.elf
- 6. At the $ prompt, type make. After a few seconds, the build should complete:
CC cpu/x86/mtrr/mtrr.o CC cpu/x86/pae/pgtbl.o AR coreboot.a CC coreboot_ram.o CC coreboot_ram CBFS coreboot.rom PAYLOAD ../seabios/seabios-for-coreboot/out/bios.bin.elf (compression: LZMA) CBFSPRINT coreboot.rom
coreboot.rom: 512 kB, bootblocksize 2390, romsize 524288, offset 0x0 Alignment: 64 bytes
Name Offset Type Size fallback/romstage 0x0 stage 69016 fallback/coreboot_ram 0x10e00 stage 47261 fallback/payload 0x1c700 payload 45815 (empty) 0x27a40 null 359458
Administrator@M3A78 /D/tmp/win-build-env-002/coreboot $ _
The final bios image is in file coreboot\build\coreboot.rom:
Directory of D:\tmp\win-build-env-001\coreboot\build 09/03/10 12:23 PM 524,288 coreboot.rom
Test using simnow (optional, AMD projects only)
The AMD simnow application is a software simulation of an AMD processor and reference board. Its accuracy is impressive, allowing it to boot an unmodified bios and operating system. To test the bios, download and install the public version of AMD's simnow. This example uses version simnow-win64-4.6.2pub.exe, a recent public version for Windows. Note that simnow requires a 64-bit operating system. Add an environment variable named simnow that points to the directory where simnow is installed:
From Windows explorer, launch coreboot\simnow\simnow.bat. This will open 3 windows:
Optionally, setup a boot cd-rom, floppy, or hard disk image:
Now, start the simulation by clicking the 'Run Simulation' button.
Putty will capture serial debug messages:
After a few seconds, video will appear:
At this point, the simulation hesitates while waiting for a keyboard response. Press a key while the mouse cursor is in the simnow window to avoid the delay. Alternatively, modify keyboard.c.
Next, the seabios payload executes:
If the optional disk image was supplied, seabios will attempt to boot it:
Oops, some ACPI debugging is needed here...
Known problems with this demo
- The seabios PS/2 keyboard initialization is not reliable when run on the simnow target.
- Windows 7 bluescreen, above. This problem can be avoided by adding an I/O write to put the system into ACPI mode before giving control to Windows. Once this is done, another problem is encountered. Windows will stay at the animated startup logo for too long. Improperly reported interrupt routing is a possible cause.
Known problems with windows building
- Libncurses is not available, which prevents make menuconfig from building. Work-around: use make oldconfig instead.