Page 68
The configuration memory editor displays settings that
are to be programmed in a device, but are not part of any
of the above memory types.
The configuration memory editor content depends on the
selected device type. It is necessary to get acquainted
with the device's data sheet in order to get a closer
explanation of individual options in this window.
Not all devices need configuration data. This means the
editor may not be available for some devices.
Tips for Advanced Users
Even though the configuration memory may be presented
as a set of settings, in reality it is nothing more than a
memory that can be approached cell by cell. Due to this,
it is possible to display the memory in this way.
This can be achieved by activating Options ➙ Program
settings ➙ Editors ➙ Configuration memory editor:
show cfg word instead of fuses option or by double-
clicking the configuration memory window.
The device's ID positions (do not mistake for Device ID)
can also be found in the configuration memory window. ID
positions can be programmed with values identifying the
device, such as the serial number, for example. ID
positions can always be read - even if the device is locked
against reading.
According to the recommendation of the Microchip, ID
positions should not be programmed with any value; only
a certain number of bits (typically 4) should carry data for
identification while other bits should be programmed with
the default value.
This can be achieved by activating Options ➙ Program
settings ➙ Editors ➙ Mask ID positions....
5.6
Running UP from
Command Line
The UP program can alternatively be controlled from the
command line.
The program itself makes sure that it always runs in one
instance only (with one class name). Should a second
instance (with the same class name) be started,
parameters from the command line are transferred to the
first instance for execution. Only the /p, /pdiff, /blank, /
verify, /erase, /read, /noe, /eeonly, /noboot, /boot, /code, /
cfg parameters are transfered to the running instance. UP
can be started in more instances using different class
name, see /wnd in List of Parameters.
5.6.1 List of Parameters
UP.EXE [{/ask | /q | /q1}]
[{/e File_with_eepromm.hex | [/noe]}] [{/p |[/pdiff]| [/
o]} File.hex | File.ppr] [/df File.hex] [/part
device_name] [/eeonly] [/erase][/w[nd]
up_window_class] [/cfg] [/devid] [/blank] [/verify File]
[/read File] [/s SN_programmer's][/progname name] [/
noboot] [/boot] [/code] [/getpartrev] [/sn
serial_number] [/conf file]
Legend
• Text presented here in bold is to be keyed in in the
command line exactly as printed here.
• Text presented here in italics is to be replaced by the
corresponding parameter. For example, file_name
should be replaced with the real name of a file to be
opened.
• Text in braces {} separated by the | sign represents a
selection of one of the presented options. For example,
{ A | B } means “choose either A or B”.
• Text in square brackets [] presents an optional
parameter – it can be keyed in but does not have to.
To Next Page
Loading...