Nick Couchman wrote:
Hmmm...not really working for me. I don't know that I'm actually at the "ok" prompt - I see the word "ok" output to the screen, but the prompt is actually "0> " and not okay. When I try "see do-boot", I get "do-boot: undefined word." Furthermore, almost none of the other commands work, either - get-bootdev, load-pkg, etc., all return "undefined word."
Just to make sure I didn't leave anything out before, I'm running qemu-system-sparc64 (from the Qemu git repo), using OpenBIOS built from the svn repository. If there's something else I should be trying, please let me know.
Thanks, Nick
Hi Nick,
By default the OpenBIOS fcode evaluator creates headerless words, and so they won't appear in any wordlists which are visible to the system.
In order to make the words visible, you need to open up forth/admin/nvram.fs and change the value of fcode-debug? from false to true in the NVRAM variables section. If you then rebuild OpenBIOS, the words generated by the Fcode evaluator will then show up in the relevant package when you type "words".
Incidentally, I see that Blue Swirl has also committed the Forth source debugger over the weekend, so you should be able to do "debug do-boot" followed by "do-boot" and then step through the process to see where it fails.
HTH,
Mark.