[SOLVED] Project to replace CY7C64613 in the ICD2

mpusbclean.exe

Zedman,

How can the PIC18F4550 reset the PIC16F877? It seems to me the pic16f877 should be reset for each connection. Otherwise there will be a connection error.

pickit inductor fails

I tought on it too cos Cypress had pin connected to 877's MCLR trough a transistor. I will check wether there is an output pin to drive it's MCLR.

Added after 1 hours 17 minutes:

It's working.

- Actually not pass (all) self tests, but it's my board's fault.
- Another thing is what I mentoined before that it's owerwrites some of the flash and after that, on EVERY connect it downloads 4550 OS. It goes on after upgrade but it should not do that.

icd2w2k.sys error

Hey nice! Well done.

Dont know what to think of those 64 bytes @0x4e00 though..

unable to re-program icd2 usb os firmware.

Hi. I thing that 4550 reset 877 via RB3.
RB3(4550) is connected via mosfet(or bipolar) transistor inverter to MCLR pin on 877. It's working for me. Not all test are passed but my board not finished( missing parts around debug connector, Vpp and Vdd control.... ).


Best Regards.

Added after 1 hours 11 minutes:

Hi, Rkodaira. Would you please check what do you have on these ports:
RA2
RA3
RA5
RB1
RB2
RB3
RB5
RB7
RB7
RC3
RC6
RC7
RE2

Thanks.

Added after 5 hours 25 minutes:

Hi, again. I complete my ICD2 and it works fine. I test download FW to ICD and PIC18F452, and debug PIC18F452. Everything is ok. Thanks for info.

Best Regards.

driver usb to rs232 redfox

Ok, this is where i am, my MPLAB issues this
01 instead of the 07 of zedman

Send 0x12 bytes to the device:
03 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..


and this is what my 4550 says

Get 0x8 bytes from the device:
03 00 01 00 FF FF 06 34 ....ÿÿ.4

ff ff 06 34, what this means?

eagle legalizer

Lads I have got to hold my head up high and take my hat of to you guys working so hard on this new ICD2 clone,

Will you sharing teh code and schematics with us all I know that it might be cheecky of me to ask considering that i really have put no input into this project but i would if i could but i would not know where to begin and it amazes me how good you people know your stuff,

cheers

wizpic

icd download operating system failed

petarpav said:

...
Hi, again. I complete my ICD2 and it works fine. I test download FW to ICD and PIC18F452, and debug PIC18F452. Everything is ok. Thanks for info.

Best Regards.

Click to expand...

And it is possible to find out details of your project or this information is top secret?

connected tool is not an mplab icd 2

Hmm...

Yes I tought it will come, but not as soon as it came.
People asking for docs/schematics/howtos on a thing that took 2-3 weeks of work for 3-4 man.
I am strongly thinking about setting up a webpage for this project with a Donate button (not points, $). Brem, Rkodaira, Albert, Kripton what do you think?

--------

narccizzo, what kind of 877 u are using? Do you initialize 0xF0 in the 4550?

--------

petarpav,

RB3 is connected to 877 MCLR on my board too.
Please read up your 4550 and check the 64 bytes @0x4E00 if there are changed from 0xFF to anything else?
Does MPLAB downloads OS on every connect?

picpgm pic24f

Hi, Zedman. MPLAB ask to update FW only when i change selected device(processor PIC16F, PIC18F, dsPIC).
Code on 4550 are FFs in range 0x46BC-0x7FFC, at 0x7FFE=0x8CA7.

Best Regards.

mplab icd2+expected val = 0xffff, val read = 0x0)

Ok guys thanks, after I initialize the 0xf0 and happends this:

000002: Control Transfer (UP), 16.04.2006 14:40:00.4702224 +0.0
12 01 00 01 FF FF FF 08 D8 04 01 80 10 00 00 00 ....ÿÿÿ.Ø..€....
00 01 ..
Setup Packet
80 06 00 01 00 00 12 00 €.......

Send 0x12 bytes to the device:
03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 ..

Get 0x8 bytes from the device:
03 00 00 00 00 01 00 00 ........

Send 0x12 bytes to the device:
04 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 ..


in the MPLAB:

Connecting to MPLAB ICD 2
ICD0021: Unable to connect with MPLAB ICD 2
MPLAB ICD 2 Ready

zedman do you refer to the 877 and 877a kind of?, because i only have 877a version, anyway, what do i have to do?, to program the 877 with the same bl010101.hex file? does this file has the psp routines?

potyo2-2006.12.07

Hi, narccizzo. On 877A you must upload atached file(bl010101 works only on 877).
For me work both on 877 and 877A. You must also connect RB3 on 4550 via transistor inverter to MCLR on 877.

icd2 pic32

THANKS PETARPAV!, So you already have this thing already working? if yes, really cool, this gives motivation for all of us..
Ok, let me continue with this.

Added after 4 minutes:

so i'm supposed that the crystal of the 877 keeps on 20MHz, right?

switching regulator used mplab icd 2

Hi, narccizzo. Yes both 4550 and 877 have 20MHz crystal.

Best Regards.

icd0161 16f84

Hi, petarpav, one more thing, who controls the E0, E1 and E2 877 signals?
is like zedman sais?
RB4 -> RE2 (~CS)
RE1 -> RE0 (~RD)
RE0 -> RE1 (~WR)
??

winpicpr down

Yes, that's right. Streaming Parallel Port on 4550 is connected to Parallel Slave Port on 877.

Best Regards.

16f877 74hc125

hi petarpav, i've connected like above plus the portd<>portd and i get this thing: (check the log file).

and the MPLAB still says:

Connecting to MPLAB ICD 2
ICD0019: Communications: Failed to open port: (Windows::GetLastError() = 0x2, 'The system cannot find the file specified.
')
ICD0021: Unable to connect with MPLAB ICD 2
MPLAB ICD 2 Ready

thanks for your help .
narccizzo.

icd2 corrupt firmware

with your 877afw.hex of course..

Added after 4 hours 16 minutes:

ok, this is what i have:

4550 with the 0xf0 corrected and os bootloaded
877a with the 877afw.hex

and the connection between both
4550 877a
portd portd
rb3 mclr (via bjt inverter)
re1 re0
re0 re1
+5v +5v
gnd gnd
rb7_hi
ra4_lo

20 and 20 MHz

the MPLAB now sais:

Connecting to MPLAB ICD 2
ICDWarn0054: MPLAB IDE has lost communications with the MPLAB ICD 2. Would you like to attempt to reconnect?
Connecting to MPLAB ICD 2
ICD0021: Unable to connect with MPLAB ICD 2
MPLAB ICD 2 Ready

what's wrong with my prototype?

Added after 3 minutes:

and rb4 of the 4550 to the re2

18f rev=0x2

zedman, did find your problem with the 64 bytes @0x4E00?

Added after 25 minutes:

I'm still have the same problem

it's supposed that i have to get some response like:

Send 0x8 bytes to the device:
3C 30 38 34 44 45 30 3E <084DE0>
5B 30 38 34 44 45 30 5D [084DE0]

Send 0x8 bytes to the device:
3C 30 38 30 31 43 39 3E <0801C9>
5B 30 11 00 45 30 31 30 31 30 33 30 34 46 45 5D [0..E01010304FE]
5B 30 11 00 45 30 31 30 31 30 33 30 34 46 45 5D [0..E01010304FE]

Send 0x8 bytes to the device:
3C 30 38 30 37 43 46 3E <0807CF>
5B 11 00 30 41 30 37 30 35 33 44 5D [..0A07053D]

Send 0xa bytes to the device:
3C 30 41 32 41 38 42 35 45 3E <0A2A8B5E>
5B 11 00 30 38 32 41 44 42 5D [..082ADB]

Send 0xe bytes to the device:
3C 30 45 30 36 30 30 37 46 46 46 34 34 3E <0E06007FFF44>
5B 11 00 30 38 30 36 43 45 5D [..0806CE]

Send 0xa bytes to the device:
3C 30 41 30 35 30 30 33 36 3E <0A050036>
5B [..0805CD]

Send 0x8 bytes to the device:
3C 30 38 33 37 44 32 3E <0837D2>
5B [..0A37A04C]

3C 30 38 33 34 43 46 3E <0834CF>
5B [0..A348040]

Send 0x8 bytes to the device:
3C 30 38 33 35 44 30 3E <0835D0>
5B [0A359F58]

Send 0x8 bytes to the device:
3C 30 38 33 37 44 32 3E <0837D2>
5B [..0A37A04C]

3C 30 38 33 34 43 46 3E <0834CF>
5B [..0A348040]

without the dots .. (these comes from a rs232 icd2 with a usb-232 converter)
but like the above logs sais the MPLAB sends twice the firmware request command.

someone knows why?
thanks.. narccizzo.

Added after 5 minutes:

ok, guys hope you'll help me, I'm so tired, I'm gonna sleep because it's 03:30am in mexico right now (gtm-6).
see ya..

icdwarn0062

narccizzo,

where is RC0(4550) <- RB0(877)?

did not find the reason for the 64 bytes.

-----------------

peterpav,

did not mean the 877 OS, but the 4550 OS.bin file. If you connect to your prototype with MPLAB how long does it take? Longer than 2-3 seconds? Did you check it with USBMon?

18lf4550 device not recognized

Zedman, when I select connect in MPLAB it takes about 1sec to 1.5sec to MPLAB say ready.

Best
Regards

Added after 3 minutes:

Zedman,
Do you receive this error from MPLAB?
"Connecting to MPLAB ICD 2
ICD0019: Communications: Failed to open port: (Windows::GetLastError() = 0x2, 'The system cannot find the file specified.
')
ICD0021: Unable to connect with MPLAB ICD 2"