Project to replace CY7C64613 in the ICD2

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

Author

Message

commonly

Joined: 02 Jul 2007
Posts: 1

19 Jul 2007 6:28 Project to replace CY7C64613 in the ICD2

Hi to all,
I've successfully built my version of ICD2 clone based on PICS sch. and it works fine with my notebook Dell Inspiron running Winxp-sp2 and Mplab 7.60.
All ok, then? NOT, not all ok. The same ICD2 is not recognized by a desk PC running the same OS and same Mplab version: I plug and unplug many times but the PC d'nt recognize it: UNKNOWN USB PHERIFERAL! Crying or Very sad

Did someone has an idea?

Thanks

comm

foxabilo

Joined: 16 Jul 2007
Posts: 67
Helped: 12
Location: Derby, England

20 Jul 2007 9:04 Project to replace CY7C64613 in the ICD2

Just a couple of thoughts,

Firstly, Is the ICD2 going directly into the USB port on the motherboard of the PC? i.e has it got a USB port all to itself? The reason I ask is that the ICD2 requires currant to operate and if like me your on your 4th USB hub and millions of small devices taking there few mA's then when you plug the ICD2 into the hub you will draw to much current.

Secondly, you say both PC's have the same OS, is that true down to the Service pack level ? Does you PC perhaps have a VIA chipset and requires that you update your 4in1 drivers to get full USB functionality ? Has your laptop perhaps got only USB ports and so comes pre configured with all the latest bits where as your desktop is not fully up to date service pack and motherboard driver wise?

Thirdly, have you considered using a seperate USB pci card to connect the programmer to? Have you got a freind with a pc you can try it in ? maybe a local PC repair workshop can let you try it on some of their machines.

In my experience USB still has these hiccups now and again, somtimes a device works in one PC and not in another though usualy it is down to driver / service pack updates.

Google
AdSense
Google Adsense

20 Jul 2007 9:04 Ads

DraganM

Joined: 24 Dec 2006
Posts: 32
Helped: 1

21 Jul 2007 10:27 Re: Project to replace CY7C64613 in the ICD2

Mine experience are:
-Do not attached ICD2 until WINxp is up
-Do not disconnect ICD2 until MPLAB is on
-Do not disconnect ICD2 from USB until WINxp is on
-If any message for bad connection persist reboot WINxp with taking account upper mentioned notes.
-If message for bad connection still persist reprogram both PIC, delete and install ICD2 usb driver.

louis99

Joined: 24 Jul 2007
Posts: 5

25 Jul 2007 21:04 Re: Project to replace CY7C64613 in the ICD2

Quote:

Author Message
DraganM Posted: 21 Jul 2007 11:27 Post subject: Re: Project to replace CY7C64613 in the ICD2

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

Mine experience are:
-Do not attached ICD2 until WINxp is up
-Do not disconnect ICD2 until MPLAB is on
-Do not disconnect ICD2 from USB until WINxp is on
-If any message for bad connection persist reboot WINxp with taking account upper mentioned notes.
-If message for bad connection still persist reprogram both PIC, delete and install ICD2 usb driver.

Hello DraganM

I already put a post in the main Subject "Project to replace CY7C64613 in the ICD2"

I have the same problem and today again, I need to reprogram the 18F4550.

I've got a original ICD2 and it always works even if you plug or unplug the ICD2 with MPLAB open.

Did you see somewhere some informations how to solve the problem ?

Thanks.