Cirrus Logic CS49300, Reference Design, Page: 14 / 51

14
APPENDIX C: BOARD CONTROL SOFTWARE
There is a suite of programs used to control the
UDSP from a PC DOS command line.
These software tools are designed to so that they
can be scripted using the MS-DOS batch language.
They will work with any of the 3 standard parallel
port addresses (0x378, 0x3bc, 0x278). The default
address for all of the programs is 0x378 (typically
LPT1). The port address can be changed by using
the '-p' option. Each time a program is executed, the
address that was used can be shown on the screen
using the ‘-v’ option. If a program seems to fail,
v e rific atio n o f th e p a ra lle l p o rt ad d ress sh o u ld
alw a y s b e th e first ste p in tro u b le sh o o tin g .
All of these programs are designed to access the
daughter card connected to the UDSP board using
SPI or I
2
C
®
serial communication. The
communication mode can be chosen from the
command line with the '-m' option. The mode
chosen must correspond to the communication
mode used by the devices on the daughter card. If
the device on the board is set up for one
communication mode, and the drivers are used with
another, results will be unpredictable. All devices
on the daughter card are configured for SPI serial
communication mode by default, and that is also
the default mode for the software.
The usage of each program will vary, depending on
the type of UDSP daughter card that is installed.
The URST, URD, and UCMD programs get a valid
list of devices for the installed daughter card from
the file specified by the “uINI_path” DOS
environment variable. This file will list all of the
devices available to the UDSP parallel port drivers,
along with each device’s I
2
C address, SPI address,
chip select number, and reset number (for reset
capable devices). It also specifies how messages
from the device should be read. For DSP-style
reads, the driver will read until the INTREQ line
goes high. For non-DSP devices, the read operation
will read out 1 byte. Please note that most non-DSP
devices require an aborted write operation to
properly set the MAP pointer before reading.
The device list file, called CRD42528.INI, must
follow a very specific format. An example of this
can be found
“CRD42528.INI” on page 13 . This
file should not be changed.
A list of available drivers and their usage is found
below:
UCMD.exe - Send commands or configuration files to a target device.
Usage: ucmd <[ABCDEF..] or [-fX]> [-dZZZZ..] [-mY] [-pWWW] [-v]
-d = device
ZZZZ.. = device designator, eg dspab, dspc, 8415a, etc.
-m = communication mode
Y = mode designator (i=I2C, s=SPI*, m=MOT, n=INT)
ABCDEF.. = hex data (1-100 bytes)
-f = send configuration file
X = .cfg file containing configuration parameters
-p = parallel port address
WWW = address in hex (278, 378* or 3bc)
-v = enable verbose mode
* = default value
Example: ucmd 000001 -d4341 -p3bc
Notes: A configuration file is a list of commands, contained in an ASCII text file. This file
can be any length, and should list the commands in hex, with an even number of characters per
line. Comments can be made in the file by putting a # at the beginning of the line. The entire
line will be interpreted as a comment. Please see the accompanying *.cfg files for examples of
a configuration file.