coreboot

coreboot@coreboot.org

25 participants
39547 discussions

new config language.
by ron minnich 09 Jun '03

09 Jun '03

I'm opening up this discussion, which was formerly just between the folks actively doing freebios2. We're getting closer to having things working and I am happy to hear any comments. linuxbios.a now builds for the K8 with the new config tool. Not all of linuxbios, just linuxbios.a, but that's quite a way to working. Things are stricter now. We've been able to operate before with code like this: #if SOME_VARIABLE_THAT_WAS_UNDEFINED == 0 stuff #endif because in the GNU C preprocessor, #if (a == 0) and #ifndef a are equivalent if a is undefined. I think that is a very poor way to operate: it can fool people, and in a BIOS you want more checking. Now that you can use an 'if' operator in the config language, setting up some things is a lot easier: For example, this: expr ROM_SECTION_SIZE =(USE_FALLBACK_IMAGE*65536)+(USE_NORMAL_IMAGE*(ROM_SIZE - 65536)) expr ROM_SECTION_OFFSET=(USE_FALLBACK_IMAGE*(ROM_SIZE-65536))+(USE_NORMAL_IMAGE *0) now becomes this: default FALLBACK_SIZE=65536 if USE_FALLBACK_IMAGE option ROM_SECTION_SIZE = FALLBACK_SIZE option ROM_SECTION_OFFSET= (ROM_SIZE - FALLBACK_SIZE) end if USE_NORMAL_IMAGE option ROM_SECTION_SIZE = (ROM_SIZE - FALLBACK_SIZE) option ROM_SECTION_OFFSET= 0 end Much better. However, if you have not defined USE_FALLBACK_IMAGE or USE_NORMAL_IMAGE, then you're going to get an error, which in the past was not the case. So we'll have to learn to be a bit more careful about defining things before they are used, and not using things that were never defined. This is all proving to be easy, but people will need to take more care with the Config files (which, in deference to Windows and MacOS, are now named Config.lb). ron

3 3

After make, where is file "docipl"?
by roger 09 Jun '03

09 Jun '03

ok. completed the make/compile for the smartcore-p5/ but yet there's no file called "docipl". I would assume by the prefix that this is meant for the DOC.. for which i do have. I'm following the Sis documentation as a guideline. >From what I'm seeing in the util/mtd/burn_mtd script, I only need to create the images (with dd) and then dd the images to the DiskOnChip (on this 440BX board). -- Roger http://www.eskimo.com/~roger/index.html

1 0

Re: tusl2-c with kernel
by Yap Ee Huey 09 Jun '03

09 Jun '03

Hi, I used RAMTEST=1 and memtest (from memtest86.com) as payload : USE_ELF_BOOT=1 payload memtest (default memtest is elf , correct ?) RAMTEST output : Testing SDRAM : 00000000-0009ffff SDRAM fill: 00000000 00010000 00020000 00030000 00040000 00050000 00060000 00070000 00080000 00090000 0009ffff SDRAM verify: 00000000 00010000 00020000 00030000 00040000 00050000 00060000 00070000 00080000 00090000 0009ffff Done. MEMTEST loading : Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 37:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Found ELF candiate at offset 0 header_offset is 0 Try to load at offset 0x0 New segment addr 0x10000 size 0x112b8 offset 0x1000 filesize 0x112b8 (cleaned up) New segment addr 0x10000 size 0x112b8 offset 0x1000 filesize 0x112b8 Loading Segment: addr: 0x000000000ff6e5a8 memsz: 0x00000000000112b8 filesz: 0x00000000000112b8 Jumping to boot code at 0x10000 entry = 0x00010000 lb_start = 0x00004000 lb_size = 0x0004ed2c adjust = 0x0ffad2d4 buffer = 0x0ff625a8 elf_boot_notes = 0x0000cb40 adjusted_boot_notes = 0x0ffb9e14 LinuxBIOS-1.0.0 Mon Jun 9 16:13:25 EDT 2003 starting... (REBOOTED) Looks like my elf boot always failed. Any debug direction ? Thanks. regards, eehuey >From: ron minnich <rminnich(a)lanl.gov> >To: Yap Ee Huey <yapeehuey(a)hotmail.com> >CC: linuxbios(a)clustermatic.org >Subject: Re: tusl2-c with kernel >Date: Fri, 6 Jun 2003 07:40:24 -0600 (MDT) > >Have you just tried memtest first? > >I am wondering if you do in fact have a dram problem. > >ron > _________________________________________________________________ Using a handphone prepaid card? Reload your credit online! http://www.msn.com.my/reloadredir/default.asp

2 1

timer.h - No such file or directory
by roger 08 Jun '03

08 Jun '03

Using the smartcore-p5 tree: gcc ... -o ide.o /home/roger/src/linuxbios/freebios/src/pc80/ide/ide.c /home/roger/src/linuxbios/freebios/src/pc80/ide/ide.c:27:19: timer.h: No such file or directory I'm seeing a freebios/src/etherboot/timer.h & freebios/src/arch/ppc/include/timer.h but nothing for the i386/ -- Roger http://www.eskimo.com/~roger/index.html

3 4

docprobe can't find DOC
by roger 08 Jun '03

08 Jun '03

Ok. I've been bit-banging all day and cannot get docprobe to find the DOC chips. This board is a tyan tiger 1832DL 440BX (2x750P3). I'm wonder if there are any known issues with DOC's on the 440bx boards? Or any known issues with any of the lately issued DOC Millinium chips? It looks as if docprobe is a) not recognizing the DOC or b) isn't probing the correct address. (i've fiddled with the high (etc) settings for the driver in the kernel config too.) I've gotten as far as this: Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 89 found at 0xc8000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 31 found at 0xca000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xcc000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xce000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 0C found at 0xd0000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 66 found at 0xd2000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xd4000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xd6000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xd8000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xda000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xdc000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xde000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 00 found at 0xe0000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID C2 found at 0xe2000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 75 found at 0xe4000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 6C found at 0xe6000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xe8000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xea000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xec000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xee000 Jun 7 16:17:16 No recognised DiskOnChip devices found -- Roger http://www.eskimo.com/~roger/index.html

2 3

Additions to list of injuries
by roger 08 Jun '03

08 Jun '03

1) 2-3 index & thumb fingures sustained several stabbings and blood lossage. 1) 1st degree burn. Thumb mysteriously has the letters "WA" imprinted. Could this be evidence that i'm the one that burned a now labeled "A**RD" bios chip? wow. and the darn thing still boots. i wonder if these bios chips could last a trip through the sun and still boot? Amazing as to how many bendings these pins can handle and still not break! -- Roger http://www.eskimo.com/~roger/index.html

1 0

Re: tusl2-c with kernel
by Yap Ee Huey 08 Jun '03

08 Jun '03

Hi , Thansk for the reply. I have been following the list , I noticed that there are two different things RAMTEST and MEMTEST in linuxbios. My linuxbios (on 815ep) passed the RAMTEST few weeks ago. Is there any HOWTO on MEMTEST ? Thanks. Regards, eehuey >From: ron minnich <rminnich(a)lanl.gov> >To: Yap Ee Huey <yapeehuey(a)hotmail.com> >CC: linuxbios(a)clustermatic.org >Subject: Re: tusl2-c with kernel >Date: Fri, 6 Jun 2003 07:40:24 -0600 (MDT) > >Have you just tried memtest first? > >I am wondering if you do in fact have a dram problem. > >ron > _________________________________________________________________ Download the latest MSN Messenger http://messenger.msn.com.my

1 0

PPC
by Greg Watson 07 Jun '03

07 Jun '03

Just thought you might like to know that I booted a linux kernel using linuxbios on a PPC yesterday. There are still a few issues to sort out, but it's looking very promising. For those that are attending USENIX next week, I'll have the machine at the BOF so you can see it really works! Cheers, Greg

2 2

new config language
by ron minnich 06 Jun '03

06 Jun '03

comments welcome. This doc is in the RFC section. ron New config language for LinuxBIOS \begin{abstract} We describe the new configuration language for LinuxBIOS. \end{abstract} \section{Scope} This document defines the new configuration language for LinuxBIOS. \section{Goals} The goals of the new language are these: \begin{itemize} \item Simplified Makefiles so people can see what is set \item Move from the regular-expression-based language to something a bit more comprehensible and flexible \item make the specification easier for people to use and understand \item allow unique register-set-specifiers for each chip \end{itemize} \section{Language} Here is the new language. It is very similar to the old one, differing in only a few respects. It borrows heavily from Greg Watson's suggestions. I am presenting it in a pseudo-BNF in the hopes it will be easier. Things in '' are keywords; things in ``'' are strings in the actual text. \begin{verbatim} #exprs are composed of factor or factor + factor etc. expr ::= factor ( ``+'' factor | ``-'' factor | )* #factors are term or term * term or term / term or ... factor ::= term ( ``*'' term | ``/'' term | ... )* # unary-op ::= ``!'' ID # term is a number, hexnumber, ID, unary-op, or a full-blown expression term ::= NUM | XNUM | ID | unary-op | ``(`` expr ``)'' # Option command. Can be an expression or quote-string. # Options are used in the config tool itself (in expressions and 'if') # and are also passed to the C compiler when building linuxbios. # It is an error to have two option commands in a file. # It is an error to have an option command after the ID has been used # in an expression (i.e. 'set after used' is an error) option ::= 'option' ID '=' (``value'' | term) # Default command. The ID is set to this value if no option command # is scanned. # Multiple defaults for an ID will produce warning, but not errors. # It is OK to scan a default command after use of an ID. # Options always over-ride defaults. default ::= 'default' ID '=' (``value'' | term) # the mainboard, southbridge, northbridge commands # cause sourcing of Config.lb files as in the old config tool # as parts are sourced, a device tree is built. The structure # of the tree is determined by the structure of the components # as they are specified. To attach a superio to a southbridge, for # example, one would do this: # southbridge acer/5432 # superio NSC/123 # end # end # the tool generates static initializers for this hierarchy. # add C code to the current component (motherboard, etc. ) # to initialise the component-INDEPENDENT structure members init ::= 'init' ``CODE'' # add C code to the current component (motherboard, etc. ) # to initialise the component-DEPENDENT structure members register ::= 'register' ``CODE'' # mainboard command # statements in this block will set variables controlling the mainboard, # and will also place components (northbridge etc.) in the device tree # under this mainboard mainboard ::= 'mainboard' PATH (statements)* 'end' # standard linuxbios commands southbridge ::= 'southbridge' PATH (statemnts)* 'end' northbridge ::= 'northbridge' PATH (statemnts)* 'end' superio ::= 'superio PATH (statemnts)* 'end' cpu ::= 'cpu' PATH (statemnts)* 'end' arch ::= 'arch' PATH (statemnts)* 'end' # files for building linuxbios # include a file in crt0.S mainboardinit ::= 'mainboardinit' PATH # object file object ::= 'object' PATH # driver objects are just built into the image in a different way driver ::= 'driver' PATH # Use the Config.lb file in the PATH dir ::= 'dir' PATH # add a file to the set of ldscript files ldscript ::= 'ldscript' PATH # dependencies or actions for the makerule command dep ::= 'dep' ``dependency-string'' act ::= 'act' ``actions'' depsacts ::= (dep | act)* # set up a makerule # makerule ::= 'makerule' PATH depsacts #defines for use in makefiles only # note usable in the config tool, not passed to cc makedefine ::= 'makedefine' ``RAWTEXT'' # add an action to an existing make rule addaction ::= 'addaction' PATH ``ACTION'' # statements statement ::= option | default | cpu | arch | northbridge | southbridge | superio | object | driver | mainboardinit | makerule | makedefine | addaction | init | register | iif | dir | ldscript statements ::= (statement)* # target directory specification target ::= 'target' PATH # and the whole thing board ::= target (option)* mainboard \end{verbatim} A sample file: \begin{verbatim} target x # over-ride the default rom size in the mainboard file option ROM_SIZE=0x100000 mainboard amd/solo end \end{verbatim} Sample mainboard file \begin{verbatim} # ### ### Set all of the defaults for an x86 architecture ### arch i386 end cpu k8 end # option DEBUG=1 default USE_FALLBACK_IMAGE=1 option A=(1+2) option B=0xa # ### ### Build our 16 bit and 32 bit linuxBIOS entry code ### mainboardinit cpu/i386/entry16.inc mainboardinit cpu/i386/entry32.inc ldscript cpu/i386/entry16.lds ldscript cpu/i386/entry32.lds # ### ### Build our reset vector (This is where linuxBIOS is entered) ### if USE_FALLBACK_IMAGE mainboardinit cpu/i386/reset16.inc ldscript cpu/i386/reset16.lds end if USE_NORMAL_IMAGE mainboardinit cpu/i386/reset32.inc ldscript cpu/i386/reset32.lds end . . . if USE_FALLBACK_IMAGE mainboardinit arch/i386/lib/noop_failover.inc end # ### ### Romcc output ### #makerule ./failover.E dep "$(MAINBOARD)/failover.c" act "$(CPP) -I$(TOP)/src $(CPPFLAGS) $(MAINBOARD)/failover.c > ./failever.E" #makerule ./failover.inc dep "./romcc ./failover.E" act "./romcc -O ./failover.E > failover.inc" #mainboardinit ./failover.inc makerule ./auto.E dep "$(MAINBOARD)/auto.c" act "$(CPP) -I$(TOP)/src -$(ROMCCPPFLAGS) $(CPPFLAGS) $(MAINBOARD)/auto.c > ./auto.E" makerule ./auto.inc dep "./romcc ./auto.E" act "./romcc -O ./auto.E > auto.inc" mainboardinit ./auto.inc # ### ### Setup RAM ### mainboardinit ram/ramtest.inc mainboardinit southbridge/amd/amd8111/smbus.inc mainboardinit sdram/generic_dump_spd.inc # ### ### Include the secondary Configuration files ### northbridge amd/amdk8 end southbridge amd/amd8111 end #mainboardinit arch/i386/smp/secondary.inc superio NSC/pc87360 register "com1={1} com2={0} floppy=1 lpt=1 keyboard=1" end dir /pc80 ##dir /src/superio/winbond/w83627hf cpu p5 end cpu p6 end cpu k7 end cpu k8 end # ### ### Build the objects we have code for in this directory. ### ##object mainboard.o driver mainboard.o object static_devices.o if HAVE_MP_TABLE object mptable.o end if HAVE_PIRQ_TABLE object irq_tables.o end ### Location of the DIMM EEPROMS on the SMBUS ### This is fixed into a narrow range by the DIMM package standard. ### option SMBUS_MEM_DEVICE_START=(0xa << 3) option SMBUS_MEM_DEVICE_END=(SMBUS_MEM_DEVICE_START +1) option SMBUS_MEM_DEVICE_INC=1 # ### The linuxBIOS bootloader. ### option PAYLOAD_SIZE = (ROM_SECTION_SIZE - ROM_IMAGE_SIZE) option CONFIG_ROM_STREAM_START = (0xffffffff - ROM_SIZE + ROM_SECTION_OFFSET + 1) # \end{verbatim} I've found the output of the new tool to be easier to handle. Makefile.settings looks like this, for example: \begin{verbatim} TOP:=/home/rminnich/src/yapps2/freebios2 TARGET_DIR:=x export MAINBOARD:=/home/rminnich/src/yapps2/freebios2/src/mainboard/amd/solo export ARCH:=i386 export _RAMBASE:=0x4000 export ROM_IMAGE_SIZE:=65535 export PAYLOAD_SIZE:=131073 export MAX_CPUS:=1 export HEAP_SIZE:=8192 export STACK_SIZE:=8192 export MEMORY_HOLE:=0 export LINUXBIOS_VERSION:=1.1.0 export CC:=$(CROSS_COMPILE)gcc \end{verbatim} In other words, instead of expressions, we see the values. It's easier to deal with.

1 0

tusl2-c with kernel
by Yap Ee Huey 06 Jun '03

06 Jun '03

Hi all, After failing to load with both Etherboot and ADLO, I tried to reduce the size of kernel to 192k bytes ( which can only boot and execute simple command ) to fit into my 256k rom. But after "Jumping to boot code", it reboots. Does that mean my ram initialization is buggy ? Thanks. Below is my log : regards, eehuey Wrote linuxbios table at: 00000500 - 0000065c checksum 2d0c Jumping to linuxbiosmain()... Welcome to start32, the open sourced starter. This space will eventually hold more diagnostic information. January 2000, James Hendricks, Dale Webster, and Ron Minnich. Version 0.1 37:init_bytes() - zkernel_start:0xfffc0000 zkernel_mask:0x0000ffff Gunzip setup gunzip_setup output data is 0x00100000 Gunzipping boot code flush 0x00100000 count 0x00008000 flush 0x00108000 count 0x00008000 flush 0x00110000 count 0x00008000 flush 0x00118000 count 0x00008000 flush 0x00120000 count 0x00008000 flush 0x00128000 count 0x00008000 flush 0x00130000 count 0x00008000 flush 0x00138000 count 0x00008000 flush 0x00140000 count 0x00008000 flush 0x00148000 count 0x00008000 flush 0x00150000 count 0x00008000 flush 0x00158000 count 0x00008000 flush 0x00160000 count 0x00000b30 <990> command line - [root=/dev/hda5] Jumping to boot code LinuxBIOS-1.0.0 Fri Jun 6 20:09:28 EDT 2003 starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 Ram Enable 5 Ram4 Ram5 Ram6 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. _________________________________________________________________ Download the latest MSN Messenger http://messenger.msn.com.my

2 1

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