
Embedded System Tools Guide (EDK 6.2i) www.xilinx.com 299
UG111 (v1.4) January 30, 2004 1-800-255-7778
Example
R
MDD file example
An example MDD file for the uartlite driver is given below:
OPTION psf_version = 2.1;
OPTION is a keyword identified by the li/jointfilesconvert/328590/bgen tool. The option name following the
OPTION keyword is a directive to the li/jointfilesconvert/328590/bgen tool to do a specific action. Here psf_version
of the MDD file is defined to be 2.1. This is the only option that can occur before a BEGIN
DRIVER construct now.
BEGIN DRIVER uartlite
The BEGIN DRIVER construct defines the start of a driver named “uartlite”.
PARAM NAME = level, DESC = "Driver Level", TYPE = int, DEFAULT = 0,
RANGE = (0, 1);
PARAM defines a driver parameter that can be configured. Each PARAM has the following
properties associated with it whose meaning is self-explanatory - NAME, DESC, TYPE,
DEFAULT, RANGE.
BEGIN BLOCK, DEP = (level = 0)
BEGIN BLOCK, dep allows conditional inclusion of a set of parameters subject to a
condition fulfillmen. The condition is given by the DEP construct. Here the set of
parameters defined inside the BLOCK would be processed by li/jointfilesconvert/328590/bgen tool only when
“level” parameter has a value 0.
OPTION DEPENDS = (common_v1_00_a);
OPTION COPYFILES = (xuartlite_l.c xuartlite_l.h Makefile);
OPTION DRC = uartlite_drc;
The DEPENDS option specifies that the driver depends on the sources of a directory
named “common_v1_00_a”. The area for searching the dependent directory is decided by
the li/jointfilesconvert/328590/bgen tool. COPYFILES option indicates the files to be copied for a “level” 0 uartlite
driver. DRC option specifies the name of the Tcl procedure that the tool invokes while
processing this driver. Here “uartlite_drc” is the Tcl procedure in the uartlite_v2_1_0.tcl file
that would be invoked by li/jointfilesconvert/328590/bgen while processing the uartlite driver.
BEGIN INTERFACE stdin
BEGIN INTERFACE defines an interface the driver supports. Here “stdin” is the name of
the interface.
PROPERTY header = xuartlite_l.h;
FUNCTION name = inbyte, value = XUartLite_RecvByte;
END INTERFACE
An Interface contains a list of standard functions. A driver defining an interface should
have values for the list of standard functions. It must also specify a header file where all the
function prototypes are defined.
PROPERTY defines the properties associated with the construct defined in the BEGIN
construct. Here “header” is a property with value “xuartlite_l.h”, defined by the “stdin”
interface. FUNCTION defines a function supported by the interface. Here “inbyte”
Comments to this Manuals