presto_en.pdf - 第53页
Page 53 ▸ Read ID posi tions not from the fil e but from the device If you want to p reserve th e content of the ID positions, use the Read ID positions not from the file but from the device opt ion. The p rogram fills i…
Page 52
▸ Warn when loaded HEX does not
contain CFG memory data
If the file does not contain configuration memory data
and the data are expected for the chosen device, a
warning message is displayed.
▸ Warn when loaded HEX is not aligned
to word size.
If the file is not aligned to the word size of the memory of
the device, a warning message is displayed.
▸ Binary file loading and saving style
This panel provides for the setting of how .bin files are to
be loaded and saved if a device with more than one byte
per word is selected.
Available options are: the program always asks before
loading or saving a .bin file (Ask if to load/save .bin as
Big or Little Endian), or without asking, the program
always loads files as Little Endian (Never ask, load/save
as Little Endian) or as Big Endian (Never ask, load/
save as Big Endian).
▸ Save unused locations to .hex file
If not all positions are saved, the final file is smaller, but it
can cause difficulties as a cell is considered an “empty
position” if it contains only ones (e.i. FFFh, 3FFFh, etc.).
Yet this could be a meaningful instruction (3FFFh is
Microchip PIC addlw -1 instruction, for example).
As UP always saves files by larger blocks, (by eight or
sixteen bytes), the danger of losing an instruction by such
saving is rather small in reality.
If you use memory initialization prior to loading a .hex file
(which is recommended), even a program loaded from a
reduced .hex file will be correctly programmed as the
missing instructions are created “automatically”.
▸ Clear code/main / data memory / ID
positions before file reading
This location is filled with ones and only then a file is
loaded. This way all positions that are not saved in the
.hex file get erased.
This option is also important if no “empty” locations are
saved in the .hex file (see
▸ Save unused locations to .hex
file
).
▸ Erase configuration memory before file
reading
With this option activated, the configuration memory is
initialized before a file for code/main memory is loaded.
If no fuses are saved in the file, it is recommended to
deactivate this option. At the beginning of the work, the
user can set the content of the configuration memory and
then the fuses do not have to be set again if the file is
repeatedly loaded.
▸ Read data memory not from the file but
from the device
If you want to make sure that the content of the data
memory does not get overwritten, use the
▸ Program all
except data memory
option. If, however the ▸ Program all
option is selected by accident (by unintended pressing of
the GO button, for example), the content of the data
memory would be erased.
For such cases, this option of Read data memory not
from the file but from the device is available. The
program fills in the given location with the memory
content of the device connected to the programmer.
Advice
This option could cause unexpected actions during work
with the programmer such as switching the application on
or starting the UP program.
Page 53
▸ Read ID positions not from the file but
from the device
If you want to preserve the content of the ID positions,
use the Read ID positions not from the file but from
the device option. The program fills in the given location
with the memory content of the device connected to the
programmer before starting the programming itself.
Advice
This option could cause unexpected actions during work
with the programmer such as switching the application on
or starting the UP program.
▸ Save fuses in UP instead of data file
This option allows to save fuses in ini file or UP projekt file
even for devices which by default have their fuses saved
in a data file.
▸ Project storing style
This panel allows you to set how projects should be saved
when exiting UP. Available options are: save
automatically, ask before saving or keep the original file
(i.e. do not save).
▸ Load last project on start-up
This option allows you to set if on the next UP start it will
open the project file, which was open on program
closing.
Options ➙ Program settings ➙
Colors
Keyboard shortcut: Shift+F10
This is where you can change and save colors of HEX
editors so that they suit your needs and your aesthetic
preferences.
A front color, a background color and a font can be
selected for all the listed text segments.
Options ➙ Program settings ➙
Editors
Keyboard shortcut: Shift+F10
▸ Code/main memory editor: show words
as bytes
Individual words can be displayed by bytes in case of
devices with 16-bit-long words.
▸ Code/main memory editor 8 words
wide
This option narrows the editor from the original sixteen
cells down to eight. The option is suitable especially for
small monitors. It can change automatically when a
different device type is selected.
The same option can be set for others memories:
▸ Data memory editor 8 words wide
▸ Boot memory editor 8 words wide
▸ Show only the lowest byte of word in
ASCII
When this option is activated, the program shows the
ASCII translation of only the lowest byte of word, which
can be useful especially for PIC MCUs.
▸ Mask ID positions while reading from
device, from file, etc.
Some manufacturers' specifications recommend saving
only masked data (with only four bits usable) in ID
positions. With this option activated, the program always
applies this bit mask when reading ID positions from
different sources.
Page 54
▸ Mask ID positions during direct user
input
With this option activated, the program applies the bit
mask to each user-modification of ID positions. For further
information see ▸ Mask ID positions while reading from
device, from file, etc.
.
▸ Configuration memory editor: show cfg
word instead of fuses
This option is recommended for advanced users only. It is
not saved in the UP configuration file for safety reasons.
Direct editing of fuses is understood as direct writing of a
configuration word value in the hexadecimal form.
When a “non-translatable” configuration word is entered,
the program leaves the unrecognized items unchanged
unless the user changes them him/herself. This typically
concerns CP fuses having several bits but only two
values.
Options ➙ Program settings ➙ Serial
numbers
Keyboard shortcut: Shift+F10
For further information on working with serial numbers
see
Serial Numbers.
▸ Serial numbers
This tab allows you to choose whether serial numbers are
to be used and if so then whether they should be read
from a file or computed and whether they should be
automatically written to the corresponding location.
▸ Prepare S/N before programming
This option prepares a serial number in the selected
memory location before the actual device programming.
▸ Find successor after programming
Once one programming procedure is successfully
completed, the system proceeds to the following serial
number. If this option is not activated, it is still possible to
proceed to the following number manually by clicking the
Next button on the Serial numbers tab – see
Serial
Numbers
.
▸ Prepare S/N after programming
This option causes that a serial number is prepared in the
selected memory location after the device programming.
▸ Serial number interval
This defines by what value the following serial number
will be larger or smaller.
▸ Log to file
By activating this option and by selecting a log file in the
field, information about correctly and incorrectly
programmed devices as well as the programming time is
saved in the selected file.
▸ After project load set actual SN
according to the last in the log
When this option is enabled, the last programmed SN is
read from the log file and when the programming is
logged as errorless the next SN is computed from the
read value else the last SN is set again.
The log file has to exist and the last record has to contain
a SN.
This function can be useful when the serial numbers are
enabled and saving of UP project files is disabled, in such
a case the actual SN will not update in the project file on
program close.