Build from Windows - Revision history

Sduplichan: /* Test using simnow (optional, AMD projects only) */

2011-04-02T01:31:55Z

‎Test using simnow (optional, AMD projects only)

Sduplichan: /* Build the coreboot project */

2011-04-02T01:27:45Z

‎Build the coreboot project

Sduplichan: /* Build the coreboot project */

2011-04-02T01:25:56Z

‎Build the coreboot project

Sduplichan: /* Setup the coreboot build environment (shortcut method) */

2011-04-02T01:02:59Z

‎Setup the coreboot build environment (shortcut method)

Sduplichan: /* Setup the coreboot build environment (long method) */

2011-04-02T00:53:48Z

‎Setup the coreboot build environment (long method)

Sduplichan: /* Test using simnow (optional, AMD projects only) */

2010-09-30T01:07:22Z

‎Test using simnow (optional, AMD projects only)

Stuge: s/linux/bare metal hardware/

2010-09-29T06:31:45Z

s/linux/bare metal hardware/

Sduplichan: /* Test using simnow (optional, AMD projects only) */

2010-09-29T03:12:05Z

‎Test using simnow (optional, AMD projects only)

Sduplichan: /* Build the coreboot project */

2010-09-29T02:54:41Z

‎Build the coreboot project

Sduplichan: /* Setup the coreboot build environment (shortcut method) */

2010-09-29T01:04:53Z

‎Setup the coreboot build environment (shortcut method)

@@ Line 184: / Line 184: @@
 [[Image:winbuild-vbios-banner.png|left]]
 <br clear="all"/>
 Next, the seabios payload executes:

@@ Line 83: / Line 83: @@
 :5. At the <tt>$</tt> prompt, type <tt>make</tt>. After a few seconds, the build should complete:
-  $ <b>make oldconfig</b>
+  $ <b>make</b>
       (some output omitted)

@@ Line 69: / Line 69: @@
 :1. Decompress the [http://notabs.org/coreboot/windows-build.htm sample project] into any directory. Note: Avoid the use of spaces in the project path and directory name. Use [http://7-zip.org/ 7-zip] for decompression.
-:2. Replace the sample <tt>coreboot</tt> [svn://coreboot.org/coreboot/trunk source code] (rev 5775) with your own. The directory must be named <tt>coreboot</tt>.
+:2. Replace the sample <tt>coreboot</tt> [svn://coreboot.org/coreboot/trunk source code] (rev 6474) with your own. The directory must be named <tt>coreboot</tt>.
 :3. Using Windows explorer, click on <tt>go.bat</tt> to start the build environment. It will look something like this:
-  <font color="#008000">Administrator@M3A78</font> <font color="#808000">/D/tmp/win-build-env-002/coreboot</font>
+  <font color="#008000">Administrator@m3A78</font> <font color="#808000">/D/tmp/win-build-env-005/coreboot</font>
   $ _
-:4. First, build the seabios payload:
+:4. Now configure coreboot:
-  $ <b>cd ../seabios/seabios-for-coreboot</b><br>
+  <font color="#008000">Administrator@m3A78</font> <font color="#808000">/D/tmp/win-build-env-005/coreboot</font>
-  <font color="#008000">Administrator@M3A78</font> <font color="#808000">/D/tmp/win-build-env-002/seabios/seabios-for-coreboot</font>
- $ <b>make</b>
- &nbsp; Compiling whole program out/ccode.16.s
- &nbsp; Compiling to assembler out/asm-offsets.s
- &nbsp; Generating offset file out/asm-offsets.h
- &nbsp; Compiling (16bit) out/code16.o
- &nbsp; 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'
- &nbsp; Compiling whole program out/code32seg.o
- &nbsp; Building ld scripts (version &quot;0.6.1-20100928_165201-m3a78&quot;)
- Fixed space: 0xe05b-0x10000 total: 8101 slack: 2 Percent slack: 0.0%
-bit size: 37760
-bit segmented size: 2416
-bit flat size: 50752
- &nbsp; Linking out/rom16.o
- &nbsp; Stripping out/rom16.strip.o
- &nbsp; Linking out/rom32seg.o
- &nbsp; Stripping out/rom32seg.strip.o
- &nbsp; Linking out/rom.o
- &nbsp; Prepping out/bios.bin
- Total size: 90928 Free space: 40144 Percent used: 69.4% (128KiB rom)
-:5. Now configure coreboot:
- $ <b>cd ../../coreboot</b><br>
-  <font color="#008000">Administrator@M3A78</font> <font color="#808000">/D/tmp/win-build-env-002/coreboot</font>
   $ <b>make oldconfig</b>
@@ Line 106: / Line 81: @@
   mainboard model          : 9 Serengeti Cheetah (Fam10)
   rom chip size            : 3 512 KB
-:6. At the <tt>$</tt> prompt, type <tt>make</tt>. After a few seconds, the build should complete:
+:5. At the <tt>$</tt> prompt, type <tt>make</tt>. After a few seconds, the build should complete:
-     CC         cpu/x86/mtrr/mtrr.o
+ $ <b>make oldconfig</b>
       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)
+      PAYLOAD    SeaBIOS (internal, compression: LZMA)
-      CBFSPRINT  coreboot.rom<br>
+      CBFSPRINT  coreboot.rom
   coreboot.rom: 512 kB, bootblocksize 2390, romsize 524288, offset 0x0
-  Alignment: 64 bytes<br>
+  Alignment: 64 bytes
   Name                           Offset     Type         Size
-  fallback/romstage              0x0        stage        69016
+ cmos_layout.bin                0x0        unknown      1776
-  fallback/coreboot_ram          0x10e00    stage        47261
+  fallback/romstage              0x740      stage        69698
-  fallback/payload               0x1c700    payload      45815
+  fallback/coreboot_ram          0x117c0    stage        48127
-  (empty)                        0x27a40    null         359458<br>
+  fallback/payload               0x1d400    payload      48893
-  <font color="#008000">Administrator@M3A78</font> <font color="#808000">/D/tmp/win-build-env-002/coreboot</font>
+  (empty)                        0x29340    null         353058
   $ _
 The final bios image is in file coreboot\build\coreboot.rom:
 <pre>
-  Directory of D:\tmp\win-build-env-001\coreboot\build
+  Directory of D:\tmp\win-build-env-005\coreboot\build
-/03/10  12:23 PM           524,288 coreboot.rom
+/01/11  08:11 PM           524,288 coreboot.rom
 </pre>

@@ Line 57: / Line 57: @@
 ==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 [http://notabs.org/coreboot/windows-build.htm 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 <tt>msys</tt>. This is the complete coreboot-ready msys+mingw. The <tt>msys.bat</tt> file in this directory starts the msys+mingw build environment. Use the standard tool names to generate output that targets the local Windows environment. To produce the i386-elf output used by coreboot, use the tools in the gcc444 or gcc450 directory. For example, <tt>gcc -c hello.c</tt> builds a Windows object, while <tt>/gcc450/xgcc/bin/i386-elf-gcc hello.c</tt> builds an i386-elf object.
+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 [http://notabs.org/coreboot/windows-build.htm 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 <tt>msys</tt>. This is the complete coreboot-ready msys+mingw. The <tt>msys.bat</tt> 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, <tt>gcc -c hello.c</tt> builds a Windows object, while <tt>/gcc452/xgcc/bin/i386-elf-gcc hello.c</tt> 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.
-#'''seabios''' directory. This directory contains seabios source code, used to build the sample payload.
+#'''simnow''' directory. Sample helper files for testing the AMD Serengeti Cheetah (Fam10) project on the AMD simnow simulator.
-#'''simnow''' directory. Helper files for testing on the AMD simnow simulator (AMD projects only).
-#'''tools''' directory. This directory contains needed tools that are not part of coreboot, msys, or mingw.
 #'''go.bat'''. This batch file sets up environment variables needed for cross compiling, and switches to the coreboot directory.

@@ Line 11: / Line 11: @@
 Step 1 involves downloading and decompressing mingw and msys, both of which contain several components. See [http://mingw.org/ 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 <tt>util/crossgcc/buildgcc</tt> for this purpose. Use msys.bat to start the msys+mingw environment, then execute these commands. In this example, <tt>buildgcc</tt> has been edited so that gcc 4.5.0 is built instead of gcc 4.4.4:
+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 <tt>util/crossgcc/buildgcc</tt> for this purpose. Use msys.bat to start the msys+mingw environment, then execute these commands:
   <font color="#008000">Administrator@M3A78</font> <font color="#808000">~</font>

@@ Line 186: / Line 186: @@
 ===Known problems with this demo===
-#An unwanted stack access by an AP core during cache as ram disable causes a crash. The work-around used in the sample project is to remove AP cores from the simnow model. A proper fix is being [http://www.coreboot.org/pipermail/coreboot/2010-September/060090.html developed].
+#The seabios PS/2 keyboard initialization is not reliable when run on the simnow target.
-#PS/2 Keyboard init timeout causes boot delay ([http://www.coreboot.org/pipermail/coreboot/2010-September/060046.html workaround]).
+#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.
-#PS/2 keyboard not working.
 ===Known problems with windows building===
 #Libncurses is not available, which prevents <tt>make menuconfig</tt> from building. Work-around: use <tt>make oldconfig</tt> instead.

← Older revision		Revision as of 06:31, 29 September 2010
Line 6:		Line 6:

	#Download and install a native msys+mingw environment on your Windows computer.		#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 ~~linux~~.	+	#Build and install cross compile versions of binutils and gcc that run on Windows and target 32-bit x86 bare metal hardware.

@@ Line 138: / Line 138: @@
 ==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 [http://developer.amd.com/cpu/simnow/Pages/default.aspx simnow]. This example uses version <tt>simnow-win64-4.6.2pub.exe</tt>, a recent public version for Windows. Note that simnow requires a 64-bit operation system. Add an environment variable named <tt>simnow</tt> that points to the directory where simnow is installed:
+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 [http://developer.amd.com/cpu/simnow/Pages/default.aspx simnow]. This example uses version <tt>simnow-win64-4.6.2pub.exe</tt>, a recent public version for Windows. Note that simnow requires a 64-bit operating system. Add an environment variable named <tt>simnow</tt> that points to the directory where simnow is installed:
 [[Image:winbuild-simnow-env.png|left]]
 <br clear="all"/>