presto_en.pdf - 第52页
Page 52 ▸ Warn when l oaded HEX does no t contain CFG mem ory data If t he file does not contain con figuration memory data and the dat a are expected for the chosen device, a warning message is displayed. ▸ Warn when l …
Page 51
▸ Display descriptions on toolbar buttons
Tool names are displayed next to individual tools in the
toolbar.
If the Descriptions on toolbar buttons to the right
option is used, the total toolbar height is reduced to a
half.
▸ Show mass production counter in
status bar
This option displays the mass production counter in the
status bar. The counter shows the number of devices
programmed and the number of devices programmed
successfully.
If you use the Count all actions option, the counter
includes all actions performed with the device (such as
reading, erasing, data memory programming, etc.).
Show values description displays explanatory notes to
individual counter items for easier understanding.
If you want to exclude operations that triggered a
warning from the correct operations, use the If action
ends with warning assume as erroneous option.
The choice Reset counters on project open causes,
that the counters are reset on any project file load,
including automatic project load during program start.
Counter style allows you to choose whether the counter
should display the good/bad or good/total figures.
The Counter reset, button can be used for zeroing the
counters while their initial values can be set in the Preset
counter values fields.
Options ➙ Program settings ➙ Files
Keyboard shortcut: Shift+F10
This tab holds all the settings for reading data from and
saving data to files.
▸ File save style
The File save style panel offers the possibility not to
always save all areas of all editors in the file, but rather
only some. UP then asks questions based on the saving
style settings before saving different project editors.
▸ Do automatic check for newer version
of actual file
This option helps especially in debugging a program. The
program re-loads the file if it detects a change in the file
modification date.
▸ Never ask and never save changes to
data file
When this option is enabled and data in an editor have
been changed, before opening of an other file, before
closing of the application etc. the application will not ask
and will not save the file which is currently open.
▸ Check device type when loading .hex
file
If the device type has been saved in the corresponding
Intel-HEX file and it does not agree with the currently
selected device type, the program points out this
discrepancy.
▸ Save device type into .hex file
The program adds one more line below the end of file
command specifying the type of device for which the file
is being saved.
Such a modified file does not comply with the Intel-HEX
format, but most programs working with the Intel-HEX
format ignore this line.
For further information about the Intel-HEX format see
Appendix C: Intel-HEX File Format.
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.