ASIX Forte - Page 70

Page 70
/devid If this parameter is used in combination
with parameter /p, the software only
checks the device's Device ID.
/blank This checks device erasure (blank check)
and returns an error code if the result is not
OK.
/verify file This verifies the device.
/read file This reads the device and saves the read
content to the file.
/s programmer_SN This makes it possible to
select a programmer by its serial number.
The serial number is to be keyed in the way
it is displayed in the UP program and
printed on the programmer bottom.
Example: 016709 or A6016709. When *
sign is used instead of the serial number,
then any available programmer of the
selected type is used.
/progname name This makes it possible to
select a programmer by its name such as
PRESTO or FORTE for example.
/noboot This skips programming of the MSP430 boot
memory.
/boot This performs the selected operation only
with the MSP430 boot memory.
Note
PIC32 microcontrollers also have a boot
memory. This, however, uses variables and
a data memory form for programming, so it
works with parameters for a data memory
and not with parameters for a boot
memory. A similar situation can be found in
the information memory of MSP430 and
CC430 microcontrollers.
/code This performs the selected operation only
with code or main memory.
/getpartrev Only reads the revision of the device
and returns revision + 0x10000 as the error
code.
/sn serial_number Using this parameter it is possible to
enter the value of the serial number, which
is then written to the address in accordance
with the serial numbers settings. In the
settings, the serial numbers have to be
configured as Computed, Manual. The
number is entered as hexadecimal, e.g.
1234ABCD.
/conf file When UP closes, it saves its console
content to the file, but only when the
operation was started from the
commandline.
Note: When no parameter requesting an operation is
used, the UP starts and keeps running. When a parameter
requesting an operation is used and the software is not
running, the operation is executed and the software
closes if it does not need user interaction.
Using a Project File
If you work on more than one project, it can happen that
the program is set up for a different device (or even a
different programmer if you have more) than what you
expected. To avoid such situations, it is recommended to
use project files (.PPR) that hold all the program settings
needed for programming and paths to the work files.
Examples of Use
The installation directory of the UP software contains the
“read_avr_eeprom.bat“ and “set_idle_power_1.bat“
sample batch files showing the use of command line
parameters.