forte_en.pdf - 第21页
Page 21 AVR in HV P mode Fig.11: AVR in HVP mode (e.g. ATtiny84 1) 1) Some devices require also other pin s t o b e c onnected to GND, t his c an be found in a pict ure in the device datasheet in ch apter "High-vol…
Page 20
2) The whole device must be erased before
programming if code/main memory protection (CP) or
data memory protection (CPD) is active.
3) Some devices cannot be erased when CP or CPD is
active if the power-supply voltage is less than 5V.
4) If a microcontroller has more than one power-supply
VDD or VSS pin, all of them must be connected
including the AVDD and AVSS pins.
5) If the LVP mode is used, it is recommended to check
whether the LVP fuse is still set after erasing the part.
6) Programming of PIC32 devices is supported by
means of the ICSP interface.
7) Devices with an ICPORT fuse must have the
dedicated ICSP port off for LVP programming.
8) PIC24 and dsPIC33 devices may be programmed
using PE (Programming Executive) or using the
standard method. Programming by means of PE is
usually faster.
9) When the MCU debug mode is enabled using a fuse,
the programmer cannot communicate with it.
AVR Microcontrollers
Fig.10: AVR microcontroller
1) A source of the clock signal, which is set in the device
or which will be set by fuses during programming
must be connected to the device. A crystal must be
connected if set up as the clock source.
2) Device fuses have been set up by the producer to the
internal oscillator with a frequency of 1MHz. In the
initial programming, the device should be
programmed with “Oscillator frequency” set up at
“>750kHz” or lower in the “FORTE programmer
settings” window.
3) Not all AVR devices allow use of a crystal
(e.g.ATtiny13, ATtiny15).
4) After the device fuses are correctly set up, right-click
(i.e. using the right mouse button) inside the
Configuration window and choose Learn fuses.
This saves the fuses in the up.ini file or in the project
if used. This is necessary due to the fact that .hex
files for AVR microcontrollers themselves do not
contain configuration fuses. If a device is
programmed from the command line, a .ppr project
file containing saved fuses needs to be used.
5) Ticking the Open file with data memory
automatically option in the File menu loads data
for the data memory simultaneously with the code/
main memory data.
6) Use the EESAVE fuse if preservation of data memory
is required. If the EESAVE is active, choose Program
all except data memory for programming,
otherwise a warning appears at this place (blank
check of data memory).
7) HPRAVR is an optional accessory for programming
AVR microcontrollers in applications with the
ISP10PIN standard connector on the device's side.
8) Some AVR devices have their ISP interface provided
at different pins than the SPI interface. Further
information can be found in the device data sheet (in
the Serial Downloading section).
Page 21
AVR in HVP mode
Fig.11: AVR in HVP mode (e.g. ATtiny841)
1) Some devices require also other pins to be connected
to GND, this can be found in a picture in the device
datasheet in chapter "High-voltage Serial
programming".
AVR with TPI Interface (e.g.
ATtiny10)
Fig.12: AVR microcontroller, TPI interface
ATxmega with PDI Interface
Fig.13: ATxmega microcontroller, PDI interface
1) For programming that uses the JTAG interface,
devices must be connected as described in the
JTAG
Interface section.
AVR with UPDI and RESET pins
Fig.14: AVR microcontroller with separated UPDI and RESET
pins
1) Some devices with separated UPDI and RESET pins
have to be connected in accordance with the "AVR
with UPDI Interface" connection example. The
connection for the selected device can be found in
the "Device/Device info" menu of the UP software.
Page 22
AVR with UPDI Interface
Fig.15: AVR microcontroller, UPDI interface
1) Some of the devices with separated UPDI and RESET
pins have to be also connected this way. The
connection for the selected device can be found in
the "Device/Device info" menu of the UP software.
2) On UPDI pin a 12V pulse is used to enter the
programming mode of ATtiny UPDI.
3) When the programmed device quits the
programming mode or the UPDI interface is disabled
during programming, a power-on reset of the
programmed device has to be done.
4) For AVR with UPDI data files with memories mapped
from zero are expected and their fuses save to a
project file same as for older AVRs, because Atmel
Studio creates the data files this way.
Atmel 8051
Fig.16: Atmel 8051 microcontroller
1) The SS pin must be connected only for AT89LP2052 /
4052 / 213 / 214 / 216 / 428 / 828 / 6440 / 51RD2 /
51ED2 / 51ID2 / 51RB2 / 51RC2 / 51IC2.
2) AT89LP213, AT89LP214 and AT89LP216 have the
inverse reset logic. Thus an appropriate resistor must
be pulled-up to VCC.
3) FORTE can not program devices containing the letter
“C” in their name, however, it supports devices with
“S” in their name, of which some are compatible with
the “C” types. For example, AT89C2051 is not
supported, but AT89S2051 is.
4) The software assumes that while programming
AT89LP52, the device’s POL pin is in logical1. If POL
is in logical0, the Inverse RESET option should be
activated in the program. For AT89LP51RD2,
AT89LP51ED2, AT89LP51ID2, AT89LP51RB2,
AT89LP51RC2 and AT89LP51IC2 the software
assumes the POL pin in logical0.