Ive recently purchased an ICD2 off of ebay, not an official microchip
unit, a 3rd party one. I got it today, and went to install it using
the microchip pre-installer, and had no luck... I tried various things
and still nothing, so I formatted and re-installed windows to get a
fresh start.
Since then I installed all my drivers, MPlab, and the pre-installation
of the ICD2 drivers.
I plug the ICD2 into the USB cable with no target attached, the
windows "new hardware found" dialogue comes up, however is it is for
the ICD Firmware client, instead of the ICD2 firmware Loader, which
according to the installation instuctions, is supposed to come up
first.
After that finishes I open MPlab and it can see the ICD, it goes to
update the operating system on it, it does, but it replies "ivalid
target device id (expected=0x21, read=0x0)" Thats as far as that
goes...
If I unplug and re-plug in the ICD, it pops up a "found new hardware"
bubble again, but it changes to unknown device, and provides a nice
error message for that.
Device manager shows "unknown device" also, and MPlab gives a "Failed
to open communications: Non-existent port"
I dont know what to do here, ive tried un-installing and re-installing
the drivers with the cleaning utililty, and the pre-loader, and still
the same problem every time.
Cliffnotes: install ICD2, doesnt pop up all the driver install windows
it should, ICD doesnt work in MPlab, unplug-plug in again gives an
unknown device from then on.
On 2/8/07, Jonathan Hallameyer <spam_OUTjmhtauTakeThisOuTgmail.com> wrote:
>
>
> After that finishes I open MPlab and it can see the ICD, it goes to
> update the operating system on it, it does, but it replies "ivalid
> target device id (expected=0x21, read=0x0)" Thats as far as that
> goes...
If you got that far, then the ICD2 is working properly. That message refers
to a lack of PIC connected to the ICD2. You should connect it to a circuit
with a pic of the proper type and the error will go away.
I have the same problem for a few months ago. I noticed that the cable
RJ-11 of the ICD2 is connected with power of my target board when
Windows start. If I disconnect the ICD2 from the target and I restart
Windows -- all work well.
> Ive recently purchased an ICD2 off of ebay, not an official microchip
> unit, a 3rd party one. I got it today, and went to install it using
> the microchip pre-installer, and had no luck... I tried various things
> and still nothing, so I formatted and re-installed windows to get a
> fresh start.
>
> Since then I installed all my drivers, MPlab, and the pre-installation
> of the ICD2 drivers.
>
> I plug the ICD2 into the USB cable with no target attached, the
> windows "new hardware found" dialogue comes up, however is it is for
> the ICD Firmware client, instead of the ICD2 firmware Loader, which
> according to the installation instuctions, is supposed to come up
> first.
>
> After that finishes I open MPlab and it can see the ICD, it goes to
> update the operating system on it, it does, but it replies "ivalid
> target device id (expected=0x21, read=0x0)" Thats as far as that
> goes...
>
> If I unplug and re-plug in the ICD, it pops up a "found new hardware"
> bubble again, but it changes to unknown device, and provides a nice
> error message for that.
>
> Device manager shows "unknown device" also, and MPlab gives a "Failed
> to open communications: Non-existent port"
>
> I dont know what to do here, ive tried un-installing and re-installing
> the drivers with the cleaning utililty, and the pre-loader, and still
> the same problem every time.
>
>
> Cliffnotes: install ICD2, doesnt pop up all the driver install windows
> it should, ICD doesnt work in MPlab, unplug-plug in again gives an
> unknown device from then on.
>
> Thanks for any help,
> Jon
>
--
------------------------------------------------------------------------
Logo Sedatelec <http://www.sedatelec.com>
yes, I tried hooking it up with the programming sockets I ordered with
it, and I did get it to read/erase/program and verify a 16F877A
however, I cant disconnect the ICD2, and reconnect it and have it work
again without uninstalling and re-installing drivers.
Also, it fails the self-test the module VPP is too high, being
reported as 14.1v so I have contacted the seller.
What is the correct sequence for hooking up the ICD2 and launching MPLAB?
1.Connect ICD to target
2. Launch MPLAB
3. Plug in USB cable to ICD
Is that correct?
> On 2/8/07, Jonathan Hallameyer <.....jmhtauKILLspam.....gmail.com> wrote:
> >
> >
> > After that finishes I open MPlab and it can see the ICD, it goes to
> > update the operating system on it, it does, but it replies "ivalid
> > target device id (expected=0x21, read=0x0)" Thats as far as that
> > goes...
>
>
>
> If you got that far, then the ICD2 is working properly. That message refers
> to a lack of PIC connected to the ICD2. You should connect it to a circuit
> with a pic of the proper type and the error will go away.
On Thu, 2007-02-08 at 08:30 -0500, Jonathan Hallameyer wrote:
> yes, I tried hooking it up with the programming sockets I ordered with
> it, and I did get it to read/erase/program and verify a 16F877A
> however, I cant disconnect the ICD2, and reconnect it and have it work
> again without uninstalling and re-installing drivers.
>
> Also, it fails the self-test the module VPP is too high, being
> reported as 14.1v so I have contacted the seller.
>
> What is the correct sequence for hooking up the ICD2 and launching MPLAB?
>
> 1.Connect ICD to target
> 2. Launch MPLAB
> 3. Plug in USB cable to ICD
> Is that correct?
No. Always have the ICD connected to your PC before you start MPLAB. I'd
recommend you connect it to your unpowered target first, connect the
ICD2 to the PC, then power up your target. Then start MPLAB.
Are you using a powered target, or are you powering from the ICD2? If
you're using ICD2 power you must connect the power supply to the ICD2,
USB alone isn't enough to support ICD2 supplying power to targets.
On Thu, 2007-02-08 at 06:15 -0500, Jonathan Hallameyer wrote:
> Ive recently purchased an ICD2 off of ebay, not an official microchip
> unit, a 3rd party one. I got it today, and went to install it using
> the microchip pre-installer, and had no luck... I tried various things
> and still nothing, so I formatted and re-installed windows to get a
> fresh start.
>
> Since then I installed all my drivers, MPlab, and the pre-installation
> of the ICD2 drivers.
>
> I plug the ICD2 into the USB cable with no target attached, the
> windows "new hardware found" dialogue comes up, however is it is for
> the ICD Firmware client, instead of the ICD2 firmware Loader, which
> according to the installation instuctions, is supposed to come up
> first.
>
> After that finishes I open MPlab and it can see the ICD, it goes to
> update the operating system on it, it does, but it replies "ivalid
> target device id (expected=0x21, read=0x0)" Thats as far as that
> goes...
That's normal. You didn't have the ICD2 plugged into a PIC? If so it
will read device id of zero.
> If I unplug and re-plug in the ICD, it pops up a "found new hardware"
> bubble again, but it changes to unknown device, and provides a nice
> error message for that.
>
> Device manager shows "unknown device" also, and MPlab gives a "Failed
> to open communications: Non-existent port"
>
> I dont know what to do here, ive tried un-installing and re-installing
> the drivers with the cleaning utililty, and the pre-loader, and still
> the same problem every time.
Have you tried using it through the serial port instead?
> No. Always have the ICD connected to your PC before you start MPLAB. I'd
> recommend you connect it to your unpowered target first, connect the
> ICD2 to the PC, then power up your target. Then start MPLAB.
>
> Are you using a powered target, or are you powering from the ICD2? If
> you're using ICD2 power you must connect the power supply to the ICD2,
> USB alone isn't enough to support ICD2 supplying power to targets.
>
> TTYL
Ok, I'll try that, but this is a clone ICD2 without a power jack or
serial port. I'm only powering a PIC in a programming socket however.
The "target" is a board with a 6-pin header for connecting to the
ICD, and 3 ZIF sockets to put a PIC in. Would that still be too much
current? I would think that a couple mA that the pic would need during
programming/reading wouldnt be too much load...
>Have you tried using it through the serial port instead?
Like I said above, no serial port on the ICD, and also no serial port
on my PC (well, not on the back plate anyway...) which was why I
wasnt to worried about it.
The main issue now is it shows up as an unkown device every time I
plug it in unless its the first time after uninstalling the drivers
with the cleaning utility, restart, and pre-load the drivers again.
On Thu, 2007-02-08 at 09:32 -0500, Jonathan Hallameyer wrote:
> > No. Always have the ICD connected to your PC before you start MPLAB. I'd
> > recommend you connect it to your unpowered target first, connect the
> > ICD2 to the PC, then power up your target. Then start MPLAB.
> >
> > Are you using a powered target, or are you powering from the ICD2? If
> > you're using ICD2 power you must connect the power supply to the ICD2,
> > USB alone isn't enough to support ICD2 supplying power to targets.
> >
> > TTYL
>
> Ok, I'll try that, but this is a clone ICD2 without a power jack or
> serial port. I'm only powering a PIC in a programming socket however.
Too much. You can't power ANYTHING from the ICD2 if you're powering the
ICD2 from USB.
It will sometimes work, but it's speced NOT to work, so why bother
trying.
> The "target" is a board with a 6-pin header for connecting to the
> ICD, and 3 ZIF sockets to put a PIC in. Would that still be too much
> current? I would think that a couple mA that the pic would need during
> programming/reading wouldnt be too much load...
You are out of spec, therefore you are on your own. It's very clear in
the ICD2 documentation that if you use the "power from ICD2 feature" you
must supply the ICD2 with power other then USB.
> >Have you tried using it through the serial port instead?
> Like I said above, no serial port on the ICD, and also no serial port
> on my PC (well, not on the back plate anyway...) which was why I
> wasnt to worried about it.
>
> The main issue now is it shows up as an unkown device every time I
> plug it in unless its the first time after uninstalling the drivers
> with the cleaning utility, restart, and pre-load the drivers again.
Until you're running your ICD2 in spec, I'd say anything is possible and
I wouldn't start debugging the problem until you're running it in spec.
> On Thu, 2007-02-08 at 09:32 -0500, Jonathan Hallameyer wrote:
> > > No. Always have the ICD connected to your PC before you start MPLAB. I'd
> > > recommend you connect it to your unpowered target first, connect the
> > > ICD2 to the PC, then power up your target. Then start MPLAB.
> > >
> > > Are you using a powered target, or are you powering from the ICD2? If
> > > you're using ICD2 power you must connect the power supply to the ICD2,
> > > USB alone isn't enough to support ICD2 supplying power to targets.
> > >
> > > TTYL
> >
> > Ok, I'll try that, but this is a clone ICD2 without a power jack or
> > serial port. I'm only powering a PIC in a programming socket however.
>
> Too much. You can't power ANYTHING from the ICD2 if you're powering the
> ICD2 from USB.
>
> It will sometimes work, but it's speced NOT to work, so why bother
> trying.
>
> > The "target" is a board with a 6-pin header for connecting to the
> > ICD, and 3 ZIF sockets to put a PIC in. Would that still be too much
> > current? I would think that a couple mA that the pic would need during
> > programming/reading wouldnt be too much load...
>
> You are out of spec, therefore you are on your own. It's very clear in
> the ICD2 documentation that if you use the "power from ICD2 feature" you
> must supply the ICD2 with power other then USB.
>
> > >Have you tried using it through the serial port instead?
> > Like I said above, no serial port on the ICD, and also no serial port
> > on my PC (well, not on the back plate anyway...) which was why I
> > wasnt to worried about it.
> >
> > The main issue now is it shows up as an unkown device every time I
> > plug it in unless its the first time after uninstalling the drivers
> > with the cleaning utility, restart, and pre-load the drivers again.
>
> Until you're running your ICD2 in spec, I'd say anything is possible and
> I wouldn't start debugging the problem until you're running it in spec.
>
> TTYL
>
Cristóvão Dalla Costa wrote:
> On 2/8/07, Jonathan Hallameyer <jmhtauspam_OUTgmail.com> wrote:
>
>> After that finishes I open MPlab and it can see the ICD, it goes to
>> update the operating system on it, it does, but it replies "ivalid
>> target device id (expected=0x21, read=0x0)" Thats as far as that
>> goes...
>>
>
>
>
> If you got that far, then the ICD2 is working properly. That message refers
> to a lack of PIC connected to the ICD2. You should connect it to a circuit
> with a pic of the proper type and the error will go away.
>
If you purchased the CLONE from Hong Kong (Kenny Wong) be advised that
the very earliest version
of his IDC2 unit had the RJ11-6 wired reverse. Confirm this with a
scope. He may have accidentally sent
you an earlier version. That would give you the symptoms you describe.
Be advised that if you DID buy from Kenny, you will NOT be disappointed.
I have two of his and they
work wonderfully.
I'm pretty sure its an ICD2 unit... only one USB connector, and one
ICSP connector, but it has an 18F4550, and a 16F877A, and a boost
converter for getting the VPP. Similar to all the schematics for the
ICD2 ive seen, just minus the MAX232 and the serial circutry...
On 2/8/07, Peter van Hoof <@spam@pvhoofKILLspamyahoo.com> wrote:
> The way you discribe the outside world connections it sound like you have a
> pickit2 clone , not an ICD2. are you sure what you have?
>
> Peter van Hoof
>
> -
> I just got my ICD2 and seem to be experiencing a simmilar problem. The '
> exopected' value differs from yours. It's a kenny wong ICD2.
Try:
1. Reinsert the chip (that is, pull it out of the ZIF, and insert it again)
2. Make sure it's inserted correctly (pin 1 where it should)
3. In MPLAB, issue a "reset and connect to ICD" (toolbar, the rightmost button)
I ended up returning the ICD2 as the problem was more of a USB issue, it
would only let me connect to it after I re-installed the drivers, after
that it wouldnt even show up as an ICD when I plugged it in. I have an
olimex ICD2 on the way from sparkfun now, hopefully that will work better...
-Jon
>
> On 3/15/07, Sean Schouten <spamBeGonedev.seantechspamBeGonegmail.com> wrote:
>
> > I just got my ICD2 and seem to be experiencing a simmilar problem. The '
> > exopected' value differs from yours. It's a kenny wong ICD2.
>
> Try:
>
> 1. Reinsert the chip (that is, pull it out of the ZIF, and insert it
> again)
> 2. Make sure it's inserted correctly (pin 1 where it should)
> 3. In MPLAB, issue a "reset and connect to ICD" (toolbar, the rightmost
> button)
>
>
> --
> - Rikard.
Jonathan Hallameyer wrote:
> I ended up returning the ICD2 as the problem was more of a USB issue, it
> would only let me connect to it after I re-installed the drivers, after
> that it wouldnt even show up as an ICD when I plugged it in. I have an
> olimex ICD2 on the way from sparkfun now, hopefully that will work better...
> -Jon
>
>
I'm amazed, I have 2 kenny wongs, and they work perfectly...
Well, isnt the install process critical for the 'real' ICD2 to work orderly?
I am thinking that something went wrong installing it. I tried to install it
on my laptop and haven't quite gotten around to trying it on my desktop
-yet-. Did you follow the MPLAB installation procedures for ICD2? I did. I
can't think of a reason for the ICD clone not to work, other than it
possibly some firmware problem?
Sean Schouten wrote:
> On 3/18/07, Bob Axtell <RemoveMEengineerTakeThisOuTneomailbox.com> wrote:
>
>> I'm amazed, I have 2 kenny wongs, and they work perfectly...
>>
>> --Bob
>>
>>
>>
>
> Well, isnt the install process critical for the 'real' ICD2 to work orderly?
> I am thinking that something went wrong installing it. I tried to install it
> on my laptop and haven't quite gotten around to trying it on my desktop
> -yet-. Did you follow the MPLAB installation procedures for ICD2? I did. I
> can't think of a reason for the ICD clone not to work, other than it
> possibly some firmware problem?
>
> Sean.
>
Well there is more to this than meets the eye.
I was never able to get my two "real" ICD2's to work reliably until
MPLAB 7.4 came along. Kenny's units
worked perfectly thereafter as well.
One difference with Kenny Wong's ICD2 is that it uses non-Cypress USB
chips. In fact, it uses Microchip
USB chips.
If you'd like to, send a KW ICD2 and I'll check it against the ones I
have. Communicate offline for an address,
etc.
>
> Jonathan Hallameyer wrote:
> > I ended up returning the ICD2 as the problem was more of a USB issue, it
> > would only let me connect to it after I re-installed the drivers, after
> > that it wouldnt even show up as an ICD when I plugged it in. I have an
> > olimex ICD2 on the way from sparkfun now, hopefully that will work
> better...
> > -Jon
> >
> >
> I'm amazed, I have 2 kenny wongs, and they work perfectly...
>
> --Bob
>
You seem to possibly be suffering a similar problem though. Did you manage
to resolve it?
Bob,
If I have time this weekend, I will have a closer look at my K.W. board and
check out the installation process in detail on my desktop PC. I might just
take you up on your kind and thoughtfull offer, if I don't manage to get it
to function as desired.
it uses an 18F4550 for the USB interface, and according to the seller it
only works with Intel chipsets, however it didnt even work with my Centrino
chipset laptop. I ended up sending it back, and ordering a olimex ICD2 from
sparkfun, which uses the cypress USB chip I believe.
-jon
>
> Its a pretty PCB...first time to see this one. What USB chip does it use?
>
> --Bob
>
> Jonathan Hallameyer wrote:
> > I never said my ICD was a kenny wong ICD, Sean had the kenny wong ICD.
> My
> > ICD unit was one of these.
> >
> cgi.ebay.com/MPLAB-ICD2-ICD-2-COMPATIBLE-DEBUGGER-PROGRAMMER-PIC-USB_W0QQitemZ180094758961QQcategoryZ4661QQcmdZViewItem
> >
> >
>
I got my Olimex ICD2 unit in, un-installing and reinstalling the drivers,
then plugging it in, the installation went as it was supposed to. The
firmware loader, and the firmware client installed seperately (only the
loader showed up with the original ICD unit) and all has been well.
I sucessfully programmed a 16F630. Though I need to find a new power supply
for the ICD2 the one I had which happened to fit was a 12v brick for
charging my jump starter pack... OCV was about 21v. Probably wouldnt have
used that if I checked the voltage before hand, but that 7805 sure did get
hot. I kept my thumb on the tab of the 7805, I figured it I can hold my
thumb on it, its not too hot. Off to find either a barrel connector or a
power brick that fits, and is better regulated...
Oh, for anyone having ICD2 difficulties, with a universal socket, check the
pinout of the universal sockets ICD header vs your programer. The ICSP cable
that came with the Olimex did not reverse the pins from one plug to the
other, so if you held the plugs side by side, they actually were in the same
order. Similar to the cable on this programmer... http://www.kanda.com/images/capr-pi_wb.jpg (random pic I found on google
images) The board was meant to be used with a ribbon cable style connector
where the pins would be in opposite order if you held them side by side...
Used the cable that came with the universal socket, and all was well.
gmail.com> wrote:
