ICD2 Testing,Trouble Shooting

Status
Not open for further replies.
Still no luck, swapped Max232. Some where I suspect theres
a bad part in my circuit, or perhaps the circuit itself is wrong.
I've dissassembled and reassembled many times now. Maybe
one more time will be the trick.


Thanks for the help Guys
Gordon
 
One other thing,
The Zener diode to the MCLR pin and pin 4 on the DB9 connector. Does
this pull the MCLR high/low from my PC? IF this fails, will the 16F876A
be able to load the OS from MPLAB or establish communcitaion.
Maybe another computer will resolve this issuse. Has there been none
trouble with laptops not working with ICD2 clones?

Any thoughts?
Gordon
 
Tried another computer and recieved the exact same results.
This almost proves the ICD2 I built is the problem and not
my comm port or MPLAB. Disabled FIFO and checked the comm
port with another device.

Looks like its time to rebuild the ICD2 again.
Thanks to all for the help.
Gordon
 
GRC said:
Must be my circuit, the 7805 gets fairly warm. Almost hot to the touch.

This should never happen as the 16F876A and MAX232 together will only consume less than 20mA. Measure the 5V current by a DVM and find out where the problem is first.

Measure voltages on the pins of MAX232 connected with capacitors and confirm that either positive or negative voltages of 8V or more is present on these pins.

A bad PIC reset circuit will prevent the PC from resetting the PIC and thus failed to enable it to connect to the PC. With the correct bootloader inside the PIC active, it will listen via the serial port and will accept data from the PC. There is no need for the OS to be downloaded first for this to happen.

On many ICD2 clone circuit design there are two LEDs(Busy, error) that you can connected to the PIC pins for indication. You can consider adding that to give you more information during troubleshooting.

If you have fitted these two LEDs, at this point in time you can re-program the PIC with a simple LED flashing routine(using a serial bootloader, details info/link shown in Jay's signature) and confirm that the PIC, its crystal OSC and all the communication circuit are all functional, before you reload it again with the ICD2 bootloader firmware and try the PC communication again.

Check your private message for info on the reset circuit I'm using. Best of luck to you and merry X'mas.
 
Well I think I finally got it working. Rebulit my circiut, swapped a few caps
around. Now I get the following messages from MPLAB


Connecting to MPLAB ICD 2
...Connected
ICD0082: Failed MPLAB ICD 2 operation
MPLAB ICD 2 Ready
Downloading Operating System
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
Target Device PIC16F876 found, revision = b8
...Reading ICD Product ID
Running ICD Self Test
...Passed
...Download Operating System Succeeded
MPLAB ICD 2 Ready


Also have a few more icons high-lighted in the IDE. This is so cool.

Thanks to you all for your help. I really appreacaite it.
Gordon
 
MPLAB 4.62 ICD2 Serial Log :

Code:
E21511     CreateFileA:COM3
E21770     EscapeCommFunction:00000006
E21770     EscapeCommFunction:00000005
E21AB5       #Connecting to MPLAB ICD 2
E21AB5     WriteFile:Z
E21D4B     ReadFile:
E21770     EscapeCommFunction:00000006
E21770     EscapeCommFunction:00000005
E21AB5     WriteFile:U
E21D4B     ReadFile:u
E21AB5     WriteFile:<0801C9>
E21D4B     ReadFile:[0E01010401FC]
E21AB5     WriteFile:<0807CF>
E21D4B     ReadFile:[0A07053D]
E21AB5     WriteFile:<0A2A8854>
E21D4B     ReadFile:[082ADB]
E21AB5       #...Connected
E21AB5     WriteFile:<0E0600FFFF53>
E21D4B     ReadFile:[0806CE]
E21AB5     WriteFile:<0A050036>
E21D4B     ReadFile:[0805CD]
E21AB5       #...Connected
E21AB5     WriteFile:<0837D2>
E21D4B     ReadFile:[0A37994D]
E21AB5       #Setting Vdd source to target
E21AB5     WriteFile:<0834CF>
E21D4B     ReadFile:[0A347F55]
E21AB5     WriteFile:<0835D0>
E21D4B     ReadFile:[0A359B54]
E21AB5     WriteFile:<0837D2>
E21D4B     ReadFile:[0A37994D]
E21AB5     WriteFile:<0834CF>
E21D4B     ReadFile:[0A347F55]
E21AB5     WriteFile:<0835D0>
E21D4B     ReadFile:[0A359B54]
E21AB5     WriteFile:<082CDD>
E21D4B     ReadFile:[0A2C0248]
E21AB5     WriteFile:<184A003FFFFE000000014F>
E21D4B     ReadFile:[084ADD]
E21D4B     ReadFile:{820EDF}
E21D4B     ReadFile:[084ADD]
E21AB5       #Target Device PIC18F4680 found, revision = a2
E21AB5     WriteFile:<0A330037>
E21D4B     ReadFile:[0833CE]
E21AB5     WriteFile:$7F00

E21D4B     ReadFile:02
E21AB5     WriteFile:<0808D0>
E21D4B     ReadFile:[0A080039]
E21AB5       #...Reading ICD Product ID
E21AB5     WriteFile:<0801C9>
E21D4B     ReadFile:[0E01010401FC]

E21AB5     WriteFile:<082CDD>
E21D4B     ReadFile:[0A2C0248]

E21AB5     WriteFile:<0807CF>
E21D4B     ReadFile:[0A07053D]

E21AB5     WriteFile:<0802CA>
E21D4B     ReadFile:[12020000000000A5]

E21AB5     WriteFile:<0A330037>
E21D4B     ReadFile:[0833CE]
 
Unable to connect with MPLAB ICD 2

Unable to connect with MPLAB ICD 2

I got over it by just reinstalling driver
 
Status
Not open for further replies.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…