Line 435... |
Line 435... |
Specify simulator to use. Default is Icarus Verilog, can be set to @code{modelsim} to use Mentor Graphics' Modelsim. No others are supported right now.
|
Specify simulator to use. Default is Icarus Verilog, can be set to @code{modelsim} to use Mentor Graphics' Modelsim. No others are supported right now.
|
|
|
@item MGC_NO_VOPT
|
@item MGC_NO_VOPT
|
When using Modelsim (specifying @code{SIMULATOR=modelsim}), if the version does not include the individual @code{vopt} executable, specify @code{MGC_NO_VOPT=1} when compiling.
|
When using Modelsim (specifying @code{SIMULATOR=modelsim}), if the version does not include the individual @code{vopt} executable, specify @code{MGC_NO_VOPT=1} when compiling.
|
|
|
|
@item VPI
|
|
Pass @code{VPI=1} to have the an external JTAG debug module stall the processor just after bootup, and then provide a GDB stub (interacting with the Verilog sim via the VPI) to allow control of the system in a similar fashtion to that of a physical target controlled over JTAG via a debug proxy application. The port for GDB is hardcoded to 50002. See the code in @code{bench/verilog/vpi/c} for more details.
|
|
If running with Modelsim, ensure the path @code{MGC_PATH} is set and points to a directory containing a path named @code{modeltech}, which should be the Modelsim install.
|
|
|
@end table
|
@end table
|
|
|
|
|
|
|
|
|
Line 1362... |
Line 1366... |
|
|
@c ****************************************************************************
|
@c ****************************************************************************
|
@c Generic Design build chapter
|
@c Generic Design build chapter
|
@c ****************************************************************************
|
@c ****************************************************************************
|
|
|
@node Generic
|
@node Generic Designs
|
@chapter Generic
|
@chapter Generic Designs
|
@cindex Generic design information
|
@cindex Generic design information
|
|
|
@menu
|
@menu
|
* Overview::
|
* Overview::
|
@end menu
|
@end menu
|
Line 1376... |
Line 1380... |
@node Generic Build Overview
|
@node Generic Build Overview
|
@section Overview
|
@section Overview
|
|
|
The paths under @code{boards/generic} contain designs similar to the reference design, in that they are not technology specific, and used for development of certain features of the processor, or peripherals.
|
The paths under @code{boards/generic} contain designs similar to the reference design, in that they are not technology specific, and used for development of certain features of the processor, or peripherals.
|
|
|
An example is the fault tolerance testing build, in @code{boards/generic/ft}, which implements some custom modules in the testbench and ORPSoC top level design, and is in general a very minimal system just for testing.
|
These builds are a TODO, but should provide technology-independent builds, with any specialist modules required to debug, or assist in development or demonstration of a module.
|
|
|
Additional builds, testing certain parts of the technology, can be developed here.
|
|
|
|
@c ****************************************************************************
|
@c ****************************************************************************
|
@c Software section
|
@c Software section
|
@c ****************************************************************************
|
@c ****************************************************************************
|
|
|