Microchip ICD3 Issue – Part 2

Continuing from my previous post (if you haven’t read it yet, read it here)

Another issue seen while using ICD3 is given below:

Capture

If the detected Target Device ID is 0x0000000, then there is some issue in the communication between ICD3 and the target device. Please re-check all your connections.

The reason for this other target device ID mismatch could be any one of the following:

  • A wrong target chip is selected in MPLab project.
  • Ensure whether the target device is the same as you think.
  • You might need a Debug adapter to Debug.

Narrow down the issue by doing Self-Test procedure on ICD3 (refer Part 1). If it goes through, then it is obvious that the issue is on the target board. You will have to check the following in such circumstances:

  • Ensure the 5 programming pins on the target (PGC, PDA, nMCLR, VDD, VSS) are properly connected and that the device is getting VDD from your power source.
  • There is proper decoupling capacitor on all the required pins.

 

 

Thanks a lot for stopping by to read this post.
If you like this post, share it with your friends.
If you have any suggestions, leave a comment.
If you never want to miss a post, please subscribe.

Advertisements

Microchip ICD3 Issues – Part 1

To design ICD3 programming circuit, follow the design guidelines found in the below link:

http://ww1.microchip.com/downloads/en/DeviceDoc/52081A.pdf

Note: nMCLR pin should be pulled to Vdd by 4.7k as shown in figure below:

Interface ICD3

A frequently seen issue while using ICD3 is given below:

Capture

To resolve this issue, follow the steps below:

Self test ICD3:  The Test Interface board is meant for checking communication between the PC and ICD3. This test ensures that the ICD3 is functioning properly. After connecting the ICD3 Test Interface board to the ICD3, you need to select “Run ICD3 Test Interface” from Debugger ->Settings->Status tab.

Following messages in the Output window confirm that the ICD3 is working fine:

Capture

If the self test pass then change the ICD3 settings in project properties:

ICD3 settings

Uncheck the “use latest firmware” and manually browse to the firmware folder/file.

firmware path

Using the default firmware will fix this issue .

Let me know if this helped 🙂

Thanks a lot for stopping by to read this post.
If you like this post, share it with your friends.
If you have any suggestions, leave a comment.
If you never want to miss a post, please subscribe.