CHIPPROG-40 Phyton Inc, CHIPPROG-40 Datasheet - Page 139

• Manufacturer Part Number: CHIPPROG-40
• Description: PROGRAMMER STANDALONE 40-DIP
• Manufacturer: Phyton Inc
• Type: Universal, Stand Aloner

Specifications of CHIPPROG-40

• Contents: Programmer, Cables, CD, Power Adapter
• Ic Product Type: Programmer, Universal
• Ic Interface Type: USB
• Features: Embedded Script Language For Automation Of Routine Operations, Splits Files To Multiple Images
• Rohs Compliant: Yes
• For Use With/related Products: EEPROM, EPROM, FLASH, MCU, NVRAM
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

© 2010 Phyton, Inc. Microsystems and Development Tools
7.2
How to create and edit script files
When you use several script files simultaneously and unload or restart some of them, remember that
script files can share global data and functions. If one script accesses data or the functions belonging to
another one that is already unloaded, then the script interpreter will issue error messages and the active
script file will be also be unloaded (terminated).
Processor text variables
The content of the text box is equivalent to the #define directive in the C language. For example, if you
type DEBUG in this text box, the result will be as if the #define DEBUG directive is placed in the first line of
the script source text.
You can specify values for variables. For example, DEBUG=3 is equivalent to #define DEBUG 3.
You can list several variables in a line and separate them with semicolons. For example:
Also, see Predefined Symbols at the Script File Compilation.
A script file is similar to a source program text written in programming language (C, for example), e.g. a
script file can be created and edited either in the
any other editor. You can allocate script files in your work directory or in the directory where the
Element of dialog
Script File Name
Browse
Defines
#include-file
Directories
Debug (open Script
Source window)
Start
Debug
DEBUG;Passes=3;Abort=No
Description
Specifies a name of the script file to be loaded. You can either typed in the
file name with a full path to the box or to take it from the drop-down history
list or browse it from a computer disc.
Opens the Load/Execute Script File dialog for locating and loading script
files into the Script File Name box.
Defines the processor text variables for compilation. For more information,
see below the
Specifies the directories in which the script file will search for the files
specified in the #include <file_name> directive(s). To specify more than
one directory, separate them by semicolons. The current directory is
scanned as well.
If this box is unchecked, a script file automatically starts execution upon the
file loading. If the box is checked, then upon loading a script file, the
program immediately opens the window for debugging the script. See also
How to Debug a Script File.
If this box is checked when you click the
the source texts of all script files visible in the Script Source windows.
Starts the script file specified in the Script File Name box.
Switches to the Debugger mode for the highlighted script file. This
command stops execution of the script and opens it in the source
window of the script for debugging. If the script is in the wait state, then
execution will immediately stop after the script returns from the Waiting
status.
Processor text
Editor window
variables.
by the ChipProgUSB built-in editor or by
ChipProgUSB
automatically saves
Script Files
139