Table of Contents
Advertisement
7.2 MCUs Do Not Function Normally
The program operates normally on the emulator, but when the MCU that has normally been written
is attached the same program does not function normally.
(1) Is the offset address specified correctly when copying data into the PROM programmer?
(2) In the emulator, NOPs are often inserted in the area where the program has not been read, therefore
(3) The emulator and the actual MCU may differ in characteristics. Consult the user's manual of the
7.3 Other Precautions
7.3.1 About the Recommended PROM Programmers
Not all PROM programmers available on the market can be checked to see if they function properly.
There are several PROM programmers that we have verified to function properly. These products are
listed as recommended PROM programmers in this instruction manual. Other PROM programmers
may also be used providing that you verified them to function properly.
Note: No matter which type of PROM programmer you use, it is necessary to verify completion of
7.3.2 About Reading Out of Device Identification Code *
Please do not use the PROM programmer's device identification code readout function.
Using this function may break down the MCU. The device identification code is included in EPROM
to indicate the manufacturer code and device code; it is not included in the MCU.
1
*
7.4 How to Request for Support
After checking this manual, fill in the following information and email to your local distributor.
For prompt response, please specify the following information:
(1) Contact address
(2) Product information
the program happens to appear functioning normally even though it may have gone wild. Check
your program again.
emulation pod to check for differences in characteristics again.
programming by executing screening, etc. that are stipulated for each MCU used.
Depending on PROM programmer manufacturers, this may be referred to by another name (e.g.
ID code).
• Company name
• Department
• Responsible person
• Phone number
• Fax number
• E-mail address
• Name of the programming adapter
• Serial number
• Date of purchase
• Target MCU
• Symptoms (Fails blank check/Cannot write a program/Fails verification etc.)
• Detailed symptoms
• How often does the problem occur? (2 out of 10 etc.)
• When did the problem start to occur? (Since purchase/Used to work correctly)
• Type name of the PROM programmer (Advantest R4945A etc.)
• Specified device when writing to PROM (M27C101 etc.)
• Specified programming area when writing to PROM
• Switch settings of the adapter when writing to PROM
1
( 15 / 18 )
Advertisement
Table of Contents
