Datasheet

www.ti.com
Writing Scripts
This script begins with a comment which specifies that a fast I
2
C bus is used, then writes 0xAA 0x55 to
the I
2
C slave device at address 0x90. The values are written into registers 0x03 and 0x04. The script then
reads back two bytes from the same device starting at register address 0x03. Note that the slave device
value does not change. It is not necessary to set the R/ W bit for I
2
C devices in the script; this is done by
the read or write commands.
Here is an example of using an SPI device that requires 16-bit register addresses:
# setup TSC2101 for input and output
# uses SPI16 interface
# this script sets up DAC and ADC at full volume, input from onboard mic
#
# Page 2: Audio control registers
w 10 00 00 00 80 00 00 00 45 31 44 FD 40 00 31 C4
w 13 60 11 20 00 00 00 80 7F 00 C5 FE 31 40 7C 00 02 00 C4 00 00 00 23 10 FE 00 FE 00
Note that blank lines are allowed. However, be sure that the script does not end with a blank line. While
ending with a blank line does not cause the script to fail, the program executes that line, and may prevent
the user from seeing data that was written or read back on the previous command.
In this example, the first two bytes of each command are the command word to send to the TSC2101
(0x1000, 0x1360); these are followed by data to write to the device starting at the address specified in the
command word. The second line may wrap in the viewer used and appear as more than one line. Careful
examination shows that there is only one carriage return on the line, following the last 00.
Any text editor may be used to write these scripts; Jedit is an editor that is recommended for general
usage. For more information, go to: http://www.jedit.org .
Once the script is written, it can be used in the command window by running the program, and then
selecting Open Command File... from the File menu. Locate and open the script. The script is then
displayed in the command buffer. The user may also edit the script once it is in the buffer, but saving of
the command buffer is not possible at this time.
Once the script is in the command buffer, it may be executed by pressing the Execute Command Buffer
button. If breakpoints are placed in the script, the script executes to that point. The user is presented with
a dialog box containing a button to press to continue executing the script. When the user is ready to
proceed, push the button and the script will continue.
Here an example of a (partial) script with breakpoints:
# setup DAC32 for input and output
# uses I2C interface
i i2cfast
# reg 07 - codec datapath
w 30 07 8A
r 30 07 1
d 1000
# regs 15/16 - ADC volume, unmute and set to 0dB
w 30 0F 00 00
r 30 0F 2
b
This script writes the value 8A at register 7, then reads it back to verify that the write was good. A delay of
1000ms (one second) is placed after the read to pause the script operation. When the script continues, the
values 00 00 is written starting at register 0F. This output is verified by reading two bytes, and pausing the
script again, this time with a break. The script would not continue until the user allows it to by pressing OK
in the dialog box that will be displayed due to the break.
USB-MODEVM Communications Protocol34 SLAU201 – November 2006
Submit Documentation Feedback