Difference between revisions of "Minnowboard:MinnowMaxCoreboot"
Darknighte (talk | contribs) m (→FSP) |
(Updated build instructions to current situation) |
||
Line 4: | Line 4: | ||
* gcc | * gcc | ||
+ | * g++ | ||
* git | * git | ||
* make | * make | ||
Line 16: | Line 17: | ||
cd coreboot | cd coreboot | ||
git submodule update --init --checkout | git submodule update --init --checkout | ||
− | git checkout | + | git checkout 7effaa4c02d974b59bd86307a54cefb7bb046a3a |
* Download [http://www.elinux.org/images/c/cd/Minnowboard_Max_Coreboot_config.txt config] | * Download [http://www.elinux.org/images/c/cd/Minnowboard_Max_Coreboot_config.txt config] | ||
Line 27: | Line 28: | ||
* extract from archive | * extract from archive | ||
* follow instructions in Readme_Extract to extract FSP | * follow instructions in Readme_Extract to extract FSP | ||
− | |||
− | |||
− | |||
− | |||
− | |||
= Setup = | = Setup = | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== TXE and SPI descriptor === | === TXE and SPI descriptor === | ||
First build a coreboot utility called ifdtool that's located within the coreboot directory | First build a coreboot utility called ifdtool that's located within the coreboot directory | ||
Line 48: | Line 37: | ||
cd ../../../ | cd ../../../ | ||
− | Download the original firmware binary [http://firmware.intel.com/sites/default/files/ | + | Download the original firmware binary [http://firmware.intel.com/sites/default/files/MinnowBoard.MAX_.X64.078.R02.bin_.zip here] |
− | unzip -d maxfirmware | + | unzip -d maxfirmware MinnowBoard.MAX_.X64.078.R02.bin_.zip |
cd maxfirmware | cd maxfirmware | ||
Run ifdtool to extract the TXE and SPI descriptor from the firmware image | Run ifdtool to extract the TXE and SPI descriptor from the firmware image | ||
− | ../coreboot/util/ifdtool/ifdtool -x | + | ../coreboot/util/ifdtool/ifdtool -x MinnowBoard.MAX.X64.078.R02.bin |
You should now have 4 files starting with flashregion_ | You should now have 4 files starting with flashregion_ | ||
Line 66: | Line 55: | ||
=== Coreboot === | === Coreboot === | ||
cd coreboot | cd coreboot | ||
− | * in src/soc/intel/fsp_baytrail/Kconfig line | + | * in src/soc/intel/fsp_baytrail/Kconfig line 75, change default value of SMM_TSEG_SIZE from '0x100000' to '0x800000' |
make menuconfig | make menuconfig | ||
* load provided config | * load provided config | ||
* save config to .config | * save config to .config | ||
* If you have a single core Minnowboard Max, change "Mainboard" -> "Memory SKU to build" to 1GB | * If you have a single core Minnowboard Max, change "Mainboard" -> "Memory SKU to build" to 1GB | ||
− | |||
= Building = | = Building = | ||
− | make crossgcc | + | make crossgcc-x64 crossgcc-i386 |
make | make | ||
* The firmware produced is build/coreboot.rom | * The firmware produced is build/coreboot.rom | ||
Line 81: | Line 69: | ||
make menuconfig | make menuconfig | ||
* Set Chipset -> Include the TXE to No | * Set Chipset -> Include the TXE to No | ||
− | make crossgcc | + | make crossgcc-x64 crossgcc-i386 |
make | make | ||
* When flashing the firmware, only flash the last 3MB of the 8 MB image onto the last 3MB of the chip | * When flashing the firmware, only flash the last 3MB of the 8 MB image onto the last 3MB of the chip | ||
** Example command using flashrom and a dediprog: echo 00500000:007fffff coreboot > regions.txt ; sudo flashrom -p dediprog -l regions.txt -i coreboot -w coreboot.rom | ** Example command using flashrom and a dediprog: echo 00500000:007fffff coreboot > regions.txt ; sudo flashrom -p dediprog -l regions.txt -i coreboot -w coreboot.rom | ||
* If you accidentally overwrite the first half, you will need to reflash the original firmware, which is available [https://uefidk.com/content/minnowboard-max here]. | * If you accidentally overwrite the first half, you will need to reflash the original firmware, which is available [https://uefidk.com/content/minnowboard-max here]. |
Revision as of 03:54, 18 April 2015
This page gives a step by step guide to building coreboot for the Minnowboard Max.
Contents
Requirements
- gcc
- g++
- git
- make
- ncurses-dev
- flex
- bison
Get sources and tools
NOTE: for simplicity, put all downloads and items extracted into the same directory.
Coreboot
git clone http://review.coreboot.org/p/coreboot cd coreboot git submodule update --init --checkout git checkout 7effaa4c02d974b59bd86307a54cefb7bb046a3a
- Download config
Intel Firmware Support Package (FSP)
- Download:
- extract from archive
- follow instructions in Readme_Extract to extract FSP
Setup
TXE and SPI descriptor
First build a coreboot utility called ifdtool that's located within the coreboot directory
cd coreboot/util/ifdtool make cd ../../../
Download the original firmware binary here
unzip -d maxfirmware MinnowBoard.MAX_.X64.078.R02.bin_.zip cd maxfirmware
Run ifdtool to extract the TXE and SPI descriptor from the firmware image
../coreboot/util/ifdtool/ifdtool -x MinnowBoard.MAX.X64.078.R02.bin
You should now have 4 files starting with flashregion_ Link flashregion_0_flashdescriptor.bin to descriptor.bin
ln -s flashregion_0_flashdescriptor.bin descriptor.bin
Link flashregion_1_bios.bin to txe.bin
ln -s flashregion_1_bios.bin txe.bin
- Ignore the other two flashregion files as they won't be used
Coreboot
cd coreboot
- in src/soc/intel/fsp_baytrail/Kconfig line 75, change default value of SMM_TSEG_SIZE from '0x100000' to '0x800000'
make menuconfig
- load provided config
- save config to .config
- If you have a single core Minnowboard Max, change "Mainboard" -> "Memory SKU to build" to 1GB
Building
make crossgcc-x64 crossgcc-i386 make
- The firmware produced is build/coreboot.rom
Building without TXE/SPI descriptor
make menuconfig
- Set Chipset -> Include the TXE to No
make crossgcc-x64 crossgcc-i386 make
- When flashing the firmware, only flash the last 3MB of the 8 MB image onto the last 3MB of the chip
- Example command using flashrom and a dediprog: echo 00500000:007fffff coreboot > regions.txt ; sudo flashrom -p dediprog -l regions.txt -i coreboot -w coreboot.rom
- If you accidentally overwrite the first half, you will need to reflash the original firmware, which is available here.