Project to replace CY7C64613 in the ICD2

Goto page Previous 1, 2, 3, 4, 5 ... 60, 61, 62 Next

Jump to page:

EDAboard.com Forum Index -> Microcontrollers -> Project to replace CY7C64613 in the ICD2

Author

Message

Brem

Joined: 06 Apr 2006
Posts: 36

07 Apr 2006 10:48 18f4550 vid_0000&pid_0000

Hi!

I'm playing with it right now, and I'm a lot further, MPLAB seems to be happy now with my ICD:

Code:

MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0020: Invalid target device id (expected=0x93, read=0x58)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready

My test board doesn't have ICD hardware so i get a funny device id.

This is what I think I understand from the USB part of the protocol.

- control packets and data for ICD are both sent over EP1.
- each control packet needs to ACKed over EP1, just send 8 zero's over EP1.
- if data for ICD is going to be sent over EP1, it will be announced by a control packet. This is how you can keep the ICD data apart from control packets.
- control packets are 18 bytes long, but only 4 bytes seem ever to contain data.
- if first byte = 0x01 it means "data incoming on EP1", 3rd byte contains length. Next pkt rcvd on EP1 is data for ICD.
- if first byte = 0x00 it means "request data over EP2", 3rd byte length. ICD data should now be sent over EP2, followed by an ACK (8 zero's) over EP1.
- if first byte = 0x02, I just ACK it. Dont know what it means, maybe some status request or so.
- I didn't see any other control packets.

Quote:

, MPLAB wont send me ANY more data,

Isn't it waiting for data on EP2? You should be able to see that on a USB monitor?

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

07 Apr 2006 11:29 icd2w2k.inf 2000

Brem please can you send me your sources? (my mail is in my profile) I know Iam asking too much, but iam going insane becauseof this, I tried to send over EP2 too, but nothing happens.
Iam hungry for analysing the protocol as you do but sucking with this silly problem...

thanks in advance!

Added after 18 minutes:

I am @work now i'll be home in 5 hours and will work on it.

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

07 Apr 2006 11:57 icd2 clone nick7

hmm, thats strange. I can see my profile and it has my mail. But I GOT it. and don't worry I hate to deal with multiple c files too.
THANKS!

Added after 15 minutes:

at the first sight I initialize only EP1 for IN/OUT and EP2 for OUT (only), you initialize 7 IN/OUT EPs. Cool

-------

Albert here are the logs.

Sorry, but you need login in to view this attachment

rkodaira

Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil

07 Apr 2006 12:11 tps6734 problems

More info I checked inside the MPLAB-IDE and in the Windows system information:

Mplab ICD2 Version 07.20.09.00
Firmware: ICD2
Firmware Type: 18F_EGG
Firmware Version: 01.02.05.00
Bootloader Version: 01.01.01.00

Drivers: ICD2w98.Sys and MCDRV48F.DLL

I did the USB dumping when the MPLAP communicates with the ICD2 clone. Here is the dump:

===================================================
Bus Hound 5.04 capture on Windows 98 SE. Complements of www.perisoft.net

Device - Device ID (followed by the endpoint for USB devices)
(9) Microchip MPLAB ICD 2 Firmware Client
Phase - Phase Type
IN Data in transfer
OUT Data out transfer
Data - Hex dump of the data transferred
Descr - Description of the phase
Cmd... - Position in the captured data

Device Phase Data Description Cmd.Phase.Ofs(rep)
------ ----- ------------------------ ---------------- ------------------
9.1 OUT 02 c1 00 00 00 00 00 00 ........ 1.1.0
9.1 IN 02 00 00 00 00 00 00 00 ........ 2.1.0
9.1 OUT 01 c2 01 00 00 00 00 00 ........ 3.1.0
9.1 OUT 5a Z 4.1.0
9.1 IN 01 00 00 00 00 00 00 00 ........ 5.1.0
9.1 OUT 00 c3 04 00 00 00 00 00 ........ 6.1.0
9.2 IN 01 01 01 03 .... 7.1.0
9.1 IN 00 00 00 00 00 00 00 00 ........ 8.1.0
9.1 OUT 02 c4 00 00 00 00 00 00 ........ 9.1.0
9.1 IN 02 00 00 00 00 00 00 00 ........ 10.1.0
9.1 OUT 01 c5 01 00 00 00 00 00 ........ 11.1.0
9.1 OUT 55 U 12.1.0
9.1 IN 01 00 00 00 00 00 00 00 ........ 13.1.0
9.1 OUT 00 c6 01 00 00 00 00 00 ........ 14.1.0
9.2 IN 75 u 15.1.0
9.1 IN 00 00 00 00 00 00 00 00 ........ 16.1.0
9.1 OUT 01 c7 08 00 00 00 00 00 ........ 17.1.0
9.1 OUT 3c 30 38 30 31 43 39 3e <0801C9> 18.1.0
9.1 IN 01 00 00 00 00 00 00 00 ........ 19.1.0
9.1 OUT 00 c8 0e 00 00 00 00 00 ........ 20.1.0
9.2 IN 5b 30 45 30 31 30 31 30 [0E01010 21.1.0
9.1 IN 00 00 00 00 00 00 00 00 ........ 22.1.0
9.1 OUT 01 c9 08 00 00 00 00 00 ........ 23.1.0
9.1 OUT 3c 30 38 30 37 43 46 3e <0807CF> 24.1.0
9.1 IN 01 00 00 00 00 00 00 00 ........ 25.1.0
9.1 OUT 00 ca 0a 00 00 00 00 00 ........ 26.1.0
9.2 IN 5b 30 41 30 37 30 35 33 [0A07053 27.1.0
9.1 IN 00 00 00 00 00 00 00 00 ........ 28.1.0
9.1 OUT 01 cb 0a 00 00 00 00 00 ........ 29.1.0
9.1 OUT 3c 30 41 32 41 38 42 35 <0A2A8B5 30.1.0
9.1 IN 01 00 00 00 00 00 00 00 ........ 31.1.0
9.1 OUT 00 cc 08 00 00 00 00 00 ........ 32.1.0

Google
AdSense
Google Adsense

07 Apr 2006 12:11 Ads

albert22

Joined: 20 Jul 2004
Posts: 95
Helped: 3

08 Apr 2006 4:45 target halted mplab

Zedman, the logs in logs.zip contain no data. Just time stamp and number of bytes transfered. Anyway I have something to start with the logs and info posted by Brem.

Today I got my 4550. Going to build the board asap to join the fun.

VoltageDrop

Joined: 07 Apr 2006
Posts: 15

08 Apr 2006 8:13 firmware load cy7c64613

Awesome! I've been looking for a true USB ICD2 for awhile now and this looks to be very close to a working prototype! Very Happy

I don't know much about debugging USB comm but if you guys get the software figured out I could help with the layout and remaining analog circuitry. We use real ICD2's at work and we blow them up every now and again so it'd be nice to build some cheap ones that we don't have to worry about. Let me know if there's anything I can do to help out Twisted Evil

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

08 Apr 2006 16:15 usb programmer use 74ls125

Sorry Albert, my fault!

sending html versions.

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

Brem,

do you have any idea if I have to transfer more than 64 bytes why it hangs after 4 or 5 transmissions? PIC just waits for UOWN to get cleared. I debugged the PC side, it wants > 10000 bytes in 64 byte blocks continously, but usually after the 4th packet sent in the next ReadData call hangs.

doing this in a cycle>

Code:

for (a=0; a<64; a++) { icd2_data_tx[a]=0xFF; }
ICD2_DATA_BD_IN.Cnt = 64;
mUSBBufferReady(ICD2_DATA_BD_IN);
LED=1; while(mDataTXBusy() == 1); LED=0;

Sorry, but you need login in to view this attachment

Brem

Joined: 06 Apr 2006
Posts: 36

08 Apr 2006 18:59 pic icd clone india

Yes indeed, should be something like: LED=0; while(...) USBTasks(); LED=1;

Quote:

...if I have to transfer more than 64 bytes why it hangs ...

This suggests you are almost there! As far as I know you only need to send >64 bytes when the ICD is reading or verifying data/program memory on the target device.
Thanks for the logs, seems like sending 8 zero's is not the correct way to ACK a control packet.

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

08 Apr 2006 23:24 rj11 icd2 target device pinout

Now Iam here:

Code:

ICDWarn0059: About to re-program ICD2 USB Boot firmware code. Please do NOT disconnect the ICD2 or interrupt this operation!

It stuck with receiving the code to burn, it should come out from EP2 OUT, but it wont. The PC hangs in the MPLABWriteData call. Seems that the PIC cannot receive or waiting on wrong EP (now trying the others).

Added after 2 hours 20 minutes:

Ok guys here is the thing! Cool

After 2 weeks of debug:

The 2 bins CAN be burned into a 4550. And it (will) work. Actually now Iam tired, burned them in but it fails USB enumeration yet, but the code is looks OK in MPLAB and can be debugged. I think it looks for some hw thing before it let itself run further.

There is no config data in the hex file, I used the config I used with my USB project cloned from the Mchip Boot fw or the CDC example. Actually it's not exactly defined. Maybe Rkodaira would help us out with this issue. (If his 4550 is protected the config can be read? It's too late here to check the ds...)

Last edited by Zedman on 10 Apr 2006 12:28; edited 1 time in total

rkodaira

Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil

08 Apr 2006 23:44 unable to communicate with icd

Hi Zedman !

Great progress ! About your request: I am still in trouble to read the 4550 contents because i don´t have another programmer able to read it. Anyway, the crystal is 20MHz but i was reading the datasheet and for USB operation, the PIC must run at 48MHz. So I think there is a configuration to divide the 20MHz signal and rebuild to 48 MHz clock (PLL ??) to PIC main clock. I don´t think the configuration addresses are locked but for now i can´t read it.

Added after 3 minutes:

One curiosity: where do you come from or where are all of you located ? Just to know because the local time (fuses) are different and there are some delays in reading and answering the messages. I am located in Sao Paulo - Brasil (GMT - 3)

Last edited by rkodaira on 10 Apr 2006 14:12; edited 1 time in total

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

09 Apr 2006 10:15 dspic icd2 icd0200

Hey Rkodaira,

look here, this programmer supports 4550:
hxxp://www.melabs.com/downloads/meProg410_setup.exe

It can be used with the traditional EPIC programmer, you can find the schematics on edaboard. If you want to build one.

I set the config up to MCU run @20MHz from OSC1/2, the USB uses clock from the 96MHz PLL/2. CPU divide 5. HSPPL and USB-HS.

According the timeshift I am in Hungary in middle Europe. It's GMT+1 i think. Smile

Kripton2035

Joined: 19 Jul 2001
Posts: 587
Helped: 20
Location: Earth

09 Apr 2006 11:31 18f4550

rkodaira wrote:

Hi Zedman !
One curiosity: where do you come from or where are all of you located ? Just to know because the local time (fuses) are different and there are some delays in reading and answering the messages. I am located at Sao Paulo - Brasil (GMT - 3)

I'm in france so GMT+1 with daylight saving time actually..so must be GMT+2

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

09 Apr 2006 12:16 picburner usb germany

Yes, Krip you are right, it's GMT+2.

Added after 2 minutes:

Rkodaira, would you please check what do you have on these ports:

PORTC.1
PORTC.2
PORTA.0
PORTA.4

PORTD

PORTE.0
PORTE.1
PORTE.3

thanks

fms

Joined: 13 Mar 2005
Posts: 46
Helped: 2

09 Apr 2006 14:59 lt1172 eagle

hi, i find this very interesting. but is there a complete circuit for this project? apart from that, what are the differences between this and the ori ICD2 (in terms of performances)? what about the speed? are they the same?

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

09 Apr 2006 20:45 chipid pic16f887

4550 is the official Mchip replacement for the obsolete cypress chip in the earlier ICD2s. They provided bootloader and OS for the new chip with MPLAB.
This project is started to figure out how the new ICD2 works, how to download and use the given FW and to discover the circuit changes.
There's no impact on speed/performance (at least I can't see any differences yet), just the replacement of the USB bridge chip.

You are also welcome to help us.

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

10 Apr 2006 9:29 pic32 starter kit hex files

Brem, Albert?

Any results? Progress?

rkodaira

Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil

10 Apr 2006 12:39 pic pl2303 pic 16f877

Zedman, your request:

PORTC.1 pin 16 is not connected
PORTC.2 pin 17 is connected to a led+resistor to indicate USB connection
PORTA.0 pin 2 is not connected
PORTA.4 pin 6 is not connected

PORTD all 8 ports (SPP) are connected to the correspondent pins of 16F877 (PSP)

PORTE.0 pin 8 (CK1SPP) is connected to pin 9 of 877 (WR)
PORTE.1 pin 9 (CK2SPP) is connected to pin 8 of 877 (RD)
PORTE.3 pin 1 (MCLR) is connected to a reset circuitry (resistors + mosfet)

PORTA.1 pin 3 is connected to Vdd via 10k resistor
[/b]

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

10 Apr 2006 13:20 classguid 18f4550

thanks!

Iam @work now for 3 more hours, but can't wait to get home to use your infos! Cool

Added after 49 seconds:

Just got your reply in time with no timeshift! Smile

Added after 21 minutes:

Rkodaira,

that pullup resistor on PORTA.1 makes me suspicious, maybe we are developing different versions...
Would you please check in BusHound:

Devices Tab/Properties(down the bottom)/Hardware ID: USB\VID_xxxx&PID_xxxx&SUBSYS_xxxxxxxx&REV_xx

thanks in advance!

rkodaira

Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil

10 Apr 2006 13:43 pickit2 4066

Zedman, you are lucky, i had noticed this information before and kept it.
Here it is:

USB\VID_04D8&PID_8001\5&3278073A&0&2

I got it not from the Bushound, but from another way, but i thought it could be useful some time. I don´t know if the numbers following the PID number are the SUBSYS and REV numbers (it should be).

Last edited by rkodaira on 11 Apr 2006 12:20; edited 1 time in total

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

10 Apr 2006 13:51 Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼ Ñ brener8

It seems revision number is different. I strongly think that you have a version like Brem developed -> a custom USB bridge. And it's may not be compatible with Mchip's 4550 fw updates. Anyway it works for you, and fast!
Thanks for the infos!

Brem

Joined: 06 Apr 2006
Posts: 36

10 Apr 2006 15:53 driver usb rs232 redfox

From reading the 877 firmware I know that it expects USB data via PORTD, and RS232 data is received over the 877 UART (MOVF RCREG, W). I dont know how it decides to use USB or RS232.

I understand your aim is to build an ICD with a 877, and a 4550 for the USB part, using the 4550 firmware provided by Microchip? Are you sure the new ICD will still contain a 877? Why would they have chosen a chip with such a high number of pins for such a simple task?

Oh and I'm from Amsterdam, the NetherLands (GMT+2)

Jay.slovak

Joined: 23 Mar 2006
Posts: 11

10 Apr 2006 16:37 pic18f4550 corrupt flash

I think they will use 16F877 for legacy purposes, so that they don't have to re-write all the firmwares, as 16F code is not compatible with 18F.

And they chose 18F4550 for it's SPP - streaming paralel port, which simplifies things a lot.

There is a small chance, that they will 'upgrade' PICkit2 into new ICD (ICD3 ???), as it's design is more advanced (good Vpp charge pump, variable target Vdd...) and cheaper to manufacture. It even contains 1Mbit of EEPROM space which is not used in current firmware...

PS: I am in Slovakia, so it's GMT+2 here (DST active).

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

10 Apr 2006 18:36 icd2 pic16f877 vpp too low

Jay is in the neighborhood Very Happy

Added after 1 minutes:

They are not using the SPP in the 4550 fw.

Jay.slovak

Joined: 23 Mar 2006
Posts: 11

10 Apr 2006 18:44 icd2 clone

Zedman wrote:

They are not using the SPP in the 4550 fw.

Hmm, that is pretty interesting, I thought they do. Then there is no reason for 4550, 18F2455 could do the work as well (cheaper & smaller).

PS: 'Neighbourhood' sounds funny, considering we are probably couple hundred kilometers appart Very Happy

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

10 Apr 2006 19:06 icdwarn0052 pic24

I think they've choosen 4550 for future things, that's why even the bootloader is upgradeable too.

Yes you are in the hood, Rkodaira is a couple of thousand kms away! Very Happy

rkodaira

Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil

10 Apr 2006 19:44 mc-34063 driver installer.exe

He he, I think I am the only in this side of the planet writing to this thread. But it is understandable because EDABOARD is an European forum. Someone noticed that there are few people from US participating in EDABOARD. In my country very few understand and/or write in english language, so the number of brazilians is low.
I am far in distance and in fuse time (around 5 to 6 hours delayed from you).

Returning to the subject, i was studying the configuration words used in the PICKIT2 (18F2550) and for the configurations fuses about the USB clock settings I think it should be the same for the ICD2 clone (18F4550).

The hex file is (available inside the zipped source code file in the Microchip site):

:020000040030CA
:0E000000240E381E000181000FC00E800F403C
:00000001FF

What turns to:

CONFIG1: 0E24
CONFIG2: 1E38
CONFIG3: 0100
CONFIG4: 0081
CONFIG5: C00F
CONFIG6: B0E8
CONFIG7: 400F

This configures the PIC with:
CONFIG1L:
USB clock source comes from the 96MHz PLL divided by 2
96MHz divided by 2 to derive the system clock
Prescaler divide by 5 (20MHz oscillator input)

CONFIG1H:
Oscillator type HSPLL

CONFIG2L:
USB voltage regulator enabled
Brown out reset disabled

CONFIG2H:
WDT disabled

CONFIG3L:
MCLR disabled

CONFIG4H:
Debug and extended instruction set and LVP disabled

CONFIG5L and so on:
Code protection for all blocks are not protected
But blocks 0 1 and 2 are write protected (block3 is not)

Of course it is not the same for the 18F4550 used in the ICD2, but for USB settings this is a clue.
If the PICKIT2 would be upgraded to an ICD2 (or 3) some day, this is much more easy to build and cheaper too. As I said, i tried to build one, but I could not communicate it with the PC.
Last year (september round) I was one of the winners of the Microchip Contest and the prize was the PICKIT2. Unfortunately (I don´t know why) I have never received my prize .... Crying or Very sad

fms

Joined: 13 Mar 2005
Posts: 46
Helped: 2

11 Apr 2006 7:18 icd0019:

hi, actually i've been planning to make a my own icd2 that can operate almost the same way as the ori. but there are many version out there. and some are clamed to be too slow. apart from that, i tot the cypress chip could easily be substituted with a ftdi chip or even a ti tusb3410 chip.

is the circuit in use is based on lothar slotz project? someone claims that it is much slower than the actual ICD2. Furthermore, they claims that converting a RS232 communication to a usb connection wont increase the speed as well. My question is, isn't it that cypress, ftdi and ti chips are actually doing the same thing? if it does, would the speed decreases when we substitute the usb chips to other manufacturers?

why can't the 4550 chip be programmed in a way to just convert the usb data into the simple RS232 signals before connecting it to the rest of the circuit. this is exactly what the rest of the chips are doing isn't it? if it's that case, can't PIC18F2455/2550 be used. less pins are used.

Pls correct me if im wrong. Just some uncertainty here.

Zedman

Joined: 13 Oct 2003
Posts: 312
Helped: 2
Location: Hungary

11 Apr 2006 9:03 jdm programmer for 30f

Think: 877 communicates serially on RS232 and if available parallely on PORTD. Even if you use PORTD than it should be faster than shifting out the data on the USART.
The Cypress chip is connected to PORTD and feeds the 877 parallely on it's PSP port. And it uses BULK type USB transfer which's speed is can be around 1.5 MByte(!)/sec. I think I won't reaches that high, but anyway it's a lot faster.
If you do it with an RS232-USB converter chip, the PC side (MPLAB) will see a SERIAL ICD2 and wont set it's speed higher than 56k even if it's driver can do more.

Added after 3 minutes:

Rkodaira is my faaaarest friend Smile

Rk, I used the same config as you sent except the Boot block protection.

narccizzo

Joined: 20 Jan 2006
Posts: 173
Helped: 4
Location: PATZCUARO,MICHOACAN,MEXICO

12 Apr 2006 2:49 pic32 pickit2

Hi every body!

good news, after some dissasembling time, i found something interesting in the boot.bin file, to make some tests i need to know the basic componentes that some of you have tried, and the last config word that you used!
thanks and see you soon..

Added after 1 hours 44 minutes:

zedman saids before that the bin files are correct, if that is true what's the real problem? is not enough to have the hex files and the schematic?

Added after 1 minutes:

because im getting confusing..

Brem

Joined: 06 Apr 2006
Posts: 36

12 Apr 2006 9:33 18f2x

Hi,

What did you find, Narcczizo? I've been looking at a dissassambled boot.bin too. I used the hex files from earlier in this thread. I find it strange that the reset-vector and isr-high vector are at 0x00C0 & 0x00C8 instead of 0x0000 an 0x0008. Is it the same at your side?

There is a lot recognizable stuff in the listing. I can find the mcc18 _startup, _do_cinit & main, and the whole USB frame wrok (USBCheckBusStatus, USBDriverService etc). The OS seems to start at 0x2800..

Zedman, where did you get stuck when you where debugging it?