Page 98
10
TROUBLE-SHOOTING
This chapter describes how to proceed if experiencing
difficulties with device programming. It also describes
testing utilities for FORTE designed to check if the
programmer is in good condition or damaged. Please go
through all the tips and tricks before you send your
programmer to a service shop.
The testing utilities are not part of the UP software
installation, but they can be downloaded separately from
http://www.asix.cz/supp_testers.htm. They are localized
only in English.
10.1
Tips and Tricks
Should you experience difficulties with programming, we
recommend checking the following points:
• Check the microcontroller and programmer
connections according to the description in Connecting
to Application. Even though it may seem trivial, it is
recommended to check the connection twice and to
assume the second time that the link does not always
lead where you want it to or it leads to more than one
point.
• If a crystal or other auxiliary devices are used for
programming, (typically pull-down or pull-up resistors),
check if their values and connections are correct.
• It is advisable (and often necessary) to have blocking
capacitors at the power supply of the device to be
programmed.
• If the device to be programmed has more than one
power-supplying pin, all of them must be really fed. It
is often recommended to check their voltage with a
voltmeter.
• Use of the latest version of UP is recommended. If you
are still using an older version, an update is
recommended.
• Are you programming a new device or has it been
previously programmed? If so, the problems may be
caused by unsuitably set fuses in the device.
• The length of the ICSP cable should not exceed 15cm.
• Make sure that there is no additional capacity present
at the programming (data) pins. Consider if circuits on
the programming pins could cause too large a load for
programming.
• It is important that the crystal or the communication
speed settings reflect the reality in devices that need
that settings.
• Some devices may be programmed using several
different methods. Programming problems may be
caused by selecting a different programming interface
or a different programming mode than the ones that
the application is prepared for.
If none of the above tips help to eliminate the problem
and if it absolutely sure that the device to be
programmed is not faulty, the fault may lie in the
programmer.
To easily find out whether the programmer is in order or
not, you can use the testing utilities described in the
following chapters.
10.2
FORTE Tester
The FORTE Tester utility easily tests the “health
state” (usability) of the FORTE programmer right at the
customer's site.
In order to run it successfully, only one FORTE
To Next Page
Loading...