Searching \ for '[PIC]:Still problems with ICD2 installation' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'Still problems with ICD2 installation'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]:Still problems with ICD2 installation'
2005\07\31@171130 by John Nall

picon face
Well, I hate to keep whining to this group, but don't know who else in he world I can whine to.  (I can whine to my wife, or to my dog, but not a lot of help from either of them, although at least the dog does express some sympathy).

I ordered an ICD-2 from Microchip.  Got it in.  Downloaded MPLAB IDE 7.20 and installed it (that went pretty smooth).  Tried to install the ICD-2, had errors, aborted, and eventually got help from piclist on how to uninstall the USB driver.  (The problem had to do with choosing the Windows 98 installation instructions rather than the Windows XP instructions).

So today I tried to install the ICD-2 again.  The instructions that come from Microchip seem not to really mesh with what I am seeing, but I followed them as faithfully as possible.  The end result was that the New Hardware Wizard proclaimed that the firmware had been succesfully installed.  I am somewhat reluctant to believe this.

Now, whenever I plug the ICD-2 into the USB port, Windows XP immediately sets up a hue and cry and says "New Hardware detected" and brings up the Wizard.  Should that happen?  I'm not going to just leave it plugged into the USB port all the time.  Is there any way to test and see if everything is right?

Back when I used to use Wisp628 and only fool around the 18F452 chip I didn't have all these problems.  Should have left well enough along, I suppose.  Probably a good lesson to learn there.

John

2005\07\31@173616 by John J. McDonough

flavicon
face
John

I had similar problems.  I finally decided to hit it with a huge club.

What worked for me was the following ...

I followed the Microchip instructions for removing the USB driver three
times.  I paid special attention to any files mentioned that happened to be
installed in the Windows directory instead of the MPLAB directory.  I
rebooted each time.

I then uninstalled MPLAB.  Turned out I had to do that twice, too.  I think
that's because I downgraded from 7.1 to 7.01 in the course of trying to make
the thing work.  Rebooted between those uninstalls, too.

I then blew away all the files that were left in the MPLAB directories.

I then went into the registry and removed any entries that seemed to have
anything to do with Microchip.  That took some doing, there were dozens of
them.  I think I may have gotten some clues about some more files, too.

Then I went and deleted any Microchip files left in the Windows directories.
There were only a few ... sorry I didn't write down their names.

Rebooted again for good measure.

Then, I installed MPLAB, and VERY CAREFULLY followed Mchip's USB
instructions.

Windows isn't all that great about getting rid of drivers, so when in doubt,
reboot ... again!

--McD

----- Original Message -----
From: "John Nall" <spam_OUTjwnallTakeThisOuTspamgmail.com>
To: "Microcontroller discussion list - Public." <.....piclistKILLspamspam@spam@mit.edu>
Sent: Sunday, July 31, 2005 5:10 PM
Subject: [PIC]:Still problems with ICD2 installation


> Well, I hate to keep whining to this group, but don't know who
> else in he world I can whine to.

2005\07\31@185033 by Robert Rolf

picon face
Seconding John's experience, the only thing that worked
on my failed MPLab 7.2 ICD2 install was to clean out
the registry of ALL mplab references, and then reboot.

I made the mistake of trying to have a dual install
(6.62/ 7.2) and it was utterly brain dead until I too
nuked all the remnants of prior installs.

7.2 had bugs with not showing PCLATH and other registers
correctly on breakpoints so I downgraded to 6.6, where
I have staying since I'm not yet using the newer chips.

Anyone else seeing this? [PCLATH isn't updating if you
jump to a new page (at a page boundary) and hit a breakpoint.
If the landing address is at least 2 words into the page,
THEN PCLATH shows OK.
You shouldn't have to debug your debugger!]

That you cannot have both versions loaded into different
directories, and have them work independently makes no sense to me.
Most other software is smart enough to know which version
of the registry keys belongs to itself, but not Microshi+ MPLAB.

In fact, if you start the previously installed version,
it complains about some registry key not being pointed to
the correct directory. Is it THAT hard to change the name
of the key to include it's version number so such version conflicts
do not occur?

Robert
May the club be with you...

John J. McDonough wrote:

{Quote hidden}

2005\07\31@205133 by William Chops Westfield

face picon face
On Jul 31, 2005, at 3:50 PM, Robert Rolf wrote:

> Seconding John's experience, the only thing that worked
> on my failed MPLab 7.2 ICD2 install was to clean out
> the registry of ALL mplab references, and then reboot.

I also recently took advantage of MC's "free shipping + discount" and
bought a genuine ICD2.  I too had difficulties getting the install to
work as per microchip's instructions; no matter what I did, it seemed
W2K always got to the USB "new device" before the microchip installer
detected it.  Eventually, I think I gave up and did a "windows style"
install - figured out where the microchip drivers were and pointed the
windows HW wizard there, which seems to have made things happy - the
laptop and MPIDE seem to talk ok to the ICD2 (what more could I ask
for) (although I haven't used it extensively yet.)

I'll be installing it "soon" on a WXP system, and I'll try to keep
track of what I need to do there (assuming I even get it to work...)

BillW


'[PIC]:Still problems with ICD2 installation'
2005\08\04@081934 by Groups
flavicon
face
Is there any definitive action that can be taken to rectify the USB issue ?

I am having problems with the USB driver on a Laptop running XP pro.

MPLAB 7.1 was running fine and I tried to update to 7.2. When installing,
the IDE installed ok but when I went to follow the help and use the
"preinstall" utility
the dialog box mentioned the driver did not require updating or
preinstalling.

I then tried to run the clean but it did not delete all the files. I went to
registry and manually
deleted all files I could locate relating to microchip.

I then installed V7.11 again but had the same problem and can no longer get
the ICD2 running
with USB.

If plug in the ICD2, windows finds the new hardware and indicates it wants
to install Microchip Client
It does this fine in 2 stages then the screen goes blue (thought XP had
dealt with locking up of machine),
then it reports a problem with the ICD driver file and indicates it is going
to dump physical memory to dick.

I emailed Microchip but had no reply.

Any help much appreciated. I assume there is a file or 2 hidden away
somewhere I need to delete.

Thanks



Kind Regards

David Huisman (CEO)
-----------------------------------------------------------------------
ORBIT COMMUNICATIONS Pty Ltd - Wireless Solutions that Work
(Telemetry, Control, Monitoring, Security, HVAC ...)
A.C.N. 107 441 869


Website : http://www.orbitcoms.com
PO Box 4474 Lakehaven
NSW 2263, AUSTRALIA
Phone: 61-2-4393-3627
Fax  : 61-2-4393-3685
Mobile: 61-413-715-986

{Original Message removed}

2005\08\04@091608 by John Nall

picon face
Groups wrote:

>> Is there any definitive action that can be taken to rectify the USB issue ?
>
>I am having problems with the USB driver on a Laptop running XP pro.
>  
>
I contacted tech support at Microchip about the problem (I was the OP on
this thread) and got the advice to just install the driver like you
would any other new USB device.  Being sure to specify the location of
the drivers, of course.  They also told me that the drivers were
installed in two stages: (a) the firmware, and (b) the USB driver.  I
don't think that I had picked up on this before.  That "preinstall
utility" really sucks!

Mine seems to work OK now, to the extent that I no longer get error
messages about "new hardware" when I plug it in the USB port.  But have
not actually tried it out yet, so cannot guarantee it works.  I think
that I have the code for an 18F452 routine that I wrote around here
somewhere, so will use that and see if I can program it using the ICD2.  
If it does not work then I will contact Microchip again.  They are very
nice, and very helpful.

So far as "the blue screen of death" I have not had that problem.

John

2005\08\04@092825 by Groups

flavicon
face
John,

Thanks for the reply. I finally got it sorted. It seems the USB driver does
not like being installed
on a USB hub. I disconnected the ICD2 from the hub and pluggd it directly
into the Laptop.
It now runs.



Kind Regards

David Huisman (CEO)
-----------------------------------------------------------------------
ORBIT COMMUNICATIONS Pty Ltd - Wireless Solutions that Work
(Telemetry, Control, Monitoring, Security, HVAC ...)
A.C.N. 107 441 869


Website : http://www.orbitcoms.com
PO Box 4474 Lakehaven
NSW 2263, AUSTRALIA
Phone: 61-2-4393-3627
Fax  : 61-2-4393-3685
Mobile: 61-413-715-986

{Original Message removed}

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...