coreboot September 2009

coreboot@coreboot.org

62 participants
305 discussions

My last note today on EFI :-)
by ron minnich 27 Sep '09

27 Sep '09

"The Unified Extensible Firmware Interface (UEFI) Shell is designed for programmers who are writing automation process software for computer-based equipment. Traditionally this software was based on various DOS family operating systems that were popular during the 1980s. While the processes may vary from hardware validation to software testing to manufacturing, the basics of automation are the same. The UEFI Shell provides a modern base to the traditional commands common to any operating system. It does so in many cases in the words that the programmers speak, even if they at times speak different languages." Yep, it's really an operating system now. This is all quite unbelievable ... ron

4 5

Re: [coreboot] EHCI Debug port support?
by TigerLiu＠viatech.com.cn 27 Sep '09

27 Sep '09

Does coreboot support outputting debug message with a usb debug cable(NET20DC?) ? Does anybody test it with coreboot? Thanks! Best wishes,

2 1

Re: [coreboot] EHCI Debug port support?
by TigerLiu＠viatech.com.cn 27 Sep '09

27 Sep '09

Hi,Peter: So how to use EHCI-debug-port device as the debug message output pipe? Could you give a sample? Best wishes,

1 0

[PATCH] cross toolchain builder
by Stefan Reinauer 27 Sep '09

27 Sep '09

Hi, the attached patch adds crossgcc, our coreboot cross toolchain builder to coreboot v2. It's a simple script to build xxx-elf toolchains that are known-good for coreboot. Best regards, Stefan -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866 This adds a simple script to build a default toolchain for coreboot compilation, to be independent of broken or missing OS/distribution tool chains. Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Index: util/crossgcc/patches/binutils-2.18.50_no-i386-svr4-asm-comments.patch =================================================================== --- util/crossgcc/patches/binutils-2.18.50_no-i386-svr4-asm-comments.patch (revision 0) +++ util/crossgcc/patches/binutils-2.18.50_no-i386-svr4-asm-comments.patch (revision 0) @@ -0,0 +1,10 @@ +--- binutils-2.18.50/gas/config/tc-i386.c~ 2009-01-20 14:19:04.000000000 +0100 ++++ binutils-2.18.50/gas/config/tc-i386.c 2009-01-20 14:20:47.000000000 +0100 +@@ -183,6 +183,7 @@ + && !defined (TE_GNU) \ + && !defined (TE_LINUX) \ + && !defined (TE_NETWARE) \ ++ && 0 \ + && !defined (TE_FreeBSD) \ + && !defined (TE_NetBSD))) + /* This array holds the chars that always start a comment. If the Index: util/crossgcc/patches/gcc-4.3.2_use-gnu-style-comments-in-assembly.patch =================================================================== --- util/crossgcc/patches/gcc-4.3.2_use-gnu-style-comments-in-assembly.patch (revision 0) +++ util/crossgcc/patches/gcc-4.3.2_use-gnu-style-comments-in-assembly.patch (revision 0) @@ -0,0 +1,11 @@ +--- gcc-4.3.2/gcc/config/i386/unix.h~ 2009-01-20 16:05:45.000000000 +0100 ++++ gcc-4.3.2/gcc/config/i386/unix.h 2009-01-20 16:05:47.000000000 +0100 +@@ -32,7 +32,7 @@ + + /* String containing the assembler's comment-starter. */ + +-#define ASM_COMMENT_START "/" ++#define ASM_COMMENT_START "#" + + /* Output to assembler file text saying following lines + may contain character constants, extra white space, comments, etc. */ Index: util/crossgcc/patches/gcc-4.3.3_use-gnu-style-comments-in-assembly.patch =================================================================== --- util/crossgcc/patches/gcc-4.3.3_use-gnu-style-comments-in-assembly.patch (revision 0) +++ util/crossgcc/patches/gcc-4.3.3_use-gnu-style-comments-in-assembly.patch (revision 0) @@ -0,0 +1,11 @@ +--- gcc-4.3.3/gcc/config/i386/unix.h~ 2009-01-20 16:05:45.000000000 +0100 ++++ gcc-4.3.3/gcc/config/i386/unix.h 2009-01-20 16:05:47.000000000 +0100 +@@ -32,7 +32,7 @@ + + /* String containing the assembler's comment-starter. */ + +-#define ASM_COMMENT_START "/" ++#define ASM_COMMENT_START "#" + + /* Output to assembler file text saying following lines + may contain character constants, extra white space, comments, etc. */ Index: util/crossgcc/patches/gcc-4.4.1_less-junk-in-crtbegin.patch =================================================================== --- util/crossgcc/patches/gcc-4.4.1_less-junk-in-crtbegin.patch (revision 0) +++ util/crossgcc/patches/gcc-4.4.1_less-junk-in-crtbegin.patch (revision 0) @@ -0,0 +1,50 @@ +--- t/gcc-4.4.1/gcc/crtstuff.c Fr. Apr 10 01:23:07 2009 ++++ gcc-4.4.1/gcc/crtstuff.c Di. Jul 28 16:43:28 2009 +@@ -204,6 +204,7 @@ + = { (func_ptr) (-1) }; + #endif /* __DTOR_LIST__ alternatives */ + ++#if 0 + #ifdef USE_EH_FRAME_REGISTRY + /* Stick a label at the beginning of the frame unwind info so we can register + and deregister it with the exception handling library code. */ +@@ -219,6 +220,7 @@ + __attribute__ ((unused, section(JCR_SECTION_NAME), aligned(sizeof(void*)))) + = { }; + #endif /* JCR_SECTION_NAME */ ++#endif + + #if defined(INIT_SECTION_ASM_OP) || defined(INIT_ARRAY_SECTION_ASM_OP) + +@@ -309,6 +311,7 @@ + } + #endif /* !defined(FINI_ARRAY_SECTION_ASM_OP) */ + ++#if 0 + #ifdef USE_EH_FRAME_REGISTRY + #ifdef CRT_GET_RFIB_DATA + /* If we used the new __register_frame_info_bases interface, +@@ -320,6 +323,7 @@ + __deregister_frame_info (__EH_FRAME_BEGIN__); + #endif + #endif ++#endif + + completed = 1; + } +@@ -333,6 +337,7 @@ + = { __do_global_dtors_aux }; + #endif /* !defined(FINI_SECTION_ASM_OP) */ + ++#if 0 + #if defined(USE_EH_FRAME_REGISTRY) || defined(JCR_SECTION_NAME) + /* Stick a call to __register_frame_info into the .init section. For some + reason calls with no arguments work more reliably in .init, so stick the +@@ -364,6 +369,7 @@ + } + #endif /* JCR_SECTION_NAME */ + } ++#endif + + #ifdef INIT_SECTION_ASM_OP + CRT_CALL_STATIC_FUNCTION (INIT_SECTION_ASM_OP, frame_dummy) Index: util/crossgcc/patches/binutils-2.19.1_no-i386-svr4-asm-comments.patch =================================================================== --- util/crossgcc/patches/binutils-2.19.1_no-i386-svr4-asm-comments.patch (revision 0) +++ util/crossgcc/patches/binutils-2.19.1_no-i386-svr4-asm-comments.patch (revision 0) @@ -0,0 +1,10 @@ +--- binutils-2.19.1/gas/config/tc-i386.c~ 2009-01-20 14:19:04.000000000 +0100 ++++ binutils-2.19.1/gas/config/tc-i386.c 2009-01-20 14:20:47.000000000 +0100 +@@ -318,6 +318,7 @@ + && !defined (TE_GNU) \ + && !defined (TE_LINUX) \ + && !defined (TE_NETWARE) \ ++ && 0 \ + && !defined (TE_FreeBSD) \ + && !defined (TE_NetBSD))) + /* This array holds the chars that always start a comment. If the Index: util/crossgcc/buildgcc =================================================================== --- util/crossgcc/buildgcc (revision 0) +++ util/crossgcc/buildgcc (revision 0) @@ -0,0 +1,340 @@ +#!/bin/bash +# +# Copyright (C) 2008-2009 by coresystems GmbH +# written by Patrick Georgi <patrick.georgi(a)coresystems.de> and +# Stefan Reinauer <stefan.reinauer(a)coresystems.de> +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; version 2 of the License. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA +# + +CROSSGCC_DATE="August 18th, 2009" +CROSSGCC_VERSION="0.9" + +# default settings +TARGETDIR=`pwd`/xgcc +TARGETARCH=i386-elf +DESTDIR= + +# version numbers +GMP_VERSION=4.3.1 +MPFR_VERSION=2.4.1 +GCC_VERSION=4.4.1 +BINUTILS_VERSION=2.19.1 +GDB_VERSION=6.8 + +# archive locations +GMP_ARCHIVE="ftp://ftp.gmplib.org/pub/gmp-${GMP_VERSION}/gmp-${GMP_VERSION}.tar.bz2" +MPFR_ARCHIVE="http://www.mpfr.org/mpfr-current/mpfr-${MPFR_VERSION}.tar.bz2" +GCC_ARCHIVE="ftp://ftp.gwdg.de/pub/gnu/ftp/gnu/gcc/gcc-${GCC_VERSION}/gcc-core-${GCC_VERSION}.tar.bz2" +BINUTILS_ARCHIVE="http://ftp.gnu.org/gnu/binutils/binutils-${BINUTILS_VERSION}.tar.bz2" +GDB_ARCHIVE="http://ftp.gnu.org/gnu/gdb/gdb-${GDB_VERSION}.tar.bz2" + +GMP_DIR="gmp-${GMP_VERSION}" +MPFR_DIR="mpfr-${MPFR_VERSION}" +GCC_DIR="gcc-${GCC_VERSION}" +BINUTILS_DIR="binutils-${BINUTILS_VERSION}" +GDB_DIR="gdb-${GDB_VERSION}" + +SAVETEMPS=0 + +red='\e[0;31m' +RED='\e[1;31m' +green='\e[0;32m' +GREEN='\e[1;32m' +blue='\e[0;34m' +BLUE='\e[1;34m' +cyan='\e[0;36m' +CYAN='\e[1;36m' +NC='\e[0m' # No Color + +searchgnu() +{ + # $1 short name + # result: GNU version of that tool on stdout + # or no output if no GNU version was found + for i in "$1" "g$1" "gnu$1"; do + if test -x "`which $i 2>/dev/null`"; then + if test `$i --version 2>/dev/null |grep -c GNU` -gt 0; then + echo $i + return + fi + fi + done + printf "${RED}ERROR:${red} Missing toolchain: $1${NC}\n" >&2 + exit 1 +} + +TAR=`searchgnu tar` +PATCH=`searchgnu patch` +MAKE=`searchgnu make` + +cleanup() +{ + printf "Cleaning up temporary files... " + rm -rf build-* combined gcc-* gmp-* mpfr-* binutils-* gdb-* + printf "${green}ok${NC}\n" +} + +myhelp() +{ + printf "Usage: $0 [-V] [-c] [-p <platform>] [-d <target directory>] [-D <dest dir>]\n" + printf " $0 [-V|--version]\n" + printf " $0 [-h|--help]\n\n" + + printf "Options:\n" + printf " [-V|--version] print version number and exit\n" + printf " [-h|--help] print this help and exit\n" + printf " [-c|--clean] remove temporary files before build\n" + printf " [-t|--savetemps] don't remove temporary files after build\n" + printf " [-p|--platform <platform>] target platform to build cross compiler for\n" + printf " (defaults to $TARGETARCH)\n" + printf " [-d|--directory <target dir>] target directory to install cross compiler to\n" + printf " (defaults to $TARGETDIR)\n\n" + printf " [-D|--destdir <dest dir>] destination directory to install cross compiler to\n" + printf " (for RPM builds, default unset)\n\n" +} + +myversion() +{ + # version tag is always printed, so just print the license here + + cat << EOF +Copyright (C) 2008-2009 by coresystems GmbH + +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; version 2 of the License. + +This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +EOF +} + +printf "${blue}Welcome to the ${red}coresystems${blue} cross toolchain builder v$CROSSGCC_VERSION ($CROSSGCC_DATE)${NC}\n\n" + +# parse parameters.. try to find out whether we're running GNU getopt +getoptbrand="`getopt -V`" +if [ "${getoptbrand:0:6}" == "getopt" ]; then + # Detected GNU getopt that supports long options. + args=`getopt -l version,help,clean,directory:,platform:,destdir:,savetemps Vhcd:p:D:t -- "$@"` + eval set "$args" +else + # Detected non-GNU getopt + args=`getopt Vhcd:p:D:t $*` + set -- $args +fi + +if [ $? != 0 ]; then + myhelp + exit 1 +fi + +while true ; do + case "$1" in + -V|--version) shift; myversion; exit 0;; + -h|--help) shift; myhelp; exit 0;; + -c|--clean) shift; cleanup;; + -t|--savetemps) shift; SAVETEMPS=1;; + -d|--directory) shift; TARGETDIR="$1"; shift;; + -p|--platform) shift; TARGETARCH="$1"; shift;; + -D|--destdir) shift; DESTDIR="$1"; shift;; + --) shift; break;; + -*) printf "Invalid option\n\n"; myhelp; exit 1;; + *) break;; + esac +done + +printf "Downloading tar balls ... \n" +mkdir -p tarballs +for ARCHIVE in $GMP_ARCHIVE $MPFR_ARCHIVE $GCC_ARCHIVE $BINUTILS_ARCHIVE $GDB_ARCHIVE; do + FILE=`basename $ARCHIVE` + printf " * $FILE " + test -f tarballs/$FILE && printf "(cached)" || ( + printf "(downloading)" + cd tarballs + wget -q $ARCHIVE + ) + test -f tarballs/$FILE || printf "Failed to download $FILE.\n" + test -f tarballs/$FILE || exit 1 + printf "\n" +done +printf "Downloaded tar balls ... " +printf "${green}ok${NC}\n" + +printf "Unpacking and patching ... \n" +for PACKAGE in GMP MPFR GCC BINUTILS GDB; do + archive=$PACKAGE"_ARCHIVE" + archive=${!archive} + dir=$PACKAGE"_DIR" + test -d ${!dir} || ( + printf " * `basename $archive`\n" + FLAGS=zxf + test ${archive:${#archive}-2:2} = "gz" && FLAGS=zxf + test ${archive:${#archive}-3:3} = "bz2" && FLAGS=jxf + $TAR $FLAGS tarballs/`basename $archive` + for patch in patches/${!dir}"_*.patch"; do + test -r $patch || continue + printf " o `basename $patch`\n" + patch -s -N -p0 < `echo $patch` + done + ) +done +printf "Unpacked and patched ... " +printf "${green}ok${NC}\n" + +mkdir -p build-gmp build-mpfr build-binutils build-gcc build-gdb +if [ -f build-gmp/.success ]; then + printf "Skipping GMP as it is already built\n" +else +printf "Building GMP ${GMP_VERSION} ... " +( + cd build-gmp + rm -f .failed + if [ `uname` = "Darwin" ]; then + # generally the OS X compiler can create x64 binaries. + # Per default it generated i386 binaries in 10.5 and x64 + # binaries in 10.6 (even if the kernel is 32bit) + # For some weird reason, 10.5 autodetects an ABI=64 though + # so we're setting the ABI explicitly here. + OPTIONS="ABI=32" + touch .architecture_check.c + gcc .architecture_check.c -c -o .architecture_check.o + ARCH=`file .architecture_check.o |cut -f5 -d\ ` + test "$ARCH" = "x86_64" && OPTIONS="ABI=64" + rm .architecture_check.c .architecture_check.o + fi + + ../${GMP_DIR}/configure --disable-shared --prefix=$TARGETDIR $OPTIONS \ + || touch .failed + $MAKE || touch .failed + $MAKE install DESTDIR=$DESTDIR || touch .failed + if [ ! -f .failed ]; then touch .success; fi +) &> build-gmp/crossgcc-build.log +test -r build-gmp/.failed && printf "${RED}failed${NC}\n" || printf "${green}ok${NC}\n" +test -r build-gmp/.failed && exit 1 +fi + +#if [ "$DESTDIR" != "" -a ! -x $TARGETDIR ]; then +# # create compat link +# ln -s $DESTDIR$TARGETDIR $TARGETDIR +#fi + +# Now set CFLAGS to match GMP CFLAGS. +HOSTCFLAGS=`grep __GMP_CFLAGS $DESTDIR$TARGETDIR/include/gmp.h |cut -d\" -f2` + +if [ -f build-mpfr/.success ]; then + printf "Skipping MPFR as it is already built\n" +else +printf "Building MPFR ${MPFR_VERSION} ... " +( + test `uname` = "Darwin" && CFLAGS="$CFLAGS -force_cpusubtype_ALL" + cd build-mpfr + rm -f .failed + ../${MPFR_DIR}/configure --disable-shared --prefix=$TARGETDIR \ + --infodir=$TARGETDIR/info \ + --with-gmp=$DESTDIR$TARGETDIR CFLAGS="$HOSTCFLAGS" || touch .failed + $MAKE || touch .failed + $MAKE install DESTDIR=$DESTDIR || touch .failed + + # work around build problem of libgmp.la + if [ "$DESTDIR" != "" ]; then + perl -pi -e "s,$DESTDIR,," $DESTDIR$TARGETDIR/libgmp.la + fi + + if [ ! -f .failed ]; then touch .success; fi +) &> build-mpfr/crossgcc-build.log +test -r build-mpfr/.failed && printf "${RED}failed${NC}\n" || printf "${green}ok${NC}\n" +test -r build-mpfr/.failed && exit 1 +fi + +if [ -f build-binutils/.success ]; then + printf "Skipping binutils as it is already built\n" +else +printf "Building binutils ${BINUTILS_VERSION} ... " +( + cd build-binutils + rm -f .failed + ../binutils-${BINUTILS_VERSION}/configure --prefix=$TARGETDIR --target=${TARGETARCH} \ + --disable-werror --disable-nls \ + CFLAGS="$HOSTCFLAGS" || touch .failed + $MAKE || touch .failed + $MAKE install DESTDIR=$DESTDIR || touch .failed + if [ ! -f .failed ]; then touch .success; fi +) &> build-binutils/crossgcc-build.log +test -r build-binutils/.failed && printf "${RED}failed${NC}\n" || printf "${green}ok${NC}\n" +test -r build-binutils/.failed && exit 1 +fi + +if [ -f build-gcc/.success ]; then + printf "Skipping GCC as it is already built\n" +else +printf "Building GCC ${GCC_VERSION} ... " +( + cd build-gcc + rm -f .failed + # GCC does not honour HOSTCFLAGS at all. CFLAGS are used for + # both target and host object files. This is pretty misdesigned. + # There's a work-around called CFLAGS_FOR_BUILD and CFLAGS_FOR_TARGET + # but it does not seem to work properly. At least the host library + # libiberty is not compiled with CFLAGS_FOR_BUILD. + CFLAGS_FOR_BUILD="$HOSTCFLAGS" ../gcc-${GCC_VERSION}/configure \ + --prefix=$TARGETDIR --libexecdir=$TARGETDIR/lib \ + --target=${TARGETARCH} --disable-werror \ + --disable-libssp --disable-bootstrap --disable-nls \ + --with-gmp=$DESTDIR$TARGETDIR --with-mpfr=$DESTDIR$TARGETDIR \ + || touch .failed + $MAKE CFLAGS_FOR_BUILD="$HOSTCFLAGS" || touch .failed + $MAKE install DESTDIR=$DESTDIR || touch .failed + if [ ! -f .failed ]; then touch .success; fi +) &> build-gcc/crossgcc-build.log +test -r build-gcc/.failed && printf "${RED}failed${NC}\n" || printf "${green}ok${NC}\n" +test -r build-gcc/.failed && exit 1 +fi + +if [ -f build-gdb/.success ]; then + printf "Skipping GDB as it is already built\n" +else +printf "Building GDB ${GDB_VERSION} ... " +( + cd build-gdb + export PATH=$PATH:$PREFIX/bin + rm -f .failed + ../gdb-${GDB_VERSION}/configure --prefix=$TARGETDIR --target=${TARGETARCH} \ + --disable-werror --disable-nls + $MAKE || touch .failed + $MAKE install DESTDIR=$DESTDIR || touch .failed + if [ ! -f .failed ]; then touch .success; fi +) &> build-gdb/crossgcc-build.log +test -r build-gdb/.failed && printf "${RED}failed${NC}\n" || printf "${green}ok${NC}\n" +test -r build-gdb/.failed && exit 1 +fi + +if [ $SAVETEMPS -eq 0 ]; then + printf "Cleaning up... " + rm -rf ${GMP_DIR} build-gmp + rm -rf ${MPFR_DIR} build-mpfr + rm -rf ${BINUTILS_DIR} build-binutils + rm -rf ${GCC_DIR} build-gcc + rm -rf ${GDB_DIR} build-gdb + printf "${green}ok${NC}\n" +else + printf "Leaving temporary files around... ${green}ok${NC}\n" +fi + +printf "\n${green}You can now run your $TARGETARCH cross toolchain from $TARGETDIR.${NC}\n" + + Property changes on: util/crossgcc/buildgcc ___________________________________________________________________ Added: svn:executable + * Index: util/crossgcc/README =================================================================== --- util/crossgcc/README (revision 0) +++ util/crossgcc/README (revision 0) @@ -0,0 +1,17 @@ +README +------ + +This is a cross toolchain builder for -elf toolchains (ie. no libc support) + +known working: + i386-elf + x86_64-elf + powerpc-elf + mipsel-elf + +known broken: + alpha-elf + arm-elf + powerpc64-elf + +

4 10

coreboot support for Intel DP45SG?
by Jaromír Mikeš 27 Sep '09

27 Sep '09

Hello, I am watching this project already few months and now come time I would like test it on my machine. First of course I would like find out if it will work on my hardware. Intel motherboard DP45SG http://www.intel.com/support/motherboards/desktop/DP45SG/sb/CS-029162.htm CPU Intel(R) Core(TM)2 Duo E7400 @ 2.80GHz North Bridge Intel P45 South Bridge Intel ICH10R Super I/O chip NSC PC8374L Outputs for lspci -tvnn, superiotool -dV, flashrom -V are in attachment Please let me know if coreboot should work here or if you need some additional info regards mira

2 4

finding the flash write enable.
by ron minnich 26 Sep '09

26 Sep '09

we just had the need to find a flash write enable on some servers. These are Dell S1850s and we're tired of having a non-Linux-based Flash tool, and, still worse, one to which we do not have source. Flashrom would be great, save that it can't get the flash to write. We decided to see if it was the classic GPIO-enabled FLASH write pin, which is the standard it seems in PC hardware. In this note I am just describing a program that I wrote long ago at LANL and have used from time to time when I could not get the info I needed on enabling FLASH write. One thing we have found over the past 10 years: the single most common write enable control is a GPIO attached to a southbridge. Don't know why it always seems to be this way, but there it is. This leads to a simple strategy to test for a GPIO enable, and to find which one it is. First, we find the southbridge, which in this case is an ICH5. The GPIO programming on this part is little changed from earlier parts. Then we find the pci function which has the GPIOs. It's usually the LPC bridge. So for ICH5: 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) it's that one. So, to make it easy, rather than look at the BAR for the GPIO, just cat /proc/ioports and find this: 0880-08bf : 0000:00:1f.0 0880-08bf : pnp 00:06 OK, we are about ready to go. The base address of the GPIOs is 0x880. If you're paranoid confirm it with setpci: [root@tn4 ~]# setpci -s 0:1f.0 58.l 00000881 [root@tn4 ~]# You need to look up the IO space mappings of SOME of the registers, but for this simple program, not ALL. In fact all we're going to do is read in the GPIO data level register, complement it, write it out, then run flashrom to see if it works. But, you ask: - what if you read inputs and write them out nothing, so don't worry. They're inputs. - you change GPIO pins that do some other thing well, it gets harder in that case. For instance, some laptops use a GPIO pin to enable DRAM power. Don't worry, you'll find out if they do. In that case, you'll have to do 32 boot/test cycles in the worst case, instead of the five we do here. It actually can be instructive on a laptop to change output GPIO levels and see what happens, so this is a fun test to do anyway. First, though, do this: flashrom -r factory.img Then emacs factory.img, (Go into OVRWRT mode!) and look for a string like this: F2 = Setup I changed it to F2 = FIXup I may have used some other F-based words, as time went on, but that's another story. You want to make sure that if you really do rewrite it that it is easy to tell! With this change, as soon as the BIOS splash screen comes up, you will know. OK, some code: Just set a few things up we think we'll need. #include <stdio.h> #include <sys/io.h> #define LVL 0xc LVL is the level register for the GPIO. Now let's go to work. int main(int argc, char *argv[]) { unsigned long gpioport = 0x880; unsigned long gpioval; iopl(3); /* first simple test: read in all GPIOs, complement them, * output them, see if flashrom works */ gpioval = inl(gpioport + LVL); printf("GPIO is 0x%x (default 0x1f1f0000)\n", gpioval); /* invert */ gpioval = ~gpioval; printf("GPIO will be set to 0x%x \n", gpioval); outl(gpioval, gpioport + LVL); gpioval = inl(gpioport + LVL); printf("GPIO is 0x%x \n", gpioval); } OK, call this program 'one'. At this point, you want to try a flashrom run. As it happens this works and is sufficient to allow us to use flashrom! How to finish the task? It's actually a fairly simple newtonian search. First try gpioval ^= 0xffff0000; If that works, then try 0xff000000, etc. etc. Even if you get it wrong, which I did, it still doesn't take long to find it. Warning, though: each time you try, be sure to change the FIXup string in the rom image, to be very very sure that you really did rewrite it. You need to be careful about this step. Anyway, hope that is a little useful. It really is a very simple process to find a GPIO enable. That's one reason that vendors are going to make this much, much harder on future systems. GPIO enables are not a security feature, in spite of what you may have heard; they are really accident protection in case some piece of software goes insane and starts writing to random memory locations. ron

2 1

Re: [coreboot] coreboot Digest, Vol 55, Issue 26
by 项宇 26 Sep '09

26 Sep '09

hi, I am porting coreboot to an amd dbm690t-like platform recently, but the vga is not work。 My board have no video memory onboard, i am not sure whether coreboot support vga output in amd dbm690t board if there is no video memory(use main memory only),can anyone tell me this? BTW: I test my vbios in another dbm690t board use coreboot, the vga output is ok. Thanks!

2 1

patch: disable IPMI on the dell s1850
by ron minnich 26 Sep '09

26 Sep '09

attached. ron

3 3

CBFS searches in Coreboot and SeaBIOS
by Myles Watson 26 Sep '09

26 Sep '09

Could we change the searches for PCI ROMs so that we look through CBFS and then for each ROM we find in CBFS we find the device instead of vice versa? It seems like we wouldn't lose a lot of generality, but we'd lose a lot of spew in the logs. Any objections? Thanks, Myles

5 12

build service results for r4681
by coreboot information 26 Sep '09

26 Sep '09

Dear coreboot readers! This is the automatic build system of coreboot. The developer "stepan" checked in revision 4681 to the coreboot repository. This caused the following changes: Change Log: This adds a simple script to build a default toolchain for coreboot compilation, to be independent of broken or missing OS/distribution tool chains. Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Acked-by: Ronald G. Minnich <rminnich(a)gmail.com> Build Log: Compilation of embeddedplanet:ep405pc is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4681&device=ep405pc&vendor… Compilation of motorola:sandpointx3_altimus_mpc7410 is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4681&device=sandpointx3_al… Compilation of totalimpact:briq is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4681&device=briq&vendor=to… If something broke during this checkin please be a pain in stepan's neck until the issue is fixed. If this issue is not fixed within 24h the revision should be backed out. Best regards, coreboot automatic build system

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
31
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot September 2009