1. Macronix_MX987xx.zip Driver
2. INTRO.TXT File Contents

INTRO.TXT Driver File Contents (Macronix_MX987xx.zip)

------------------------------------------------------------------------
             Introduction to the DMI Component Test System
------------------------------------------------------------------------

DCTS2 is a tool created to aid developers of DMI v2.x Service Providers
and instrumentation in the testing and validation of their products.
It allows you to connect to one or more Service Providers (SPs), on
different systems.  Once you are connected to an SP, you can browse and
modify the contents of the SP's component database, or submit a sequence
of DMI commands to the SP and view the results (status and returned
data) of those commands.


[Internal Database]
For each system that DCTS2 is connected to, it maintains a component
database similar to the one that is managed by the SP.  This database is
used internally by DCTS2 to assist you in creating the list of commands
to send to the SP (this list is called a Test Execution List, or TEL).
The internal database contains the same information that is in the SP's
database, plus some information that is not available from the SP.


[System Connections]
A system connection is an RPC link to an SP, either on a remote system
or the local system (the one that DCTS2 is running on).  The LOCAL RPC
is also supported.

To make a remote connection, select Database|New_Connection, and a New
Connection dialog box will appear.  Enter the name of the system you
want to connect to (or its IP address) in the System Name box, and then
select the RPC and Transport types from the corresponding listboxes.
If you enter a directory path in the "Use MIF and Expectation files 
from" box (this is optional), DCTS2 will attempt to install any MIF 
files that are found in that directory into the internal database,
automatically, after the RPC connection is established.

To make a LOCAL connection, select "Local" from the RPC list and "DMI"
from the Transport list.  Enter any name you prefer in the System Name
box (for a local connection, this name is not used, but it serves to
identify the connection in various lists and menus within DCTS2).

In either case, when you click the OK button, DCTS2 will try to create
an RPC link to the specified system.  If successful, it will then load
the MIF files and created the internal database for the new connection
(if you specified a directory path in the New Connection dialog).

DCTS2 keeps a list of all current system connections.  This list appears
in various places as you use DCTS2.  When you exit the program, the
current list of connections is saved, and DCTS2 will attempt to restore
each of those connections the next time you start it up (there is a
checkbox in the Preferences dialog that controls this action - if you
clear the checkbox, DCTS2 will not save or attempt to restore the list
of connections).  You can save your list of connections at any time, or
restore a previous connection list, by using commands in the Database
menu.  If you restore a previous connection list, any connections you 
have currently established will be broken first.  You can also break
any current connection with the Database|Disconnect_System menu command.


[Browsing]
You browse the contents of either an SP or internal database by opening
a browser window of the corresponding type.  Do this via the Service_-
Provider_Database or DCTS_Internal_Database commands from the Database
menu.

When the browser window is opened, it is not associated with any system.
To attach the browser to a system, activate the browser window and then
select the system you want to attach it to via the Database|Connections
popup menu.  This popup menu is also available in the browser window's
system (control) menu.  This menu also includes a "New" command, so you
can create a new system connection.

The browser window is split into two panes, left and right.  The left
pane contains a tree-style view of the DMI components in the associated
database.  When the browser is first attached to a system, you'll see a
list of the DMI components.  Each node in this list will expand to show
the groups that make up that component.  Each node in a component's
group list will expand to show the group's attributes.  The right pane
of the window is divided into Component, Group, and Attribute sections.
When you select (highlight) a component, group, or attribute in the left
pane, the details of the item will be shown in the right pane.

The Attribute section of the right pane includes buttons to let you walk
the rows of a table.  If a selected attribute has an Access specifier of
Read-Write or Write-Only, the "Set" button in the Attribute section is
enabled.  If you enter a new value in the "Value" field and click the 
"Set" button, the attribute value will be changed to the new setting.
If you set an attribute value in the DMI (SP) database, the new value
will be reflected into the internal database, but not vice versa.

Components can be added to or deleted from either the SP or internal 
database, or both, via the Install or Uninstall commands in the Database
menu.


[Event Indications]
When you establish a system connection, DCTS2 registers with the SP on
that system, and subscribes for all Indication types, including both the
Component Added and Component Deleted indications.  When DCTS2 receives 
one of these indications from any SP it is connected to, it automatically 
updates any DMI database browser windows that are attached to that SP.  
Currently, DCTS2 does not update its browser windows when it receives 
Group or Language Added/Deleted indications; that support is planned 
for a future release.


[Test Sessions]
Although the browser is a useful feature, and can indeed be valuable in
testing an SP or instrumentation, it is still basically a feature.  The
major vehicle for testing SP and instrumentation is the test session, 
and its associated Test Execution List (TEL).  A TEL is a sequence of
one or more DMI commands that you build, one at a time, using a special
dialog box.  The TEL is then submitted to the SP to be executed.  The
test session includes the TEL plus a handful of parameters, set via the
Preferences dialog, that control execution of the TEL.

A DCTS2 test session is somewhat analagous to a word processor document.
You create, save, open, and close sessions from the File menu, just like
the word processor.  However, DCTS2 allows only one session to be open 
at a time.  The session is independent of any browser window(s) that may
be open, however the session and the browser windows both use the same 
list of system connections.

[Creating a Test Execution List]
Selecting Tests|Build_A_New_Test_List brings up the TEL builder dialog
box.  This dialog allows you to construct a list of DMI commands that
will later be submitted to the SP to be executed.  The list may contain
as many commands as you like.  The commands are built one by one, and
added to the list as they are built.

Each command has a system name associated with it.  This is the system
whose SP will receive the command when the TEL is submitted.  You can
mix and match different target systems within a TEL if you desire.  The
first step in constructing a command is to select the system you want
the command to go to, from a listbox that shows all your current system
connections.

After the system is selected, you go on to select the command that you
want to send, followed by the various argument values that go with the
command.  You are prompted for the appropriate selection at each step
in the command building sequence.  Most selections are made from a list
box, except for those that require a text entry, for example, a filename
is required for an AddComponent command.  The "Add Comp", "Add Attr", 
and "Add Lang" buttons are used to select multiple targets or files for
the GetMultiple, SetMultiple, AddLanguage, AddComponent, and AddGroup
commands.

The "Command Modifiers" block allows you to set a few items that are
specific to certain commands; these items are enabled only at the final
step in the command specification sequence.  "Get Description" and "Get
Pragma" apply to the DmiList* commands, as does the "Max Count" editbox.
"Set Mode" is for SetAttribute and SetMultiple commands.  "Iteration
Count" applies to all commands; you can specify how many times you want
each individual command in the TEL to be sent to the SP (a separate
iteration count, set when the TEL is submitted, applies to the entire
TEL).

When you finished with a command, click on the "Done" button to commit
the command to the TEL.  When you have specified all the commands you 
want, click on the "OK" button to exit the dialog.  After exiting the 
TEL builder, the left pane of the TEL Manager window will contain a list
of the commands in the TEL.  If you highlight a command from the list,
that command's arguments will be detailed in the right pane.

The TEL construction dialog will prevent you from building a command
that is improperly formatted or illegal.  This is enforced by including,
in the list box, only those options that are valid in the context of
all previously made selection.  For example, if the target system you've
selected doesn't have any components (except the SP component) in its
database, the command selection list that you have to pick form will not
include DeleteComponent.  Or, if you're building a SetAttribute command,
read-only attributes (or components/groups that contain only read-only
attributes) will not be included in the selection list.

If you want to examine how your SP or instrumentation handles an invalid
command, you can use the "Error" checkbox in the Command Modifiers.
This checkbox is enabled at the final step in the sequence.  If you set
it, a list of error codes (specified by the DMI spec for the command you
are building) will be provided in the selection listbox.  If you select
one of these error codes, the command will be "adjusted" when it is
submitted to the SP, in a manner that should cause the SP to fail and
return the selected error code.

[Executing a test list]
Submitting a TEL for execution is done from the Tests menu, but before
doing so, look at the Preferences dialog (Options|Preferences).  This
dialog allows you to control if and how the test result data is logged
to disk or displayed.  If you select "Log test results to file", you'll
be prompted for a filename when you submit the TEL.  If you select "Log
test results to window", a Test Monitor window will be opened when you
submit the TEL.

The results log, whether in the Test Monitor window or written directly
to disk, lists all of the input parameters that were given to the SP
for each command, and the data and status code that the SP returned.