This is a working RS232.... ICD2 !!!!

[myown]

rs232 ind2

I use 16F876A, MAX232, and 3 bipolar transistor - work fine.

 

[Asnake]

bootloader with icd2

I use 16F876A, MAX232, and 3 bipolar transistor - work fine.

Really? 16F876A+MAX232+3 transistor==ICD2??I'm very interesting in that! Will you share that?

 

[acinfo32]

icd2 clone rs232

Dear all,

I have also a problem with updating the firmware.
With the original firmware from crazyduck I get while connecting without firmware update:

ICDWarn0031: MPLAB ICD 2 contains the incorrect operating system for the selected device. Would you like to download the correct operating system? [NO] Setting Vdd source to target ICD0133: Firmware does not support command (0x9). ICD0082: Failed MPLAB ICD 2 operation ...Reading ICD Product ID ICD0133: Firmware does not support command (0x8). ICD0082: Failed MPLAB ICD 2 operation Running ICD Self Test ...Passed MPLAB ICD 2 Ready
And in the version tab of the setting I see a firmware version 02.00.21.00 and so on
If I update the firmware I get

Downloading Operating System ICD0152: Failed to read all of requested bytes (0x0 of 0x8) ...Download Operating System Failed ICD0152: Failed to read all of requested bytes (0x0 of 0x2) ICD0082: Failed MPLAB ICD 2 operation ICD0082: Failed MPLAB ICD 2 operation ICD0082: Failed MPLAB ICD 2 operation ICD0082: Failed MPLAB ICD 2 operation MPLAB ICD 2 Ready
And the version tab is now total empty. After a reset of ICD the version is back at 02.00.21.00.

I’m using v6.60 of mplab. ORIGINAL FIRMWARE.hex (from crazyduck) only WRT enabled, HS oscillator pic16F877 (NOT the A version). Dig. Pot replaced by normal Pot and power at 13V.

My questions are:
Does the ICD work with the new version of mplab v6.60?
Does it need the 13V voltage to program its own firmware (mclr is at vpic)?
The 1% resistances I can get have slightly different values (e.g. 6K74 instead of 6k8) could this be a problem?
Can anyone with an updated (from mplab v6.60) pic16F877 (NOT A version) read the pic and post it? So I can experiment with the newest loader and firmware.
Does anyone had the same problems and solved it?
Are there other things you can do wrong?

Regards
Acinfo32

 

[Regnum]

icd2 pcb

Acinfo32,

Both firmware and MCU you're using are wrong.

You must use a 16F877A, and the firmware "BootLoader" attached by Zaphod42 in the first page of this topic.

 

[acinfo32]

icd2 fucking

Dear Regnum

On the first page Crazyduck says

Hi,
I solve my problem. It was about the "A" suffix of 16F877.
You must not use 16F877A to put the firmware, but a 16F877.

HI,
The firmware can be updated with no problem if you use a 16F877.

Therefore I thought it should work. But according to your post I should use the 877A version. I will order the 877A and hope that its the answer.

Regards

Acinfo32

 

[Regnum]

16f876 max232

Acinfo32,

The original bootlader from CrazyDuck has some firmware merged that MPLAB isn't able to update at all.

When I checked this combination (16F877 + Original Firmware) with MPLAB 6.5 I obtained the same freaking messages you've posted...

Zaphod42 fimware doesn't run into a 16F877, so the solution is burning a 16F877A with zaphod42 firmware (BootLoader.hex)

I am currently using my ICD2 clon with a 16F877A and Zaphod42 Firmware successfully under MPLAB 6.5.

Good luck

 

[Zaphod42]

icd2 bootloader 16f877

Acinfo32,

The bootloader I provided was only modified to allow it to work with the 16F877A. For your 16F877, just use the original file (BL010101.HEX) in the ICD2 directory of MPLAB.

Zaphod

 

[acinfo32]

max232 voltage doubler not working

@Zaphod42

Tankt you for showing which file the bootlooder is. It’s very usefull.
But if I programm the file …\ICD2\BL010101.hex in the PIC16F877 (no A) with only the WRT option bit on and HS oscillator. Then put the chip in the ICD I get the same problem:

Connecting:
...Connected
ICD0082: Failed
MPLAB ICD 2 operation MPLAB ICD 2 Ready

Download Firmware ICD10010205.hex:
Downloading Operating System
ICD0152: Failed to read all of requested bytes (0x0 of 0x8)
...Download Operating System Failed
ICD0152: Failed to read all of requested bytes (0x0 of 0x2)
ICD0082: Failed MPLAB ICD 2 operation
ICD0082: Failed MPLAB ICD 2 operation
ICD0082: Failed MPLAB ICD 2 operation
ICD0082: Failed MPLAB ICD 2 operation MPLAB ICD 2 Ready

B.t.w. in ICD Pic is oscilating at 20MHz, MCLR = 5V and power is ok. And I use a female D-Con at the ICD.

Regards
Acinfo32

 

[Regnum]

pic876a pdf

acinfo32,

Did you check MAX232 self-generated supplies too?
(+10V at pin#2, and -10V at pin#6)

In original schematics I noticed that polarity of C12 is wrong, maybe it's taking supplies down, and fucking the communication.

 

[acinfo32]

mc41010

Dear Regnum

The voltages are +/- 8V. (Maybe with an 1u i can get it some higher)
The polarity of C12 is indeed wrong but also the voltage at the - of C10. This should not be GND but VPIC. I have solved these problems and now the firmware can be updated.

With the F877 and the updated (to v01.02.05.00) crazyduck fireware i get one error

MPLAB ICD 2 Ready
Downloading Operating System
Connecting to MPLAB ICD 2 ]
...Connected
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x40, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
...Download Operating System Succeeded
MPLAB ICD 2 Ready

But this should be normal if no target is attached.

Thanks you all for you help,
Acinfo32

 

[crazyduck]

dspic30f4013 bootloader download

Hi,
Sometime ago I've the same problem with "invalid target". I check my cable and connectors between the target and the ICD2 module. This cable must be short. The quality of the cable is very important too.

CD

 

[Regnum]

pic disassembler+pic12f629

Target ID is 0x00 if you have no device attached

1 ft. cable length is OK

Thanks Crazyduck and Zaphod for this great contribution to the poor engineers crusade

 

[joe123]

db9 rs232 schematic max232 self powered

Hello All... Now I hope I dont get shot for asking this question....

Ive decided to build an ICD2. I have read and read this forum up and down and gotten a fairly good understanding of what I need to do..

1. I will be using a 16F877A thus I must program with BootLoader.hex (also known as BootLoader16F877A.hex). WRT set to enabled and HS as the oscillator configuration. I can then automatically update with new frimware from MPLAB.

2. I have a set of about 10 different schematics downloaded from this and other threads. Unfortunetally, I cannot make sence of which one is the most curent and functional (I now many of the early versions had minor errors which were copied into other members versions). I am not interested in USB since it is too hard to get a hold of the Cypress USB IC.. Can someboody PLEASE direct me to the most current shematic..

Below are some of the schematics I'v found.

Regards: Joe

 

[simce]

mplab icd2 rs232 bug

Well i build ICD2 and it seamed to work fine, but now i noticed a problem. Well i can program and debug 18F , and 12F, series, but when i try to debug 16F877 on 18-20Mhz running target i got info that target is in running and not debug mode! I can debug 18F series even on 20Mhz without any problem! If i lower the frequency of target MCU everything is just fine. I'm using 74HC126 (also tried with 74HCT126, but without sucess) drivers for target ICSP pins and DG411 for Vpp. In original ICD2 fro MCHP 74AHC126 are used. Can this be the problem? Does anyone else experienced the same problems?

 

[simce]

fds4435 equivalent

Or, better will be if anyone can test his ICD2 on target 16F877 running on 20MHz quartz. If this test is sucessfull please, tell me the used sch/pcb combination.

 

[alex_ts]

18f877a eeprom externa

I don't think it is possible, because ICD2 connecting to the computer with COM port, so you have to use exact XTAL for exact baudrate!!

 

[simce]

icd2 hc126

I don't think it is possible, because ICD2 connecting to the computer with COM port, so you have to use exact XTAL for exact baudrate!!

What are you talking about? I ment if someone that has buid ICD2 using one of the schematics posted here can test its own ICD2 on target system that uses PIC16F877 running on 20MHz. This means that RS232 connection is made between ICD2 and PC, and not target board/MCU and PC.
Here is how i tested my ICD2.
Target board with quartz of 18.432MHz and required power supply for stand alone mode when ICD2 is not used. On the same board i connected ICD2 made by me and target 16F877 which has LED connected on PORTC,0. I wrote simple se that blinks led on pin PORTC,0. But after proggraming of target MCU i got message that MPLAB can not connect to debug executive on target MCU that is in Running Mode. Than i connected original mictochip ICD2 instead of my homemade version and everything was just fine (here again i used RS232 connection between PC and Microchip's ICD2). Than i replaced target MCU PIC16F877 with PIC18F452 and again i used my homemade ICD2 and everything was just fine.
Than i put back PIC16F877 and replace quartz with 8MHz rezonant frequency, and used my homemade ICD2 whth no poblems at all.
So the question again is:
Does anyone tested his homemade ICD2 in debug mode on PIC16F877 running on frequencies close to 20MHz. Or can anyone test his homemade ICD2 on this configuration so i can know if i have made a mistake or there is something wrong with the schematics?!
The problem is the same also with PIC16F877AI/P-20; PIC16F876I/P-20; PIC16F876A I/P-20

 

[Testu]

parametre rs232 icd2

Does anyone tested his homemade ICD2 in debug mode on PIC16F877 running on frequencies close to 20MHz. Or can anyone test his homemade ICD2 on this configuration so i can know if i have made a mistake or there is something wrong with the schematics?!
The problem is the same also with PIC16F877AI/P-20; PIC16F876I/P-20; PIC16F876A I/P-20

I'm using 16F877A @ 20MHz just now. It's working fine. May be you are using too long cabel?

Schematic - icd2 clone 3 2 from https://icd2clone.narod.ru

 

[Testu]

slow down programming icd2

I'm using 74HC126 (also tried with 74HCT126, but without sucess) drivers for target ICSP pins and DG411 for Vpp. In original ICD2 fro MCHP 74AHC126 are used. Can this be the problem?

74HC126 and 74HCT126 will work with 5V targets good enough, but without them icd will work even better. For 2V - 3V tagets you have to use 74AHC126, 74VHC126 etc. They have 5V tolerant inputs when Vcc = 2V - 6V.

But it's not your case (20MHz @ 4.5V - 5V)

 

[simce]

mchp bootloader

I've tested target board with PIC16F877 I/P-20 with quartz of 18.432MHz and power taken from ICD2 and from its own +5V power supply. I've tested this using original ICD2 cable and one short cable of about 5cm to see if this is the problem. I'll test you schmatic to see how it works.
Maybe i have made a mistake in my own board.