presto_en.pdf - 第51页
Page 51 ▸ Display descriptio ns on too lbar buttons Tool names are displayed n ext to individ ual tools in t he toolbar. If the Descriptions on toolbar buttons to the right option is used, the total t oolbar height is re…
Page 50
▸ Do not perform blank check after
erasing
This option speeds up the programming process and is
useful especially for debugging. The danger is that an
incorrectly erased device is subsequently incorrectly
programmed and the fault only gets detected later. On
the other hand, a device is erased incorrectly only once in
several hundred attempts.
▸ Do not erase device before
programming
The device is not erased before programming.
▸ Do not erase data memory before its
programming
This option only concerns programming of Atmel AVR
devices e.g. ATmega8. Data memory of this family
devices does not require to be erased before
programming. If this option is not activated, whole device
will be erased before programming.
▸ Do not verify unprogrammed words at
the end of the memory
If there is a location at the end of the code/main memory
containing only default values, it is not verified.
This option speeds up the verification of the programmed
memory as the content of the “empty” memory at its end
usually does not matter.
▸ Do not verify
This option completely switches off the verification of a
programmed device. Such off-switching can radically
speed up the programming process during development.
This option must not be activated for production as
correctness of the programmed content would not be
guaranteed.
▸ Verify with two supply voltages
This option is available only for FORTE and only for the
internal power supply from the programmer. It allows you
to perform the verification at two different power supply
voltages defined by the user.
Some device manufacturers recommend to verify the
content after production programming at two different
voltages corresponding with the approved range of the
device's power supply voltages.
Options ➙ Program settings ➙
Panels
Keyboard shortcut: Shift+F10
This part of the Options menu allows you to alter the
application's appearance. The user can set where and
how some control components are to be displayed.
▸ Display selected device on toolbar
In addition to the status bar, the selected device is also
displayed in the toolbar.
▸ Display selected programmer on
toolbar
In addition to the status bar, the selected programmer is
also displayed in the toolbar.
▸ Display the status bar in the lower part
of the window
This option determines whether the status bar is to be
displayed or not.
▸ Display icons on toolbar buttons
Icons of individual tools are displayed in the toolbar.
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.