Page 58
▸ 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.
▸ 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.
To Next Page
Loading...