What is the OpenBIOS FCODE Suite?
OpenBIOS provides a sophisticated set of FCODE utilities:
- the tokenizer toke
- the detokenizer detok
- and a PCI rom header utility.
- a portable implementation of forth local values
These files are offered without any warranty. If you experience problems, please contact the OpenBIOS mailinglist.
Downloading the OpenBIOS FCode Suite
The latest version of the OpenBIOS FCode Suite is 1.0.2 (released 2006-10-30)
There are three documents, all in html format, plus a sub-directory of templates that provide common formatting support.
It is important that these be kept in the same directory, as there are some links from one file to another.
The documents are User's Guides to:
- the New Features of the Tokenizer,
- the Detokenizer, and
- the Local Values feature, which is mentioned briefly in the Tokenizer User's Guide and described fully in the Local Values document.
These documents are also part of the source code repository.
There is also doxygen generated documentation available
- doxygen documentation for toke 0.6.10
- doxygen documentation for toke 1.0.0
- TODO: doxygen documentation for toke 1.0.2
Executables for three platforms
While you can find a couple of executables here we strongly recommend that you compile the FCode toolchain from the sources above so you gain from the integration work and fixes that have been done since these executables have been created.
There are three programs: the Tokenizer, the Detokenizer and the ROMHeaders utility. (Binaries)
There is a version for each of three platforms (i.e., combinations of Processor and O/S): Cygwin running on an X86, GNU Linux running on a Power-PC, and AIX running on a Power-PC.
There are two variants of each version: One that has level-2 Optimization and one that has no optimization at all, which I provided for purposes of Debugging. Optimization causes some routines and variables to become obscured and inaccessible to debuggers, and also re-arranges the sequence of execution in a way that can become confusing during single-stepping.
And finally, for each, there is a "stripped" and an "unstripped" executable image. The "unstripped" image has an extension of "unstripped"; the "stripped" image has no extension.
There are separate directories for the Debug and Optim(ized Level)2 variants.
Under each are sub-directories for the different platforms, within which the executable images reside.
All binaries are also available in a single Tar-File: Binaries.tar.bz2
Local Value Support
Includ-able tokenizer-source files for Local Values Support (explained in one of the User's Guide documents). Five files:
- One supplies the basic functionality
- the second adds a development-time facility
- the third generates a variant behavior ("Global" scope rather than scope limited to a single Device-Node)
- and the fourth combines the "Global" variant behavior with the development-time facility.
- The fifth allows the choice of combinations to be governed by command-line switches, and is probably the best to use with Makefiles in commercial development and production environments.
There is commentation in each one explaining how it is to be used.
Available as part of the OpenBIOS FCODE suite.
A list of "Still To Be Done" items, excerpted from the commentation in the Sources
The source files have, scattered among their commentation, an occasional item discussing a feature or implementation detail that might be worth attention in future revisions.
This file is a collection of all of them in a single convenient location.
The suite of unit-test cases
This is the accumulation of test-cases that were created in the course of development. Some of these are a straightforward invocation of a feature, others are convoluted combinations of features whose interaction needed to be carefully watched, and still others are collections of coding errors, for purposes of verifying the Error-detection capabilities of the Tokenizer. They are grouped into sub-directories representing broad categories.
Run the unit-test cases with
$ make tests
The tools to run the Unit-Test Suite as a batch and examine the results for changes relative to the results from a previous run.
The process of manually running a unit-test and comparing against the previous output, after every change, became unwieldy, especially when it came to running the entire suite of tests. These scripts were developed to automate both processes:
There is commentation in each explaining how it is used.
Unit-Test Suite Logs
These can be used as base-lines for comparison against future versions, or, if so be, versions compiled for additional platforms.
Note that a comparison of these against each other will not yield exact identity. Some of the test-cases, for instance, code the current date and time, others display a complete file-path, and still one other attempts to load a file for encoding using a syntax that is erroneous on some O/S's but not on others.
All in all, five or six file differences will be expected to be reported by AutoCompare.
- The results from a run of the Unit-Test Suite on the X86/Cygwin platform.
- The results from a run of the Unit-Test Suite on the PowerPC/Linux platform.
- The results from a run of the Unit-Test Suite on the PowerPC/AIX platform.
The test suite has been run using gcov/lcov to produce graphical code coverage reports.
Kudos and Thanks