Processor Local Bus Functional Model Toolkit User's Manual

4.3 Invoking the Bus Functional Compiler
The bus functional compiler operates on files with the extension “.bfl”, and it generates a file with the
same name but with a “.cmd” or “.do” or “.v” extension depending on the target simulator. If the “.bfl”
extension is omitted, the “.cmd” extension is simply added to the end of the filename.
It is possible to invoke the BFC with multiple command files by specifying each file as an argument
(input parameter) to the BFC. When multiple files are used in a single BFC call, the command file
which is generated will be named using the first input file name.
To invoke the bus functional compiler, type “BFC filename1.bfl filename2.bfl...”.
Note: If the message “perl: not found” or other system error is encountered when invoking the BFC,
ensure that the path for the Perl executable is correct on the first line of the BFC source
program as required by the Perl interpreter specification. To locate the Perl executable, try
using the UNIX command “which perl.”
4.4 Initializing the Bus Functional Models
The command files which are generated by the bus functional compiler should be executed at
simulation time 0. For the VHDL toolkit this is accomplished with an “include” or “do” type command
after the model is loaded by the simulator. For the Verilog toolkit the BFC generates a Verilog
initialization command file which should be included when the simulation model is compiled.
Version 4.9.2 PLB Bus Functional Compiler 13