Microchip Technology Universal Device Programmer DV007004 DV007004 User Manual
Product codes
DV007004
© 2006 Microchip Technology Inc.
DS51464C-page 107
MPLAB
®
PM3
USER’S GUIDE
Appendix B. Troubleshooting
B.1
INTRODUCTION
The troubleshooting information in this chapter can help you resolve typical problems
or obstacles in programming microcontroller devices. Topics covered in this appendix:
• Troubleshooting Hardware
• Troubleshooting Operational Problems
• Troubleshooting Software
• Common Problems
• Error Messages – PC
• Error Messages – LCD
• Limitations
or obstacles in programming microcontroller devices. Topics covered in this appendix:
• Troubleshooting Hardware
• Troubleshooting Operational Problems
• Troubleshooting Software
• Common Problems
• Error Messages – PC
• Error Messages – LCD
• Limitations
B.2
TROUBLESHOOTING HARDWARE
Some problems involving the hardware include:
• Communication Failure
• Ensuring Proper Socket Module Contact
• Socket Module Failure
• Communication Failure
• Ensuring Proper Socket Module Contact
• Socket Module Failure
B.2.1
Communication Failure
Appendix A. “Hardware Specifications” gives the data for connecting the MPLAB
PM3 Device Programmer to a communications port. If communication fails, check your
communications port.
PM3 Device Programmer to a communications port. If communication fails, check your
communications port.
B.2.2
Ensuring Proper Socket Module Contact
After changing a socket, insert a blank device and do a Blank Check to ensure the
socket is making proper contact. A blank device will show erased. An improperly seated
module socket may cause a device to fail the Verify process with errors claiming that
the bad data is all zeros (0000).
socket is making proper contact. A blank device will show erased. An improperly seated
module socket may cause a device to fail the Verify process with errors claiming that
the bad data is all zeros (0000).
B.2.3
Socket Module Failure
If you can program a master chip, and if you can read and try to program
code-protected chips, but the chips fail the programming attempts, then potential
socket pin damage may be the cause of the problem. Contact your Microchip Field
Application Engineer (FAE) if your socket module is not operating properly.
code-protected chips, but the chips fail the programming attempts, then potential
socket pin damage may be the cause of the problem. Contact your Microchip Field
Application Engineer (FAE) if your socket module is not operating properly.