openfirmware

openfirmware@openfirmware.info

3007 discussions

Trap Question about booting
by Jean-François Bachelet (Voxel) 20 Jan '21

20 Jan '21

Hello ^^) here is the problem : I have an openfirmware machine with enormous boot disks, 3 to 8 TB big disks. even the smallest 3 TB disk have 20 bootable partitions on it, of various filesystems types. problem is that I can't boot from it as the boot part recog fail at the 13th partition and doesn't go further and return to of shell. an idea why this happens ? is it a limitation of openfirmware ? is there a solution for this ? Thanks by advance, Jeff

3 4

Question about OF
by Jean-François Bachelet (Voxel) 20 Jan '21

20 Jan '21

Hello ^^) When I look at the Openfirmware sources, there are a lot of FS listed as supported but only a few are in the fs folder (ext2, grubfs, hfs, hfsplus and iso9660) where can I find all the others ? (FFS, SFS, NTFS, etc...) Thanks by advance, Jeff

1 0

Support for real hardware.
by Andrew Back 17 Feb '20

17 Feb '20

Hello, Apologies if the answer should be obvious, but I wondered if Open Firmware could be used with any real hardware in a practical sense? E.g. as a Coreboot payload and then used to load Linux, *BSD or Plan 9. Regards, Andrew

1 0

Using OFW for Pegasos2 emulation and as generic PPC firmware in QEMU
by BALATON Zoltan 17 Sep '19

17 Sep '19

Hello, I'm trying to use OFW for the Pegasos2 emulation in QEMU that I'm working on but at the same time I'm trying to make this generic with the promise that it could later be used for other machines emulated by QEMU as well (such as 40p and Macs and maybe even sparc machines but for those compiling the OBP sources may be better as these two seem to have diverged too much, so this is only for PPC now and mainly focusing on Pegasos2 at first). Starting from Artyom's prep/qemu port I've got something starting but it's not working yet and I have several questions and need some advice on how to continue. My current work in progress code is here: https://github.com/zbalaton/openfirmware/tree/master/cpu/ppc/qemu that can be tested with the currently off-tree pegasos2 emulation from: https://osdn.net/projects/qmiga/scm/git/qemu/tree/pegasos2/ (this is QEMU with WIP pegasos2 patch) only needed to compile with configure --target-list=ppc-softmmu to get qemu-system-ppc with pegasos2 machine, then it can be tested with: qemu-system-ppc -M pegasos2 -m 512 -bios qofwppc.rom -serial stdio where qofwppc.rom is what's built from the above OFW fork. More info on the Pegasos2 emulation can be found here: https://osdn.net/projects/qmiga/wiki/SubprojectPegasos2 To keep it generic and easy to adapt in the future to other machines I'm trying to do what SLOF does and use a flattened DTB to pass initial parameters from QEMU to OFW and start from there instead of detecting hardware as it would be done on a real machine. (Since this is only for QEMU emulated machines, a lot of low level hardware init and testing that OFW would normally do on real hadrware can be skipped as those are not needed for a virtual machine.) I've attempted to port SLOF's fdt parsing, which is in fdt.fth. It's able to create the initial device tree but may have some problems so it needs to be reviewed by someone who knows OFW. The rest is mostly a cut down version of cpu/ppc/prep/qemu with as much machine specific parts removed as I could. The idea I've tried was to put machine specifics in a drop-in (so a generic rom could be built for similar machines that would load the appropriate driver based on the device tree it got from QEMU or it would be easy to build different roms for different machines with common parts still being the same). I only have one such driver now: the pegasos2.bth implements that drop-in but some code I could not put in there as those do not seem to work in fc file so those are now in pegasos2.fth. Ideally these should also be in the machine specific driver but I'm not sure that's possible. If not then maybe the above idea can't work and we'll need separate rom image for each machine but maybe there are some Forth tricks I'm not aware of to make this work. Currently this gets to an OFW prompt but detecting pci devices does not work yet. With the default (for pegasos2) cirrus vga a /pci/vga device node is created but I think it stops during that and does not detect any more pci devices. With -vga std (that's the normal QEMU Bochs compatible VGA) it freezes during init-ing the card and with my experimental -vga none -device ati-vga (that's also upstream in QEMU now) an unnamed node is created so something is wrong with PCI probing at the moment. Could it be because not properly doing memory scrub&release? The the prep/qemu rom has some code for this and SLOF fdt code also has some parts to handle that but I did not understand how this should work so I've disabled these but it could be this causes problems with memory management later? Once this can be made working and would get PCI devices detected next question is if it would be possible to emulate the board's original firmware that the OSes running on it expect. It's an OpenFirmware implementation (SmartFirmware) but properties may be slightly different so it may be necessary to change some properties to match that but I'm not sure what's the best way to do that. Lastly once Pegasos2 works I may be interested in trying to make this work with the emulated Mac machines in QEMU as well but it seems drivers for that would be needed as those are not included in the OFW sources so it may be a bigger task so for now I focus on Pegasos2 but keeping it open for future enhancement. I think I need more understanding on how OFW works and if the above is possible at all or how to debug it further so I hope someone here can provide some insight or answer my questions to get me over these hurdles. (I've already read http://wiki.laptop.org/go/Forth_Lessons which was a great introduction also discussing OFW implementation details but that still left me with a lot of pieces missing so I'd need some more help.) Thank you, BALATON Zoltan

2 4

Porting ofw to custom board
by Max Ruttenberg 30 Nov '17

30 Nov '17

Hi all, I'm interested in porting ofw to a board with QorIQ ppce5500 processor. The board currently uses U-Boot as its primary and secondary boot loader. Is it possible to boot into an ofw image from U-Boot? Is there a porting guide? Thank you, Max -- Max Ruttenberg, Member of the Technical Staff Emu Technology 270 W 39th St. #1302 New York, NY 10018

2 1

OpenFirmware - PS/2 keyboard
by Samuel Hodgkins 27 Feb '17

27 Feb '17

So, I've been experimenting with booting OpenFirmware on some random x86 hardware. Chainloading it from GRUB works and is simple and loads to the grey/white 'Open Firmware' screem with an 'ok' prompt near the top and the cursor blinking in the absolute top-right of the screen. However, I can't seem to type anything into the 'ok' prompt. As the tested machine does not have a USB keyboard but a PS/2 one, do I need to alter the configuration to build a PS/2 driver into ofwgrub.elf?

2 1

get-inherited-property broken?
by Artyom Tarasenko 13 Jan '17

13 Jan '17

on the current git: ok " addresses-preassigned" get-inherited-property . ffffffff ok " someweirdnonxisting" get-inherited-property . ffffffff ok " whatever" get-inherited-property . ffffffff Looks like a bug. -- Regards, Artyom Tarasenko SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu

1 1

[OpenFirmware] [ARM] [Qemu] Cannot build OpenFirmware for ARM using make
by John Fisherman 25 Oct '16

25 Oct '16

Hello all, I am currently facing an issue to build OpenFirmware for ARM. Let’s start with some explanations : My goal is to have a Forth interpreter running on a barebone ARM device. I’ve tried some, like ForthOS (which runs on x86 only) and another one designed for the Raspberry Pi which is far for being complete. So, I’ve been following two of your official tutorials : - https://www.openfirmware.info/Building_OFW_for_QEMU - https://www.openfirmware.info/Building_OFW_for_ARM Got to say the first one worked well, except it is not stated that “subversion” is required, but we can easily find it out by ourselves. At the end, I got OpenFirmware running and have been able to type some Forth commands on the interpreter. Then, I tried to reproduce this with ARM Qemu. Fell on the second tutorial, which is somewhat less detailed than the first one, but optionnal configuration on the first one should also be viable for the ARM’s one. Well, my issue comes when executing the “make” command inside “openfirmware/cpu/x86/pc/emu/build”. Here is what I get : *jacky@debiannos:~/openfirmware/cpu/arm/mmp2/build$ make* *./build ofw.rom* *--- Rebuilding sp.img* *--- Cmd: ${HOSTDIR}/forth ${HOSTDIR}/../build/builder.dic ../sp.bth* *--- Rebuilding fw.img* *--- Cmd: ${HOSTDIR}/armforth ${BP}/cpu/arm/build/basefw.dic ../fw.bth* *sh: 1: /home/jacky/openfirmware/cpu/x86/Linux/armforth: not found* *Makefile:22: recipe for target 'ofw.rom' failed* *make: *** [ofw.rom] Error 1* *jacky@debiannos:~/openfirmware/cpu/arm/mmp2/build$ * At first I tought it was due to script’s or environment’s variable like ${HOSTDIR} as this was the line causing the error. It seemed those variables were correctly replaced in the script itself, as a previous line is well executed using this same variable. Next, I’ve been looking for openfirmware/cpu/x86/Linux/armforth file. As the error states, this file is not present in the cpu/x86/Linux folder. In fact, there is a file named like this, but it has an extension .qemu (the complete file name is armforth.qemu. So I tough about a simple mistake, and renamed it (in fact, I copied it to avoid other errors) into armforth. Once renamed, I did “make clean”, and relaunched a “make”. The previous error disappeared, the script went farther, but still did not complete : *jacky@debiannos:~/openfirmware/cpu/arm/mmp2/build$ make* *./build ofw.rom* *--- Rebuilding sp.img* *--- Cmd: ${HOSTDIR}/forth ${HOSTDIR}/../build/builder.dic ../sp.bth* *--- Rebuilding fw.img* *--- Cmd: ${HOSTDIR}/armforth ${BP}/cpu/arm/build/basefw.dic ../fw.bth* *${BP}/cpu/arm/mmp2/rootnode.fth:32: io2-va ?* *${BP}/cpu/arm/mmp2/rootnode.fth:36: io-va ?* *${BP}/cpu/arm/mmp2/mmuon.fth:12: fw-mem-va ?* *${BP}/cpu/arm/mmp2/mmuon.fth:12: page-table-offset ?* *${BP}/cpu/arm/mmp2/mmuon.fth:13: page-table-va ?* *Makefile:22: recipe for target 'ofw.rom' failed* *make: *** [ofw.rom] Error 1* *jacky@debiannos:~/openfirmware/cpu/arm/mmp2/build$* These errors appears to be forth-related, as if some words were not defined. Maybe is it due to the *basefw.dic *dictionnary… To be honest, I can’t think about any other solutions. Maybe I will dig into these forth files but I am afraid it will be a loss of time as I am a real beginner to Forth. Here’s what I tried : - Executing make as root. Same issue. - Executing it on another distro (Ubuntu 14.x). Same issue. - Tried different Qemu versions (don’t ask me why… I tried the 4.7 one on the official website, and the maintained one on github’s Qemu repo. Forgot to mention this has been has been tested on both a clean Ubuntu and a clean Debian VM using VMWare. Yes, I am emulating an emulator. ;) Also, I'd be glad if you have any other solutions to run a Forth interpreter on a bare-metal ARM machine, either emulated or not. Thanks in advance, for your work, for your help, and for reading this. Regards, - John

4 7

Xen domU support: first steps
by Marcin Cieslak 08 Jul '16

08 Jul '16

Hello, I am experimenting with the Xen kernel a bit and I found out that having some interactive Forth to talk to it is really helpful. At the end of this email I enclose some words that I am using to talk to Xen. The file gets included in my config.fth but I have initialize it by hand by running "init-xen" first. To try the code below just setup a HVM domain with an OFW floppy image: ------------ domain cfg begin ----------------- builder = "hvm" memory = 512 vcpus = 2 name = "ofw" vnc = 1 # vnclisten = '0.0.0.0' vif = [ 'bridge=bridge0,mac=00:16:3e:76:ff:49,model=ne2k_isa' ] device_model_args = [ '-fda', 'openfirmware/cpu/x86/pc/biosload/build/floppy.img' ] vga="stdvga" videoram=16 serial = [ "tcp::4445,server,nowait" ] xen_platform_pci = 1 ------------ domain cfg end ----------------- One can use the bga video adapter with vnc. I had to comment out "create virtual-mode" since apparently any attempt to access BIOS (in the biosload setup) caused a hang there (probably unrelated to Xen/SeaBIOS). Once the basic Xen support is working we could get OFW to work as a fully paravirtualized guest. I think that OFW could also be used as a firmware to start HVM (fully emulated) domains. Currently Xen has a little stub called "hvmloader" that loads either SeaBIOS or TianoCore (UEFI firmware). Xen detection works (actually the code can be used to detect other hypervisors: HyperV, KVM and VMware), hypercalls also seem to work. I'd like to replace assembler code words with something nicer (a defining work building machine code on the fly with asm8, maybe?). XenStore initialization does work, but events are not working yet. I managed to get a simple response from XenStore in the ring buffer somehow though. XenStore is said to be inspired by OpenBoot PROM and could probably be used for nvram storage. Few questions: Should I use something thread local for "hybuf" or maybe just pad would do? How to nicely set edi in the assembler word? Which registers should not be clobbered (apparently edi is the return address)? I wasn't sure how to nicely allocate a page aligned memory. Xen provides a memory map to the guests in the BIOS E820 format (here with "xen-get-memmap"), how can I tell Openfirmware which memory areas are really available? Sorry in advance for my poor Forth skills! I'd love your comments on this code and information how to integrate it into the OFW codebase. Marcin (I also hang out as "saper" on #olpc-devel) purpose: Basic Xen support hex headers code get-cpuid eax pop cpuid eax push ebx push ecx push edx push c; h# 4000000 dup value >cpuidreg h# 1000 + value -cpuidreg : 0cpuidreg h# 40000000 dup to >cpuidreg h# 1000 + to -cpuidreg ; : +cpuidreg >cpuidreg h# 100 + dup to >cpuidreg -cpuidreg >= ; : this-xen? get-cpuid xor xor nip h# 7e7b7e7b = ; : (xen?) begin >cpuidreg this-xen? if true exit then +cpuidreg not until false ; : xen? 0cpuidreg (xen?) ; -1 value hypage 0 value /hypage d# 10 buffer: hybuf : msr/hypage >cpuidreg 2 + get-cpuid 2drop swap ( msr pages # ); : alloc-hypage 1+ pagesize * alloc-mem pagesize round-up ; : zero-hypage /hypage h# c3 fill ; : setup-hypage ( msr hypage -- ) 0 rot wrmsr ; : init-hypercalls msr/hypage dup pagesize * to /hypage alloc-hypage dup to hypage dup zero-hypage setup-hypage ; : +hypercall h# 20 * ; : >hypercall hypage 0> if +hypercall hypage + else abort" Xen support not initialized" then ; code (hypercall) eax pop eax call 1push c; code (bxhypercall) eax pop ebx pop eax call 1push c; code (cxbxhypercall) eax pop ebx pop ecx pop eax call 1push c; code (dxcxbxhypercall) eax pop ebx pop ecx pop edx pop eax call 1push c; : xen-version hybuf 1 d# 17 >hypercall (cxbxhypercall) ; : sched-op d# 29 >hypercall (cxbxhypercall) ; : xen-yield 0 0 sched-op ; : xen-block 0 1 sched-op ; : xen-shutdown hybuf ! hybuf 2 sched-op ; : xen-poweroff 0 xen-shutdown ; : xen-reboot 1 xen-shutdown ; : xen-crash 3 xen-shutdown ; : xen-get-memmap h# 1000 dup hybuf ! alloc-mem dup hybuf 4 + ! hybuf 9 d# 12 >hypercall (cxbxhypercall) ; h# 7ff0 constant domid-self : hvm-param swap hybuf 4 + ! domid-self hybuf ! hybuf swap ( arg op -- ) h# 22 >hypercall (cxbxhypercall) 0> if abort" Cannot fetch HVM parameter " then hybuf 8 + 2@ ; : hvm-param-set 0 hvm-param ; : hvm-param-get 1 hvm-param ; -1 value storebuf -1 value storeevt h# 400 constant /storebuf : init-store 1 hvm-param-get nip h# c lshift dup to storebuf 2 hvm-param-get nip to storeevt ; : >event hybuf ! hybuf d# 9 d# 32 >hypercall (cxbxhypercall) ; : >reqring [ /storebuf 1- ] literal and storebuf + ; : >rspring >reqring /storebuf + ; : storeptr storebuf [ /storebuf 2 * ] literal + ; : ringptr@ create , does> @ storeptr + @ ; : ringptr! create , does> @ storeptr + ! ; 0 dup dup ringptr@ reqcons@ ringptr! reqcons! 4 + dup dup ringptr@ reqprod@ ringptr! reqprod! 4 + dup dup ringptr@ rspcons@ ringptr! rspcons! 4 + dup ringptr@ rspprod@ ringptr! rspprod! 0 value reqptr : 0req reqprod@ to reqptr ; : req, reqptr >reqring ! reqptr 4 + to reqptr ; : reqc, reqptr >reqring c! reqptr 1+ to reqptr ; : .store cr ." reqcons=" reqcons@ . cr ." reqprod=" reqprod@ . cr ." rspcons=" rspcons@ . cr ." rspprod=" rspprod@ . ; 0 variable xid : +xid xid @ dup 1+ xid ! ; : xs-read 0req 2 req, +xid req, 0 req, word ; : init-xen xen? if init-hypercalls init-store ['] xen-poweroff is power-off ['] xen-reboot is reset-all then ;

1 0

TFTP Block Size setting?
by Alec 10 Jun '16

10 Jun '16

I am attempting to do an IBM NIM install across a 20ms latency. Is there an ability to kick off the network boot on AIX open boot with a block size option for tftp from the ok? Prompt? Forgive me if this is not an appropriate place for this. Alec

3 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

openfirmware