Options
|
Description
|
-GANG[:<number of sockets> | #<list of serial numbers>]
|
This option launches the ChipProgUSB in the multi-programming (gang) mode. In this mode the ChipProgUSB software drive multiple programmers, i.e. either a ChipProg-G4 or ChipProg-G41 gang programmer or multiple single-site ChipProg programmers connected to one computer. You must use this key to control the ChipProg-G4 or ChipProg-G41 gang programmers. The -N, -P and -R keys below may not be included in the same command line with the -GANG key.
|
|
The /GANG key can be supplemented by a parameter :<number of sockets> that specifies a number of programming modules in the controlled gang machine or a programming cluster. For example, the /GANG:2 key says that USB communication will be established only with two first programming modules in the gang machine. This allows to expedite establishing USB communication with the gang programmer. If the ChipProgUSB has been launched with the -GANG key the program waits up to 16 sec or until all multiple of 4 device programmers were detected, whichever happens earlier. For example, the -GANG:2 key stops establishing USB communication when first two programming modules were detected.
If the /GANG key is followed by the '#' sign and a list of serial numbers separated with semicolon, the programmer application waits for the connection of the number of the single-site programmer devices that match the number of serial numbers in the list, and automatically assigns the sequence numbers according to the serial number positions in the list. For example, if the /GANG#PHP00014;PHP00020 is specified, the application waits for two programmers with serial numbers PHP00014 and PHP00020 to be connected, the programmer with serial number PHP00014 will be assigned the sequence number 1 and programmer with serial number PHP00020 will be assigned the sequence number 2.
|
-C"<manufacturer^device>"
|
This option opens the ChipProgUSB program with a device specified as a combination of the device manufacturer and device part number separated by the ^ character. The device specified in a previously loaded project will be replaced by a device specified by the -C"<manufacturer^device>" key. For example: /C"Atmel^AT89C51".
|
-L<file name>
|
This option loads the <file name> file into the ChipProg buffer immediately after launching the ChipProgUSB program. If other files were previously loaded with some project then a new one will be loaded in accordance with the file format and start address. The loader automatically recognizes the file format in accordance with the file extension. If an actual file format differs from one listed in the file format list, use the option -F; this option enables you to explicitly specify the file format (see below).
|
-F<file format>
|
This key explicitly sets the format of the file specified by the option -L<file name> above. The <file format> is specified by one of the following letters:
H - standard or extended Intel HEX format
B - binary format
M - Motorola S record format
P - POF (Portable Object Format)
J - JEDEC format
G - PRG format
O - Holtek OTP format
V - Angsrem SAV format
For example: the option -FH loads a file in the HEX format, which defines the start destination address in the ChipProg buffer.
If the binary format (B) is specified by the option -F then it may be accomplished by a hexadecimal value that specifies the destination start address of the file to be loaded. For example: the option /FBFF04 loads a binary file and places the data at the address FF04h in the buffer.
If a command line includes a key -F<file format> but does not include a key -L<file name>; i.e., it specifies the file format but does not specify the file name itself, the -F<file format> option will be ignored.
|
|
Note that use of the -C, -L, -F command line keys is less beneficial than use of projects, which allows much more flexible and effective control of device programming. It is highly recommended, and especially for mass production, to open, configure and store as many projects as you need and launch them from a command line. .
|
-A[buffer number]
|
This option initiates the Auto Programming session in accordance with other command line options immediately after launching the ChipProgUSB application. It closes this application in case of successful completion. In case of error the ChipProgUSB application remains suspended until it is closed manually. If the [buffer number] is omitted then the data for Auto Programming are taken from buffer #0; otherwise from the buffer number that follows the -A. For example: the option -A2 specifies that data for the Auto Programming session will be taken from the buffer number 2..
It makes sense to use the -A option only when including in the command line a project name or the -L<file name> option.
|
-I
|
This key makes the ChipProgUSB application main window invisible until a programming error occurs. In case of error the window appears on the PC screen along with the error message. Use of this option makes sense only if the option -A (Auto Programming) is included in the same command line. Otherwise the -I option will be ignored.
|
-I1
|
This key is similar to the -I key but use of the -I1 holds the ChipProgUSB application main window invisible even if a programming error occurs. The first occurrence of a programming error returns the error code 1 and closes the ChipProgUSB program. (A successful Auto Programming session ends with returning the code 0). These return codes can be conveniently used by an external application that controls the ChipProg remotely; for example, LabVIEW, similar programs or batch files.
|
-I2
|
This key is similar to the -I key, but use of -I2 holds the ChipProgUSB application main window invisible, suppresses displaying error messages, but copies them to the Windows clipboard.
|
-M
|
Including this key in the command line launches the ChipProgUSB software in the demo mode, which does not require use of the ChipProg hardware and real data exchange between a computer and the programmer hardware. Use of this mode is convenient for product evaluation without the ChipProg hardware.
|
|
Important! The three keys below - -N<serial number>, -P<identifier> and -R - allow control of one single-site programming module, either from a cluster of similar multiple programmers or inside a gang device programmer, but only when the programmers are not driven in the gang mode. These three keys may not be used with a combination of the key -GANG.
Use of these keys may be convenient when, for example, it is necessary to program two different files into two different device types on two pairs of programming sites of the Phyton gang machine. In this case each pair of programming modules specified by the -R or -P keys can perform two different programming jobs simultaneously.
|
-N<serial number>
|
This key enables operations with a particular single-site ChipProg programmer from a cluster of multiple programmers driven from one PC but only when these programmers are not controlled in the gang mode (with the key -GANG). Each single programmer has its own unique serial number (<serial number>) enabling you to address it by this serial number. A serial number can be found on the bottom of the programmer case or, better, by opening the menu Help > About... . Serial numbers of all single programmers connected to one PC are also available in the "Choose programmer" dialog that the ChipProgUSB program opens if the command line does not include the options -N or -P. For example, the option -NPHP10012A apecifies that all other command line options are applicable to the programmer with a serial number PHP10012A only.
|
-P<identifier>
|
This key is similar to the -N above but it defines a single module in the gang machine or in a programming cluster by setting the site number following a reserved text identifier "Phyton Gang Programmer" for the programmers driven by the ChipProgUSB software and "Phyton Fast Gang Programmer" for the programmers driven by ChipProgUSB-01. For example, the option -P"Phyton Gang Programmer #2" defines that all other command line options are applicable exclusively to the programming module #2.
|
-R
|
This key is applicable only for operations with Phyton gang programmers (ChipProg-G41 and ChipProg-G4) but only when it is necessary to operate with a particular programming module inside of these gang machines; i.e., not in the gang mode. Since all single programming modules belonging to each ChipProg gang programmer have the same serial number it is impossible to address the programming site by a serial number (key -N). When one of the mentioned gang programmers is launched from the command line, including the -R option, this opens the dialog prompting a user to specify a particular number of the programming module inside of the gang machine. It is possible to use the key -P for choosing a programming module with a specified socket number.
|
-S<file>
|
This key replaces a default session configuration file UPROG.ses by a new one with the name <file> and the extension .ses. The session configuration file stores major ChipProg settings, and includes a name of the last working project; it resides in the ChipProgUSB folder. The new session settings will be used by the ChipProgUSB right after the command line execution.
|
-O<file>
|
This key replaces a default option configuration file UPROG.opt by a new one with the name <file> and the extension .opt. The option configuration file stores the target device type, file options, etc.; it resides in the ChipProgUSB folder. The new options will be used by the ChipProgUSB right after the command line execution.
|
-D<file>
|
This key replaces a default desktop configuration file UPROG.dsk by a new one with the name <file> and the extension .dsk. The desktop configuration file stores the computer screen configuration, i.e., positions, dimensions, colors and fonts of all opened windows; it resides in the ChipProgUSB folder. The new ChipProgUSB desktop configuration will be in force right after the command line execution.
|
-ES<file>
|
This key executes a script file, whose name follows the key -ES, right after launching the ChipProgUSB application. If the command line does not include the -ES key, the ChipProgUSB application searches for the script file named ‘Start.cmd’ in the programmers’s working folder and, if such a script file exists, it executes this script.
|