OpenBIOS September 2004

openbios@openbios.org

8 participants
14 discussions

PCI Enumeration and driver Implementation
by Vishu＠soc-soft.com 30 Sep '04

30 Sep '04

Hi Everyone I need to write PCI Bus Driver for MIPS Embedded Processor. In my case PCI is a built-in device, need to know the details about writing PCI Enumeration -- i.e configuring and enumerating PCI Devices. Should there be any base enumeration to be written in C program if so where is the hook Point in Openbios kernel and then rest in Forth or everything (configuring, enumerating, Reading and writing) needs to be implemented in Forth using PCI Bus Binding according to Open Firmware. Regards Viswa The information contained in this e-mail message and in any annexure is confidential to the recipient and may contain privileged information. If you are not the intended recipient, please notify the sender and delete the message along with any annexure. You should not disclose, copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail are those of the individual sender except where the sender specifically states them to be the views of SoCrates Software India Pvt Ltd., Bangalore.

3 2

How primitive words are getting called?
by Swamy＠soc-soft.com 24 Sep '04

24 Sep '04

Hello, I am unable to understand how the forth words are called? The definitions for forth words are maintained in "char *wordnames[]" of "/kernel/bootstrap.c" and in "/kernel/primitive.c" all the functions for primitive words are defined. When we say "dup" what will be the s/w flow? Please let me know how these two files are interconnected. Please give me some input with regard to this. Thanks and Regards Swamy

2 1

Interpreter and Forth Compilation
by Swamy＠soc-soft.com 21 Sep '04

21 Sep '04

Hi, 1) When I enter a command (e.g. dup) on openbios prompt,how does it get linked to corresponding c function fdup()? I understand that the entered command goes through the outer-interpreter and is finally executed using forth word "execute". I am not able to understand how this "execute" gets linked to fdup(). 2) Please let me know how the forth files are compiled and executed? I understand that all the forth source files (*.fs) are converted to (.dict) files using "./bootstrap" executable and is linked to the kernel. Kindly provide some input with regard to this. Can you please provide some link/document with respect to above Regards Swamy

2 1

Re: [OpenBIOS] Cygwin/Linux issues with openbios-devel-20040919-1800.tar.bz2
by Dwight Schauer 20 Sep '04

20 Sep '04

On Tue, 21 Sep 2004 00:45:22 +0200, Stefan Reinauer <stepan(a)openbios.org <mailto:stepan@openbios.org>> wrote: > * Dwight Schauer <das(a)teegra.net <mailto:das@teegra.net>> [040920 00:28]: > > I got the standalone forth from openbios-devel-20040919-1800.tar.bz2 to > > build and run on Cgywin and Linux. > > > > While building I did get this error (had the same problem on linux as well): > > make[2]: *** No rule to make target > > `../../obj-x86/build/arch/unix/../../fs/libfs.a', needed by > > `../../obj-x86/build/arch/unix/unix'. Stop. > > make[1]: *** [sub-arch/unix-all] Error 2 > > Did you disable all filesystem support? Looks like a bug in the build > system. Thanks for reporting this. I believe so, I was trying for a minimum build so I could play around with it on cygwin. >From .config-x86 # # Filesystem Configuration # # CONFIG_DISK_LABEL is not set > > > { ---------------- start clip ----------------------- } > > 0 > : star [char] * emit ; ok > > 0 > : stars 0 ?do star loop ; ok > > 0 > 5 stars ***** ok > > 0 > 10 stars **************** ok > > 0 > bye > > vs: > > > 0 > : star [char] * emit ; ok > > 0 > : stars 0 ?do star loop ; star isn't unique. > > ok > > 0 > star * ok > > 0 > 5 stars stars: undefined word. > > 0 > bye > > > That time I had a problem. Before I entered the "stars" line I hit up > > arrow, and got the "0 > : star [char] * emit ;" back. > > That is what I'd expect. I then pressed up arrow again and got: "0 >" so > > I figured I was on an empty line. After typing the definition for stars > > again, I got the "star is not unique" warning message. > > Sounds like a problem with the command line module (modules/cmdline.c) > > > On linux it acted the same way. > > I can't reproduce this on my system. What terminal are you > using? > the rxvt that comes with Cygwin. Rxvt v2.7.10 - released: 26 MARCH 2003

1 0

Cygwin/Linux issues with openbios-devel-20040919-1800.tar.bz2
by Dwight Schauer 20 Sep '04

20 Sep '04

I got the standalone forth from openbios-devel-20040919-1800.tar.bz2 to build and run on Cgywin and Linux. While building I did get this error (had the same problem on linux as well): make[2]: *** No rule to make target `../../obj-x86/build/arch/unix/../../fs/libfs.a', needed by `../../obj-x86/build/arch/unix/unix'. Stop. make[1]: *** [sub-arch/unix-all] Error 2 Which I was able to correct by going into fs and doing a make from there. ~/openbios/openbios-devel-20040919-1800/fs $ make Compiling ioglue.o : compiling= gcc -I. -I../obj-x86/include -I./include -I../include -I- -Wall -Wmissing-prototypes -g -O2 -fno-builtin -msoft-float -Wp,-MT,../obj-x86/build/fs/ioglue.o,-MD,../obj-x86/deps/fs/ioglue.P -c ioglue.c -o ../obj-x86/build/fs/ioglue.o ok ofiles=`find ../obj-x86/build/fs/.ardst -name '*.o'` ; \ ar cru ../obj-x86/build/fs/libfs.a_ $ofiles && ranlib ../obj-x86/build/fs/libfs.a_ && mv ../obj-x86/build/fs/libfs.a_ ../obj-x86/build/fs/libfs.a ok After that the top level make completed without problem. (This fixed the build issue on linux as well) so I ran it. { ---------------- start clip ----------------------- } $ make run ./obj-x86/build/arch/unix/unix ./obj-x86/build/arch/unix/unix.dict Welcome to OpenBIOS v1.0.RC1 Built on Sep 19 2004 16:22 Type 'help' for detailed information [unix] Booting default not supported. 0 > : star [char] * emit ; ok 0 > : stars 0 ?do star loop ; ok 0 > 5 stars ***** ok 0 > 10 stars **************** ok 0 > bye Farewell! ok { ---------------- end clip ----------------------- } Ok, no problem there (apart from me being momentarily stumped about hex being the default base, but that makes sense), so I tried it again. { ---------------- start clip ----------------------- } $ make run ./obj-x86/build/arch/unix/unix ./obj-x86/build/arch/unix/unix.dict Welcome to OpenBIOS v1.0.RC1 Built on Sep 19 2004 16:22 Type 'help' for detailed information [unix] Booting default not supported. 0 > : star [char] * emit ; ok 0 > : stars 0 ?do star loop ; star isn't unique. ok 0 > star * ok 0 > 5 stars stars: undefined word. 0 > bye Farewell! ok { ---------------- end clip ----------------------- } That time I had a problem. Before I entered the "stars" line I hit up arrow, and got the "0 > : star [char] * emit ;" back. That is what I'd expect. I then pressed up arrow again and got: "0 >" so I figured I was on an empty line. After typing the definition for stars again, I got the "star is not unique" warning message. On linux it acted the same way.

2 1

FCODE Evaluator
by Swamy＠soc-soft.com 15 Sep '04

15 Sep '04

Hello, In one of your earlier mails (Date: Sat, 24 Jul 2004 02:18:05 +0200), u have mentioned that "FCODE Evaluator" has been already implemented and is part of the kernel. We need to support a PCI device which has a FCODE Driver burnt in ROM. My question is: 1. Will the kernel take care of inserting this PCI Driver and mapping the device? Or else do we need to build some evaluator for this? 2. Can you please name some PCI device which has FCODE driver built in Regards Swamy

3 3

RE: [OpenBIOS] Problem with jumping from assembly to c function
by Vishu＠soc-soft.com 13 Sep '04

13 Sep '04

Hi Stefan I'm able to cross compile the OpenBios Kernel for mips board but I cannot mention for which board right now. Sorry to tell this since my company doesn't allow me to expose u the facts. I was successful in doing so with some changes in Makefiles and kept only /openbios/forth and /openbios/kernel. Within these folders I made changes for Host compilation and Target Compilation. The compile image is to boot from RAM right now Initial stage since I wanted to know the kernel booting on the Target Board. Later on I would like to Compile for ROM and run on RAM. For this we have to write a linker file for relocatable code. The problem right now I'm facing is that 1. openbios.full contains "/openbios/obj-mips/kernel/openfirmware.dict" as the final compiled image which is converted to SREC format and downloaded On the Target Board. 2. But it is not including the "/openbios/obj-mips/forth/openfirmware.dict". Copied this file manually from the said directory to "/openbios/obj-mips/kernel/" and tried to boot it used to hang. The same problem is there in X86 system, i cross verified through grub loader as well as for the Target Board. I'm waiting for the reply..... Regards Viswanath -----Original Message----- From: openbios-bounces+vishu=soc-soft.com(a)lists.openbios.org [mailto:openbios-bounces+vishu=soc-soft.com@lists.openbios.org] On Behalf Of Stefan Reinauer Sent: Monday, September 13, 2004 5:26 PM To: The OpenBIOS Mailinglist Subject: Re: [OpenBIOS] Problem with jumping from assembly to c function Hi Viswanath, * Vishu(a)soc-soft.com <Vishu(a)soc-soft.com> [040908 12:03]: > For my previous mail of cross compiling the kernel for mips board. I > resolved the issue As u mentioned of on HOSTCC and CC for Target. > > Is there any other way of compiling forth sources. You can choose a system with the same bit width (32/64bit) and and endianess (big/little endian) and compile the dictionary natively there. Otherwise you will have to wait until OpenBIOS supports cross compiling officially. > And after cross compilation I am facing the problem of jumping from > boot.s to main. Somehow Succeeded in jumping to cmain function. > Openbios function is called from cmain during this period > Context is saved is it necessary to initialize global pointer. Because > once it goes to cmain after some > Execution of instructions the global pointer gets manipulated and > exception occurs. Why is it so. Do you get any output before this? Did you initialize the stack properly in or before boot.S? > But in /arch/x86 example there is only the initilization of stack > pointer. Do u have any example for Cross compilation procedure and > linking the linker script to download to ROM or RAM. Have a look at the current version at http://www.openbios.org/snapshots/ Relocation from rom to ram is currently only done by the underlying ELF loader (ie LinuxBIOS) but we want to support more in the future. Any concrete ideas / patches are welcome. Stefan -- OpenBIOS http://openbios.org/ Mailinglist: http://lists.openbios.org/ Free your System - May the Forth be with you

1 0

RE: [OpenBIOS] How to enable print statement in the openbios-kernel?
by Swamy＠soc-soft.com 13 Sep '04

13 Sep '04

==>So you are not cross compiling? No, I am using GCC for compilation version - gcc-g77-2.96-110 ==>So you cannot even build all of openbios on your machine? When I compile the kernel with option "#define DEBUG_CONSOLE" (/kernel/include/config.h), it compiles fine. But, If I add single "printk" statements in the each of the functions processxt(), next(), enterforth() in the file /kernel/kernel/internal.c it hangs.... ALSO If I add DEBUG_INTERPRETER OR DEBUG_INTERNAL it still hangs....the output I have mailed at the bottom. ==>Where_ does it hang? - # make Welcome to OpenBIOS.. Creating build directory /home/shon/openbios/obj-x86/kernel Checking types...found 32bit platform, creating "types.h" Endianess definition: glibc. Dynamic linker functions provided by libdl Building common core files for architecture x86 compiling primitives.c... ok compiling stack.c... ok compiling dict.c... ok compiling lib.c... ok compiling openbios.c... ok compiling bootstrap.c... ok linking bootstrap... ok Bootstrapping dictionary... ok Building final dictionary... ok Building binary converter... ok Compiling x86 architecture specific binaries assembling mboot.S... ok compiling multiboot.c... ok assembling boot.S... ok compiling plainboot.c... ok generating linkable dictionary... ok compiling builtin.c... ok compiling console.c... ok Linking: native multiboot kernel for grub... ok native kernel (for LinuxBIOS)... ok native kernel with dictionary... ok Building files for unix hosted bootstrap compiling unix.c... ok compiling plugins.c... ok linking unix bootstrap... ok Building plugins compiling loader.c... ok OpenBIOS build finished for platform x86. Building forth sources: Adding lib specific forth code to dictionary... ok Adding device specific forth code to dictionary... COMPILATION HANGS AT THIS POSITION..........

2 1

RE: [OpenBIOS] How to enable print statement in the openbios-kernel?
by Swamy＠soc-soft.com 13 Sep '04

13 Sep '04

what platform are you using, what compiler? -I am working on Linux (x86). I am using the command "make" to compile the image. what did you try to do? -I need to watch the kernel flow using printk statements what was the exact output? -If I do "make" it takes too much time to compile and will not come out at all for hours. * Swamy(a)soc-soft.com <Swamy(a)soc-soft.com> [040908 11:59]: > > The path is: openbios/kernel/kernel/openbios.c > If this file is not called, Plz let me know the procedure to watch the > print statements of this file? Basically I need to watch the kernel > flow. openbios.c is called. And it's printk statements work fine for me. Can you please be a bit more detailed? - what platform are you using, what compiler? - what did you try to do? - what was the exact output? Please use the snapshots from http://www.openbios.org/snapshots/ Stefan -- OpenBIOS http://openbios.org/ Mailinglist: http://lists.openbios.org/ Free your System - May the Forth be with you

2 1

Problem with jumping from assembly to c function
by Vishu＠soc-soft.com 13 Sep '04

13 Sep '04

Hi stefan For my previous mail of cross compiling the kernel for mips board. I resolved the issue As u mentioned of on HOSTCC and CC for Target. Is there any other way of compiling forth sources. If so how to eliminate the Hosted compilation Directory i.e. unix directory which is in kernel-1.1/arch/unix. And after cross compilation I am facing the problem of jumping from boot.s to main. Somehow Succeeded in jumping to cmain function. Openbios function is called from cmain during this period Context is saved is it necessary to initialize global pointer. Because once it goes to cmain after some Execution of instructions the global pointer gets manipulated and exception occurs. Why is it so. For example Boot.s contains this RAM address Mnemonics Instructions a0100044: 3c1ca011 lui gp,0xa011 /* Loads the global pointer address */ a0100048: 279c40c8 addiu gp,gp,16584 a010004c: 8f8880a4 lw t0,-32604(gp) /* get the address of cmain which is stored in to (temp register) */ a0100050: 01000008 jr t0 /* jumps to main */ a0100070 <cmain>: a0100070: 3c1c0001 lui gp,0x1 /* don't know why gp is loaded with 0x1 */ a0100074: 279c4058 addiu gp,gp,16472 a0100078: 0399e021 addu gp,gp,t9 a010007c: 27bdffe0 addiu sp,sp,-32 a0100080: afbc0010 sw gp,16(sp) a0100084: 8f848010 lw a0,-32752(gp) /* after this instruction exception is occuring and jumping to 0x80000000 address (RAM) */ a0100088: 00000000 nop But in /arch/x86 example there is only the initilization of stack pointer. Do u have any example for Cross compilation procedure and linking the linker script to download to ROM or RAM. Regards Viswanath

3 2