August 2012 - OpenBIOS - mail.coreboot.org

Re: [OpenBIOS] [Qemu-ppc] FreeBSD powerpc issue
by Andreas TObler Aug. 25, 2012

Aug. 25, 2012

On 08/25/12 11:00, Blue Swirl wrote: > On Fri, Aug 24, 2012 at 9:45 PM, Andreas Tobler <andreast(a)fgznet.ch> wrote: >> Hello, >> >> I'm trying to get FreeBSD powerpc running with qemu. >> So far it loads the fbsd loader and the loader loads the kernel. >> The kernel starts booting but it hangs in an endless loop. It tries to print >> out a fatal_trap but it looks like the 'of' doesn't work properly (anymore?) >> at this stage. >> >> I have a remote debugger attached to the kernel and I can see where it >> hangs. But I can not figure out what caused the fatal trap here. >> >> An 'info registers' in qemu shows the srr0=fff025a4, this, as I understand, >> points to of_client_callback from OpenBIOS. (objdump -dS >> openbios-qemu.nostrip gives me this.) >> >> qemu is on 1.1.90, iow, a git snapshot from yesterday with OpenBIOS from >> 19th of aug. >> >> Is there a possibilty to 'debug' the OpenBIOS somehow? > > CCing OpenBIOS list too. > > We have a built-in debugger in OpenBIOS (maybe not well documented). > Then there's DEBUG_CIF in libopenbios/client.c and it should be > possible to add debugging print statements to forth/system/ciface.fs > too. Oh, thank you. I'll take a look when I'm back on the machine. >> I'm not sure whether it is a kernel issue or an OpenBIOS issue. > > The problem could be that there's a MMU fault when the kernel calls > OpenBIOS, maybe because OpenBIOS is no longer mapped (MMU disabled?) > and then the above debugging would not help. Hm, from the FreeBSD kernel code view, I passed several 'of' calls to read the memory regions etc. to map memory. That said, OB is working fine for the start. I'm not sure where it happens, the fault above. It might be when I start to call 'of' again after I have started the MMU on the FreeBSD kernel side. So, to my understanding, you say it might be an MMU fault, that OB is no longer mapped? Who would be the responsible for this mapping, the FreeBSD kernel or OB? Thanks a lot! Andreas

2 1

Re: [OpenBIOS] [Qemu-ppc] FreeBSD powerpc issue
by Andreas Tobler Aug. 25, 2012

Aug. 25, 2012

On 08/25/12 12:05, Blue Swirl wrote: > On Sat, Aug 25, 2012 at 9:47 AM, Andreas TObler <andreast(a)fgznet.ch> wrote: >> On 08/25/12 11:00, Blue Swirl wrote: >>> >>> On Fri, Aug 24, 2012 at 9:45 PM, Andreas Tobler <andreast(a)fgznet.ch> >>> wrote: >>>> >>>> Hello, >>>> >>>> I'm trying to get FreeBSD powerpc running with qemu. >>>> So far it loads the fbsd loader and the loader loads the kernel. >>>> The kernel starts booting but it hangs in an endless loop. It tries to >>>> print >>>> out a fatal_trap but it looks like the 'of' doesn't work properly >>>> (anymore?) >>>> at this stage. >>>> >>>> I have a remote debugger attached to the kernel and I can see where it >>>> hangs. But I can not figure out what caused the fatal trap here. >>>> >>>> An 'info registers' in qemu shows the srr0=fff025a4, this, as I >>>> understand, >>>> points to of_client_callback from OpenBIOS. (objdump -dS >>>> openbios-qemu.nostrip gives me this.) >>>> >>>> qemu is on 1.1.90, iow, a git snapshot from yesterday with OpenBIOS from >>>> 19th of aug. >>>> >>>> Is there a possibilty to 'debug' the OpenBIOS somehow? >>> >>> >>> CCing OpenBIOS list too. >>> >>> We have a built-in debugger in OpenBIOS (maybe not well documented). >>> Then there's DEBUG_CIF in libopenbios/client.c and it should be >>> possible to add debugging print statements to forth/system/ciface.fs >>> too. >> >> >> Oh, thank you. I'll take a look when I'm back on the machine. >> >> >>>> I'm not sure whether it is a kernel issue or an OpenBIOS issue. >>> >>> >>> The problem could be that there's a MMU fault when the kernel calls >>> OpenBIOS, maybe because OpenBIOS is no longer mapped (MMU disabled?) >>> and then the above debugging would not help. >> >> >> Hm, from the FreeBSD kernel code view, I passed several 'of' calls to read >> the memory regions etc. to map memory. That said, OB is working fine for the >> start. >> I'm not sure where it happens, the fault above. It might be when I start to >> call 'of' again after I have started the MMU on the FreeBSD kernel side. >> >> So, to my understanding, you say it might be an MMU fault, that OB is no >> longer mapped? Who would be the responsible for this mapping, the FreeBSD >> kernel or OB? > > Assuming that SRR0 is the fault address (I'm not so familiar with > PPC), since it's pointing to the low level entry point this could make > sense. Ok. > At least on Sparc, the kernel should save the original MMU mappings > and restore them on point of entry to OpenBIOS. Alternatively, you > could try to arrange the code so that after you take control of MMU, > OpenBIOS is not used anymore. For example, Linux builds an internal > model of the Open Firmware tree and does not use the OF calls for OF > tree lookup after the initial probe. I'd suppose NetBSD and OpenBSD > kernel code could be used for reference since they work on PPC (real > machines at least, I haven't tried on QEMU). This exact code (FreeBSD kernel) is working on real G3/4/5, namely here on an imac G3, on a PowerBook G4 and on several UP and SMP G5s. We use often 'of' calls even after starting the MMU in the kernel on real machines. But it is not said that this code is 100% bullet proof. I try to dive in a bit more and investigate the MMU mappings when entering 'of'. Thanks again! Andreas

1 0

Re: [OpenBIOS] [Qemu-ppc] FreeBSD powerpc issue
by Blue Swirl Aug. 25, 2012

Aug. 25, 2012

On Fri, Aug 24, 2012 at 9:45 PM, Andreas Tobler <andreast(a)fgznet.ch> wrote: > Hello, > > I'm trying to get FreeBSD powerpc running with qemu. > So far it loads the fbsd loader and the loader loads the kernel. > The kernel starts booting but it hangs in an endless loop. It tries to print > out a fatal_trap but it looks like the 'of' doesn't work properly (anymore?) > at this stage. > > I have a remote debugger attached to the kernel and I can see where it > hangs. But I can not figure out what caused the fatal trap here. > > An 'info registers' in qemu shows the srr0=fff025a4, this, as I understand, > points to of_client_callback from OpenBIOS. (objdump -dS > openbios-qemu.nostrip gives me this.) > > qemu is on 1.1.90, iow, a git snapshot from yesterday with OpenBIOS from > 19th of aug. > > Is there a possibilty to 'debug' the OpenBIOS somehow? CCing OpenBIOS list too. We have a built-in debugger in OpenBIOS (maybe not well documented). Then there's DEBUG_CIF in libopenbios/client.c and it should be possible to add debugging print statements to forth/system/ciface.fs too. > > I'm not sure whether it is a kernel issue or an OpenBIOS issue. The problem could be that there's a MMU fault when the kernel calls OpenBIOS, maybe because OpenBIOS is no longer mapped (MMU disabled?) and then the above debugging would not help. > > Any hint is welcome. > > TIA, > Andreas > > Here some info, it might help... > > telnet localhost 1200 > Trying ::1... > Connected to localhost. > Escape character is '^]'. >>> Configuration device id QEMU version 1 machine id 2 >>> CPUs: 1 >>> Memory: 255M >>> UUID: 00000000-0000-0000-0000-000000000000 >>> CPU type PowerPC,750 > Welcome to OpenBIOS v1.0 built on Aug 19 2012 13:11 > Trying cd:,\\:tbxi... > Consoles: Open Firmware console > > FreeBSD/powerpc Open Firmware loader, Revision 0.1 > (root(a)tcx58.andreas.nets, Sun Aug 19 10:32:07 CEST 2012) > Memory: 261120KB > Booted from: cd > > Loading /boot/defaults/loader.conf > /boot/kernel/kernel text=0xb1ff27 data=0x5ff60+0x1ac7d0 > syms=[0x4+0x8c690+0x4+0xae1e0] > / > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Kernel entry at 0x100100 ... > KDB: debugger backends: ddb > KDB: current backend: ddb > > > QEMU 1.1.90 monitor - type 'help' for more information > (qemu) info registers > NIP 009463ec LR 009463b0 CTR 0094638c XER 00000000 > MSR 00001032 HID0 00000000 HF 00000000 idx 1 > TB 00000000 1000640182 DECR 3294327117 > GPR00 0000000000000001 0000000000c7ba00 0000000080020400 000000000fd00000 > GPR04 00000000005b5128 000000000094638c 00000000005b5128 0000000000c7bab0 > GPR08 000000000fd00000 0000000000c7bab0 0000000000000000 0000000000c7ba00 > GPR12 000000000de9bba0 0000000000000000 00000000fff30714 00000000fff30ec8 > GPR16 00000000fff2f256 0000000004000000 00000000fffb36cc 00000000fffb3ecc > GPR20 0000000000f68000 0000000000000004 00000000fff2f03f 00000000fff2efbf > GPR24 00000000fff2f047 00000000fffb3630 0000000001c2f3b0 0000000001c325a8 > GPR28 0000000080020002 0000000000805180 00000000f97ff97f 0000000000c7ba00 > CR 40003034 [ G - - - EO - EO G ] RES ffffffff > FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > FPSCR 00000000 > SRR0 fff025a4 SRR1 40003030 PVR 00080301 VRSAVE 00000000 > SPRG0 0fd00000 SPRG1 00c7c090 SPRG2 0094e3f0 SPRG3 00000400 > SPRG4 00000000 SPRG5 00000000 SPRG6 00000000 SPRG7 00000000 > SDR1 0100001f > > >

1 0

C's continue statement in Forth?
by Programmingkid Aug. 24, 2012

Aug. 24, 2012

I was wondering if there is a way to implement C's continue statement in Forth. I have this loop, and some times I only want to execute part of it, and then continue on to the next iteration without finishing the current iteration. Is there any way of doing this in OpenBIOS? Example: begin \ condition while \ conditional code if CONTINUE \ skip rest of loop then \ rest of loop ... repeat My guess to a possible solution would be to manipulate the return stack. Any body have any ideas?

2 1

Re: [OpenBIOS] Building OpenBIOS - OS list
by Programmingkid Aug. 21, 2012

Aug. 21, 2012

On Aug 13, 2012, at 12:08 PM, openbios-request(a)openbios.org wrote: > Date: Mon, 13 Aug 2012 08:54:10 -0700 (PDT) > From: Kenneth Salerno <kennethsalerno(a)yahoo.com> > To: The OpenBIOS Mailinglist <openbios(a)openbios.org> > Subject: Re: [OpenBIOS] Building OpenBIOS - OS list > Message-ID: > <1344873250.64301.YahooMailClassic(a)web110401.mail.gq1.yahoo.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > > I have a cross-compiler chain on 32-bit Windows XP using Cygwin that I use to build OpenBIOS. > > Attached are my scripts for ppc64/ppc, sparc64/sparc, s390x/s390, x86_64/x86. > > Also attached are two patches for OpenBIOS to build correctly with this Cygwin environment (one is just to set options and point to my cross-compilers but the other more importantly fixes some ldscripts so I can use my 64-bit/32-bit cross-compilers correctly to build the 32-bit OpenBIOS roms instead of linking to the default 64-bit C run-time). > > Ken Thanks for the reply. I'm glad to see other OS's can build OpenBIOS. I just hope Mac OS X will be one of them some day. My knowledge of how OpenBIOS is built is limited, so trying to fix the problem myself would be next to impossible.

3 3

Re: [OpenBIOS] Help with building
by Andreas Färber Aug. 21, 2012

Aug. 21, 2012

Am 20.08.2012 21:41, schrieb Blue Swirl: > On Sun, Aug 19, 2012 at 10:15 PM, Programmingkid > <programmingkidx(a)gmail.com> wrote: >> When I try to build OpenBIOS, I see this error message: >> >> Building OpenBIOS for x86 >> Building...error: >> GEN target/include/openbios-version.h >> GEN forth/version.fs >> HOSTCC host/kernel/dict.o >> HOSTCC host/kernel/bootstrap.o >> HOSTCC host/kernel/forth.o >> HOSTCC host/kernel/stack.o >> HOSTCC forthstrap >> GEN bootstrap.dict >> panic: segmentation violation at 0x30061c >> dict=0x100300000 here=0x100300628(dict+0x628) pc=0x0(dict+0xffd00000) > > It looks like this is 64 bit host but the x86 target is 32 bits. > Please try amd64 target. The underlying issue then probably is that on Mac OS X it is not properly recognized whether we're building for x86 or x86_64? Andreas >> Here are the details: >> OS: Mac OS 10.6 >> gcc -v: 4.2.1 >> target: unix-x86 -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

1 0

[commit] r1063 - trunk/openbios-devel/arch/ppc/qemu
by repository service Aug. 20, 2012

Aug. 20, 2012

Author: agraf Date: Tue Aug 21 00:29:42 2012 New Revision: 1063 URL: http://tracker.coreboot.org/trac/openbios/changeset/1063 Log: ppc qemu: Increase PCI hole for heathrow The heathrow machine needs more PCI hole space than we provide. Increase its range by a bit. IIUC this still doesn't reflect the actual hole size, but neither do the Mac99 machines. We should probably compare values with the real hardware again. Signed-off-by: Alexander Graf <agraf(a)suse.de> Modified: trunk/openbios-devel/arch/ppc/qemu/init.c Modified: trunk/openbios-devel/arch/ppc/qemu/init.c ============================================================================== --- trunk/openbios-devel/arch/ppc/qemu/init.c Sun Aug 19 15:25:31 2012 (r1062) +++ trunk/openbios-devel/arch/ppc/qemu/init.c Tue Aug 21 00:29:42 2012 (r1063) @@ -144,7 +144,7 @@ .cfg_len = 0x7f000000, .host_mem_base = 0x80000000, .pci_mem_base = 0x80000000, - .mem_len = 0x01000000, + .mem_len = 0x10000000, .io_base = 0xfe000000, .io_len = 0x00800000, .rbase = 0xfd000000,

1 0

Help with building
by Programmingkid Aug. 20, 2012

Aug. 20, 2012

When I try to build OpenBIOS, I see this error message: Building OpenBIOS for x86 Building...error: GEN target/include/openbios-version.h GEN forth/version.fs HOSTCC host/kernel/dict.o HOSTCC host/kernel/bootstrap.o HOSTCC host/kernel/forth.o HOSTCC host/kernel/stack.o HOSTCC forthstrap GEN bootstrap.dict panic: segmentation violation at 0x30061c dict=0x100300000 here=0x100300628(dict+0x628) pc=0x0(dict+0xffd00000) dstackcnt=0 rstackcnt=0 instruction=deadbeef dstack: 0x0 rstack: 0x0 Writing dictionary core file make[1]: *** [bootstrap.dict] Error 1 make: *** [build] Error 1 Anyone know where the building fails? Here are the details: OS: Mac OS 10.6 gcc -v: 4.2.1 target: unix-x86

2 1

[PATCH] fix ppc builds with ppc64 compiler and ppc64 linker
by Kenneth Salerno Aug. 19, 2012

Aug. 19, 2012

Need to specify ppc object code output arch (gcc/as -m32) and 32-bit C run-time (ldscript arch) when using ppc64 compiler and linker. Signed-of-by: Kenneth Salerno <kennethsalerno(a)yahoo.com> --- a/config/scripts/switch-arch 2012-08-14 10:33:34.859375000 -0400 +++ b/config/scripts/switch-arch 2012-08-14 10:34:45.375000000 -0400 @@ -232,11 +232,12 @@ ppc) select_prefix powerpc if [ "$unix" = "no" ]; then - CFLAGS="-msoft-float -fno-builtin-bcopy -fno-builtin-log2" + CFLAGS="-m32 -msoft-float -fno-builtin-bcopy -fno-builtin-log2" + AS_FLAGS="-m32" else CFLAGS="-fno-builtin" + AS_FLAGS= fi - AS_FLAGS= ;; ppc64) --- a/arch/ppc/qemu/ldscript 2012-08-14 10:30:42.046875000 -0400 +++ b/arch/ppc/qemu/ldscript 2012-08-14 10:30:20.218750000 -0400 @@ -1,5 +1,5 @@ OUTPUT_FORMAT(elf32-powerpc) -OUTPUT_ARCH(powerpc) +OUTPUT_ARCH(powerpc:common) /* Initial load address */

2 1

[commit] r1062 - in trunk/openbios-devel: arch/ppc/qemu config/scripts
by repository service Aug. 19, 2012

Aug. 19, 2012

Author: blueswirl Date: Sun Aug 19 15:25:31 2012 New Revision: 1062 URL: http://tracker.coreboot.org/trac/openbios/changeset/1062 Log: fix ppc builds with ppc64 compiler and ppc64 linker Need to specify ppc object code output arch (gcc/as -m32) and 32-bit C run-time (ldscript arch) when using ppc64 compiler and linker. Signed-of-by: Kenneth Salerno <kennethsalerno(a)yahoo.com> Signed-off-by: Blue Swirl <blauwirbel(a)gmail.com> Modified: trunk/openbios-devel/arch/ppc/qemu/ldscript trunk/openbios-devel/config/scripts/switch-arch Modified: trunk/openbios-devel/arch/ppc/qemu/ldscript ============================================================================== --- trunk/openbios-devel/arch/ppc/qemu/ldscript Sat Jun 9 19:05:32 2012 (r1061) +++ trunk/openbios-devel/arch/ppc/qemu/ldscript Sun Aug 19 15:25:31 2012 (r1062) @@ -1,5 +1,5 @@ OUTPUT_FORMAT(elf32-powerpc) -OUTPUT_ARCH(powerpc) +OUTPUT_ARCH(powerpc:common) /* Initial load address */ Modified: trunk/openbios-devel/config/scripts/switch-arch ============================================================================== --- trunk/openbios-devel/config/scripts/switch-arch Sat Jun 9 19:05:32 2012 (r1061) +++ trunk/openbios-devel/config/scripts/switch-arch Sun Aug 19 15:25:31 2012 (r1062) @@ -232,11 +232,12 @@ ppc) select_prefix powerpc if [ "$unix" = "no" ]; then - CFLAGS="-msoft-float -fno-builtin-bcopy -fno-builtin-log2" + CFLAGS="-m32 -msoft-float -fno-builtin-bcopy -fno-builtin-log2" + AS_FLAGS="-m32" else CFLAGS="-fno-builtin" + AS_FLAGS= fi - AS_FLAGS= ;; ppc64)

1 0