| Author |
Message |
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
 30 Mar 2006 20:50 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
I did some research on cypress EZ-USB thing, now I know why there are 2 .sys files.
Had no luck with the hex files, cannot create easily understandable asm from them.
Therefore I don't know what type (class) of usb device is the ICD2. And without that info I cant even do byte/byte debug because the device driver wont let me open itself because it thinks the icd2 is not attached because it sends wrong configuration descriptors...
(Iam trying with the Comm Class sample by microchip, anyway it's working fine emulating a COM4 port, but that not our goal)
rkodeira please if u can do a connect with this monitor program:
(or anyone else who has original ICD2 with the cypress chip)
h**p://www.hhdsoftware.com/Download/usbmon.exe
I would very appreciate it, it would help a lot!
Another question: does ICD2br have it's own usb driver? Because Cypress chip has 2 (1st loads it's fw, second is for the real communication).
Or it works with the original microchip driver?
Without infos, after a lot of google and dissasembling of device drivers/dll-s I stuck a little bit, and I think we have to write a new device driver too. (and that will be a long journey)
|
|
| Back to top |
|
 |
Rbn
Joined: 14 Feb 2006
Posts: 2
|
| 30 Mar 2006 21:09 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
I don't know if you are refearing to this but, I have read that ICD2 can operate at 2 Mbps speed.
Cheer up! It's a good project!
|
|
| Back to top |
|
|
rkodaira
Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil
|
| 30 Mar 2006 21:12 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
I´m sorry I´m not going to have time to do the USB monitoring in the next days, because I´m not going to stay at home (I use PICs at home lab). I could not even do the download of the monitor.
Answering the question about the driver: I ´m not sure, but it should use the driver used by the original Microchip ICD2, because no driver is provided with my board.
Read the text regarding USB interface found in a document prepared by a member of Edaboard (jonas Meyer) about the Cypress chip:
=================================================
3.2 USB ID’s
To get the programmer working on the USB port the EEPROM U13 connected to
the CY7C64613 has to be programmed with the correct VID/PID/DRev. It is possible
to either use a standard EEPROM programmer or the development tools provided
by Cypress ( 60MB download). The correct EEPROM data is stored in
the ICD2_EEPROM.HEX (also included in ICD2_FW.zip). The first 9 bytes of the EEPROM
have to contain the values 0xb4 0xd8 0x04 0x00 0x80 0x01 0x00 0x06 0x00
(VID/PID/DRev).
If using the Cypress development tools, EZ-USB FX has to be installed first. After
connecting ICD2 to the USB port, the host recognizes the CY7C64613 (with empty
EEPROM) as a Cypress device. Now Cypress drivers have to be installed. Then
the Cypress USB control panel can be started to program the EEPROM with the
corresponding values.
When the EEPROM is programmed correctly ICD2 will be recognized by the OS as
a Microchip device. Now the Microchip USB drivers have to be installed. After starting
MPLAB it first downloads the CY7C64613 firmware. If the download was successful,
MPLAB connects to ICD2 and downloads the appropriate PIC firmware. Now ICD2 is
ready to connect to the target board and download or debug your code.
3.3 USB Drivers
Microchip USB drivers seem to be kind of buggy since they provide a USB driver removal
tool MPUsbClean.exe. It is included in the MPLAB distribution. After installing
MPLAB it is located in the installation directory in /Utilities/MPUsbClean/.
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 30 Mar 2006 21:23 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
I knew that the cypress reads the VID/PID from an external chip.
I tried to set them, it's ok, but it's much more complex than just showing the correct numbers to the windows' driver.
If it recognizes the correct VID/PID it starts asking the chip for more info.
If someone captures a complete connect sequence with the USB Monitor program I mentoined before, than it will be easier to examine what should I put into those descriptors.
Someone please help us with that monitor thing, it's easy, just install the program, start it, and start MPLAB and connect to ICD2 (real or clone but USB). Save the log file and put it up to the forum. It would be good enough to start.
thanks in advance.
|
|
| Back to top |
|
|
Rbn
Joined: 14 Feb 2006
Posts: 2
|
| 30 Mar 2006 22:01 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
| I think I can help you with it this weekend. I have an original ICD2 in the lab, I'll try to have a break to download the program and monitor the usb port of the USB.
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 30 Mar 2006 22:37 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
zedman, here is the log !
made with the usbmon you want
on the icd2 clone made by silicium31
real usb clone with cypress cy64613 chip in it...
here is the log of the connection from mplab, and the session file.
good luck in decrypting that !!!
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 30 Mar 2006 22:54 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
rkodaira,
please what is the small ic 8 pins near the inductor ?
regards,
Added after 3 minutes:
i think the 18f4550 is here a cypress 64613 clone... they could have used a 18f2550 and the RB port as a psp port, may be it's easier to use the psp on the 4550?
Added after 12 minutes:
bonus log...
this is the log of the connection of mplab when you connect as a programmer to the icd2
the first one was a connection as a debugger.
good luck.
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 30 Mar 2006 23:04 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
and another bonus...
the debugger is connected, the target is programed,
I start the logger and made a step into with mplab
and stopped the logger just after that.
hope this helps ?
|
|
| Back to top |
|
|
albert22
Joined: 20 Jul 2004
Posts: 94
Helped: 3
|
| 31 Mar 2006 5:22 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
This thread is getting big. I thought Id have time to read the new msgs in a couple of minutes. But I dont have so much time now. Will read them carefully tomorrow.
The source C files that I got was the .sys driver propossed by Cypress. it can be donwloaded from their web as part of the EZ-USB kit. The source makes reference to a well known book that has been posted here at edaboard (I dont remember the exact title).Ill post the c here when I get back home.
This drivers handles the power up and initial load of the CY. It does a 8051reset, downloads a "loader" that is suppossed to be the routines to handle the external RAM (which we dont need). and then after another reset, the user "firmware" The later is linked to the .sys and contains the code for the CY in intel hex format.
It is important to determine if the Brazilian labs had cloned the real microchip ICD2 or they developed the clone emulating the USB interface.
If the brazilians developed the code it will surelly be protected into the chip with CPPon
If microchip developed the code I think it will not be protected because they seem to be using the same philosofy of a bootloader and an operating system. With the code protection on, the bootloader could not modify the internal program memory to upgrade the software of the 4450. Take into account that they can even easyly upgrade the code on the CY. As well as in the 877.
Added after 1 hours 59 minutes:
the link to the cypress soft is:
http://www.cypress.com/portal/server.pt?space=CommunityPage&control=SetCommunity&CommunityID=209&PageID=418&r_folder=Developer%20Kits&r_title=CY3671%20-%20EZ-USB%20FX%20Development%20Kit
I dont think that such a link will work so here is plan b
search for the name of the chip cy7c6413 at cypress and the scroll down to development kits.
Two zips are available. The one that is 60Megs contains an exe which installs everything including the sources and manuals.
I think that the driver is discussed or based on the book mantioned at "loader.c"
I dont understand very much of USB but it is not HID,
It is highly probable that microchip just did minor changes to this loader.c Including the brand name, If you see at the strings that the microchip .sys contains, you will find "anchor chips" or something like that. That was the firm that developed the processor cy7c6413 that was then purchased by cypress.
You see? This is not even Cypress stuff but older.
Thanks for the USB monitoring it is going to be very useful. Didnt have a real ICD so I had no way to get it.
Im still on my trip. Ill get a beer for the advances that the people made on this project right now.
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 31 Mar 2006 11:49 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Thanks Kripton for the files, i'll examine them asap.
Added after 16 minutes:
Kripton please unplug the ICD2 from the port start the monitor and after that connect it again, because the initial sequences are missing.
Anyway it's using bulk transfers! it's a new info!
Added after 2 hours 29 minutes:
Kripton,
all of the type/class descriptors of the endpoints in the USB device are sent when it's physically connected to the host, sorry I haven't wrote it before you started to monitor.
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 31 Mar 2006 11:52 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
zedman, ok I will do it at home tonight (within 10 hours from now...) the icd2 is at home and i'm at work for now.
Added after 1 minutes:
well, this usbmon is a nice piece of software.. do you know how long it works in demo mode ? can't find it anywhere..
|
|
| Back to top |
|
|
rkodaira
Joined: 08 Jun 2004
Posts: 332
Helped: 54
Location: Sao Paulo - Brasil
|
| 31 Mar 2006 13:09 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Answering to Krypton:
- The 8 DIP chip in the right side above the inductor is the switching regulator MIC2172 (Micrel - search in the Google for MIC2172, its datasheet is the first result) used in the boost converter.
Some comments about code protection: the 18F4550 can be code protected only in some blocks of the program memory, so the bootloader area may be protected and the downloadable code may be not.
I think the logo "Microchip Licensed" means that the manufacturer had the cooperation of Microchip, but the code remains secret. I don´t think they would sell a product with unprotected code and so easy to be copied. If this happened I could see a lot of clones of the clones here, and this have not happened (until now).
About the drivers: I forgot all steps I did when I installed the clone but reading the manual I could remember that when it asked the drivers, we should use the USB drivers located in the MPLAB/IDE/ICD2 directory. So, for sure it uses the Microchip USB drivers.
|
|
| Back to top |
|
|
petarpav
Joined: 25 Mar 2002
Posts: 557
Helped: 8
|
| 31 Mar 2006 14:49 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Hi, Kripton2035. Look here:
"Evaluation and Registration
This is not free software. Subject to the terms below, you are hereby licensed to use this software for evaluation purposes without charge for a period of 30 days (or 100 sessions). If you use this software after the 30 day evaluation period a registration fee is required. "
Best Regards.
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 31 Mar 2006 14:51 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Kripton, i dunno long it works, but i'll fix it if it wont do what i want 
Waiting for the other dumps like hell 
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 31 Mar 2006 18:17 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
with a little advance... i'm back home
play with this !!!
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 31 Mar 2006 18:56 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Thanks Kripton!
I started to examine it!
Would you please upload the device window (just a screenshot) when icd2 is connected to the port?
(I attached the window I want, please expand all parts of the tree of icd2 device)
thanks in avdvance
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 31 Mar 2006 19:11 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
You can use the copy subtree function and save it as text file, it's the second icon from the left.
thanks.
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 31 Mar 2006 19:22 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
I can get you a cy7c64613 for some 25 euros + shipping if you want...
I'm doing it right now (the device window..)
Added after 4 minutes:
Port2: Microchip MPLAB ICD 2 Firmware Client
Hub Power: Self Power
Number of Ports: 2
Power switching: None
Compound device: No
Over-current Protection: None (Bus Power Only)
Device Descriptor
USB Version: 1.0
Device Class: (255) Vendor Specific
Device Subclass: 255
Device Protocol: 255
Max Packet Size: 0x40 (64) bytes
Vendor: 0x04d8 ()
Product ID: 0x8001
Product Version: 0x0003
Manufacturer: 0
Product: 0
SerialNumber: 0
Number of Configurations: 1
Connection Status: Device Connected
Current Configuration: 1
Device Bus Speed: Full
Device Address: 0x02
Number of Open Pipes: 14
Configuration Descriptor (1)
Total Length: 116 bytes
Number of Interfaces: 1
Configuration Value: 1
Configuration: 0
Attributes: 0x80
Bus Powered
Max Power: 0x4b (150 Ma)
Interface Descriptor (0)
Interface Number: 0
Alternate Setting: 0x00
Number of Endpoints: 0x0e
Interface Class: (255) Vendor Specific
Interface Subclass: 255
Interface Protocol: 255
Interface: 0
Endpoint Descriptor (Addr: 0x01)
Endpoint Address: 0x01, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x02)
Endpoint Address: 0x02, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x03)
Endpoint Address: 0x03, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x04)
Endpoint Address: 0x04, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x05)
Endpoint Address: 0x05, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x06)
Endpoint Address: 0x06, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x07)
Endpoint Address: 0x07, Output
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x81)
Endpoint Address: 0x81, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x82)
Endpoint Address: 0x82, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x83)
Endpoint Address: 0x83, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x84)
Endpoint Address: 0x84, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x85)
Endpoint Address: 0x85, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x86)
Endpoint Address: 0x86, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
Endpoint Descriptor (Addr: 0x87)
Endpoint Address: 0x87, Input
Transfer Type: Bulk
Max Packet Size: 0x0040 (64) bytes
Interval: 0x01
|
|
| Back to top |
|
|
Kripton2035
Joined: 19 Jul 2001
Posts: 424
Helped: 8
Location: Earth
|
| 31 Mar 2006 21:07 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
| Zedman wrote: |
thanks, I ordered samples from cypress some weeks ago, but hey this is a challenge isn't it? |
I asked them some weeks ago and they answered me one week later this part is obsolete and so cnnot give sample of it !
too easy.. 
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 31 Mar 2006 21:56 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
That's sad.
At the moment: device fails Enumeration...
Damn I hate to deal with 10000 .c/.h files...
mrrr.
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 01 Apr 2006 20:08 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Now it identifies itself as ICD2 VID/PID but when I start to install the mchip drivers it freezes... Think it waits for data from and endpoint. More debugging and more time and more patience needed.
Also if anybody else has any idea how can I recover the 2 Cypress HEXs to Assembly language, it would help a lot to discover what should the 4550 do in place of the Cy.
The text Kripton sent shows ICD2 uses 7(!) IN/OUT endpoints in one interface.
1 device / 1 interface / 7 endpoints.
I dunno if it uses all or not, i'll check in the log files, but it seems it's more complex than just a bridge between the USB and the PSP port.
|
|
| Back to top |
|
|
albert22
Joined: 20 Jul 2004
Posts: 94
Helped: 3
|
| 01 Apr 2006 22:51 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Zedman. Are you developing with a 4450 ? If thats the case. Did you try to program the 4450 with the .bin (boot)included in the 7.30 mplab ?
I think it is worth a try to see if it is recognized by the microchip USB driver. That is the first thing I want to test when I get the pic on my return.
Added after 1 minutes:
ICD2_4550_BOOT_0180.BIN seems to be a very good candidate.
|
|
| Back to top |
|
|
predrage
Joined: 23 Jul 2005
Posts: 132
Helped: 5
|
| 02 Apr 2006 10:18 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
| I will try to program 4550 with ICD2_4550_BOOT_0180.BIN later today and i will let you know about results. I didn't know that pic can be programed with bin files. I thought that hex file is the only one possible. Oscilator is 20MHz? Am I right?
|
|
| Back to top |
|
|
Make_Pic
Joined: 13 Apr 2002
Posts: 79
Helped: 1
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 02 Apr 2006 16:27 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
albert, Iam developing with 4550.
albert, predrage I tried to disassemble them, (first bin2hex than -> mplab) but they are look like scrambled code, or the bin2hex was not successful I dunno.
Good news:
Last night I was able to install the Mchip drivers for my 4550, it recognizes it as an ICD2, now MPLAB tries to connect it, but fails since I do not return any data yet, because have some probs with tx routine.
Studied some on the protocol of the ICD2 and it's seems not so hard.
I'll work on it tonight too. (my wife doesn't like this project tough...)
Added after 6 minutes:
Make_Pic,
I got IDA, and tried it on the hex files, but it has only generic 8051 register names/symbol table.
thanks anyway!
|
|
| Back to top |
|
|
tde040141
Joined: 02 Apr 2006
Posts: 1
|
| 02 Apr 2006 18:37 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Hello I'm very interested with this thing and I found out that the OS downloaded is from ICD05010304.hex not from: ICD2_4550_BOOT_0180.BIN and ICD2_4550_OS_0100.BIN
the OS-file is for all the newest PIC18 ex. PIC18F8722,PIC18F4550
so you should test the bin files.
the clock input shall after the datasheet for PIC18f4550 so the USB peripheral gives 48Mhz
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 02 Apr 2006 18:49 Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Going insane.
the UOWN bit of the IN endpoint1 wont get cleared. This means the SIE is using the shared RAM of this EP. But why? I did not set the ownership to SIE. Mrrrr. 
Added after 8 minutes:
tde040141
it's true not the binfiles downloaded into the 877 while programming the new chip types.
I don't give much chance downloading the bin files into a 4550 (altough it can be good), at least the *boot image should look as a working code in a dissassembler. I said it can be that's really a working thing for a new 4550 based ICD2, but how to download them into an EMPTY 4550?
|
|
| Back to top |
|
|
predrage
Joined: 23 Jul 2005
Posts: 132
Helped: 5
|
| 02 Apr 2006 23:14 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
My friends i didn't succeed in programming ICD2_4550_BOOT_0180.BIN into 4550. I'v
tried to open bin file with winpic 800 software but it failed. I tryed to open it with option "all files" in "file types" because there is no direct support for bin files. ICprog have that support (to open bin files) but can't program 4550. In fact there is no 4550 in device list. What should i do next? Any suggestions? I'm just a beginner but I have good will to help.
Sorry about my bad english.
|
|
| Back to top |
|
|
Zedman
Joined: 13 Oct 2003
Posts: 281
Helped: 2
|
| 02 Apr 2006 23:24 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
Actually it receives the first packet from MPLAB, I set the appropriate answer for it into my buffer, and set TX state to BUSY, indicating that I put someting into the tx buffer.
TXService routine checks the shared RAM buffer's ownership and if it's owned by the MCU then copies the data from my buff to shared buff and sets the owner bit to SIE, signing that it should transmit it.
And here I stuck.
The SIE owns the buffer forever. I checked the error handler routine, not running into error. I read in other forums, that the transmission may not took place and SIE waits. I know that USB is a master / slave thing, host initiates IN transmissions too, so there must be an IN token sent by host to the device indicating it wants n bytes.
here is Kripton's log:
| Code: |
000001: Bulk or Interrupt Transfer (UP), 30.03.2006 23:34:55.2028448 +37.6942016
Pipe Handle: 0x8260b020 (Endpoint Address: 0x1)
Send 0x12 bytes to the device:
02 C1 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00
.Á..............
..
000002: Bulk or Interrupt Transfer (UP), 30.03.2006 23:34:55.2328880 +0.0300432
Pipe Handle: 0x8260b0e4 (Endpoint Address: 0x81)
Get 0x8 bytes from the device:
C1 00 00 00 00 00 00 00
Á.......
|
Endpoint 0x01 is endpoint 1's OUT (pc->device) pipe
Endpoint 0x81 is endpoint 1's IN (device->pc) pipe
it shows no IN token sent by the host, just a Get 0x8 byte and there it is.
But my 4550 waits, and MPLAB sends this sequence 2 times, and after that it says something is wrong. (actually it is)
Any ideas?
Any USB gurus?
Ahh, iam tired, gone to take care of the wife...
Added after 7 minutes:
predrage,
the only way is to do a bin->hex conversion and the burn the hex files with mplab or any other programmer. There are converters available, search google for bin2hex.exe. If you load the hex into MPLAB you will see that there's no configuration data in it.
|
|
| Back to top |
|
|
albert22
Joined: 20 Jul 2004
Posts: 94
Helped: 3
|
| 02 Apr 2006 23:40 Re: Project to replace CY7C64613 in the ICD2 |
|
|
|
|
| Quote: |
| My friends i didn't succeed in programming ICD2_4550_BOOT_0180.BIN into 4550. |
predrage & zedman bin2hex should have worked. Another posibility is loading the bin into the ICPROG. Check the contents (strings should be readable) save buffer in intel hex format. Then use the .hex to program the 4550 with mplab.
There are at least two versions of the intel hex file format. Word address and byte address. Mplab may be trying to read the wrong version and the 4550 will not be correctly programmed. I suggest to check the versions that mplab accepts and what can be generated with bin2hex and ICPROG.
Zedman good work! Did you do something with the initial firmware downloading of the CY ? It is supposed to come up in the USB using the (xxxl.sys loader) download its code and then use the icd2 driver (xxx.sys) to communicate with mplab. May be this process generates the different endpoints that you are seeing.
|
|
| Back to top |
|
|
