Post by thread:[PIC] Does MPLAB v7.60a actually WORK on ICD2?

Bob I've used ICD2 with MPLAB 7.60 (without the a) and Im using it with MPLAB 7.62 without having noticed anything wrong. ----- Mensaje original ---- De: Bob Axtell <spam_OUTengineerTakeThisOuTcotse.net> Para: Microcontroller discussion list - Public. <.....piclistKILLspam@spam@mit.edu> Enviado: viernes 14 de septiembre de 2007, 12:25:34 Asunto: [PIC] Does MPLAB v7.60a actually WORK on ICD2? For some reason, my XP's won't run ICD2 properly with MPLAB v60a. But MPLAB v7.40 works just fine. Why is it always ME who has to wring out Microchip's stuff? --Bob

>Im using it with MPLAB 7.62 without having noticed anything wrong. Same here. Mauricio Giovagnini wrote: {Quote hidden}> Bob I've used ICD2 with MPLAB 7.60 (without the a) and Im using it with MPLAB 7.62 without having noticed anything wrong. > > > > ----- Mensaje original ---- > De: Bob Axtell <engineerKILLspamcotse.net> > Para: Microcontroller discussion list - Public. <.....piclistKILLspam.....mit.edu> > Enviado: viernes 14 de septiembre de 2007, 12:25:34 > Asunto: [PIC] Does MPLAB v7.60a actually WORK on ICD2? > > For some reason, my XP's won't run ICD2 properly with MPLAB v60a. > But MPLAB v7.40 works just fine. > > Why is it always ME who has to wring out Microchip's stuff? > > --Bob

Den 2007-09-14 17:46:51 skrev Mauricio Giovagnini <EraseMEmaugiovagninispam_OUTTakeThisOuTyahoo.com.ar>: My collegue have used theese versions MPLAB with ICD2. There are both hardware and software problems. Note that we and at least one more user here ave had problems when PortB internal pullups are enabled. (A PIC18FJ running at VCC=VDD=2,5V) Problems showed when using "Real-ICE" but ICD are measured to be close to signal level problems too. It works for us to either a) shut of PortB pullups. b) configure the ICD pins as outputs and set them low. One more thing Micochip did not tell... OH, and my collegue have had lots of problems with MPLAB and the drivers on WinXP. MPLAB and sometimes WinXP need to be restarted some times a day :( Also, we broke WinXP by pluggin in a serial-USB and dumping data to it WinXP suddenly "detected a mouse", "autoinstalled" it, hung, and broke the filesystem :( :( Can this autodestroumyself idiocracy be turned off? Or we will try to move to only run windows in software emulators, or tools under wine. /Morgan {Quote hidden}> Bob I've used ICD2 with MPLAB 7.60 (without the a) and Im using it with MPLAB 7.62 without having noticed anything wrong. > > > > ----- Mensaje original ---- > De: Bob Axtell <engineerspam_OUTcotse.net> > Para: Microcontroller discussion list - Public. <@spam@piclistKILLspammit.edu> > Enviado: viernes 14 de septiembre de 2007, 12:25:34 > Asunto: [PIC] Does MPLAB v7.60a actually WORK on ICD2? > > For some reason, my XP's won't run ICD2 properly with MPLAB v60a. > But MPLAB v7.40 works just fine. > > Why is it always ME who has to wring out Microchip's stuff? > > --Bob -- Morgan Olsson

Mauricio Giovagnini wrote: > Bob I've used ICD2 with MPLAB 7.60 (without the a) and Im using it with MPLAB 7.62 without having noticed anything wrong. > > > > ----- Mensaje original ---- > De: Bob Axtell <KILLspamengineerKILLspamcotse.net> > Para: Microcontroller discussion list - Public. <RemoveMEpiclistTakeThisOuTmit.edu> > Enviado: viernes 14 de septiembre de 2007, 12:25:34 > Asunto: [PIC] Does MPLAB v7.60a actually WORK on ICD2? > > For some reason, my XP's won't run ICD2 properly with MPLAB v60a. > But MPLAB v7.40 works just fine. > > Why is it always ME who has to wring out Microchip's stuff? > > --Bob > Are you using XP Home Edition? --Bob

I am using 7.6 with ICD2 right now. So far okay. John --- Mauricio Giovagnini <spamBeGonemaugiovagninispamBeGoneyahoo.com.ar> wrote: {Quote hidden}> Bob I've used ICD2 with MPLAB 7.60 (without the a) > and Im using it with MPLAB 7.62 without having > noticed anything wrong. > > > > ----- Mensaje original ---- > De: Bob Axtell <TakeThisOuTengineerEraseMEspam_OUTcotse.net> > Para: Microcontroller discussion list - Public. > <RemoveMEpiclistTakeThisOuTmit.edu> > Enviado: viernes 14 de septiembre de 2007, 12:25:34 > Asunto: [PIC] Does MPLAB v7.60a actually WORK on > ICD2? > > For some reason, my XP's won't run ICD2 properly > with MPLAB v60a. > But MPLAB v7.40 works just fine. > > Why is it always ME who has to wring out Microchip's > stuff? > > --Bob > -

On 14/09/2007, Bob Axtell <engineerEraseME.....cotse.net> wrote: > Well, I am running again on 7.40. Thanks for all the responses. > It HAS to be me.... somehow. FWIW, the ICD2 fails miserably when I try to use 16F628A-chips. Any other chip works perfectly, but not the 628As. Microchip has no clue as to why, and the only way they've helped me regarding that matter is to give me questions which I answered in the first posting when contacting the support. I have tried only one ICD2, though, but atleast you're not on your own. -- - Rikard - http://bos.hack.org/cv/

Morgan Olsson skrev: > Den 2007-09-14 17:46:51 skrev Mauricio Giovagnini <EraseMEmaugiovagniniyahoo.com.ar>: > > > Also, we broke WinXP by pluggin in a serial-USB and dumping data to it > WinXP suddenly "detected a mouse", "autoinstalled" it, hung, and broke the filesystem :( :( > > Can this autodestroumyself idiocracy be turned off? > I used to have that all the time when using at GPS->serial-USB->PC setup. If the GPS was already sending NMEA messages when the USB dongle was plugged in, XP would detect it as some kind of MS mouse most of the time. Obvious solution is to make sure there is no traffic on the serial port until XP has properly detected and installed the USB device. Another solution is to allow the bogus mouse driver to be installed, stop the incoming serial traffic (to prevent old XP from hanging) and then select "disable this device" (or whatever the exact wording is) on the mouse in the Device Manager. {Quote hidden}> > >> Bob I've used ICD2 with MPLAB 7.60 (without the a) and Im using it with MPLAB 7.62 without having noticed anything wrong. >> >> >> >> ----- Mensaje original ---- >> De: Bob Axtell <RemoveMEengineerEraseMEEraseMEcotse.net> >> Para: Microcontroller discussion list - Public. <RemoveMEpiclistspam_OUTKILLspammit.edu> >> Enviado: viernes 14 de septiembre de 2007, 12:25:34 >> Asunto: [PIC] Does MPLAB v7.60a actually WORK on ICD2? >> >> For some reason, my XP's won't run ICD2 properly with MPLAB v60a. >> But MPLAB v7.40 works just fine. >> >> Why is it always ME who has to wring out Microchip's stuff? >> >> --Bob >> > > > >

Why Bob, Im just curios. Can't you download 7.62? ----- Mensaje original ---- De: Bob Axtell <RemoveMEengineerTakeThisOuTspamcotse.net> Para: Microcontroller discussion list - Public. <EraseMEpiclistspamspamBeGonemit.edu> Enviado: viernes 14 de septiembre de 2007, 14:22:27 Asunto: Re: [PIC] Does MPLAB v7.60a actually WORK on ICD2? John Chung wrote: > I am using 7.6 with ICD2 right now. So far okay. > > John > > > I'm stumped. Why me? I get bunches of USB comm errors, on all 3 machines, with 7.60a. With 7.4, all 3 work fine. Well, I am running again on 7.40. Thanks for all the responses. It HAS to be me.... somehow. -=-Bob

Thinking about it the trick might also have been uninstalling the ms crack pot mouse driver... it was a year ago or so I did this and my memory is globally declared volatile. Try either disabling the device or uninstalling the driver when the USB installation has gone haywire. Olof Larsson skrev: {Quote hidden}> Morgan Olsson skrev: > >> Den 2007-09-14 17:46:51 skrev Mauricio Giovagnini <RemoveMEmaugiovagniniKILLspamyahoo.com.ar>: >> >> >> Also, we broke WinXP by pluggin in a serial-USB and dumping data to it >> WinXP suddenly "detected a mouse", "autoinstalled" it, hung, and broke the filesystem :( :( >> >> Can this autodestroumyself idiocracy be turned off? >> >> > > I used to have that all the time when using at GPS->serial-USB->PC > setup. If the GPS was already sending NMEA messages when the USB dongle > was plugged in, XP would detect it as some kind of MS mouse most of the > time. Obvious solution is to make sure there is no traffic on the serial > port until XP has properly detected and installed the USB device. > Another solution is to allow the bogus mouse driver to be installed, > stop the incoming serial traffic (to prevent old XP from hanging) and > then select "disable this device" (or whatever the exact wording is) on > the mouse in the Device Manager. > > >> >> >>> Bob I've used ICD2 with MPLAB 7.60 (without the a) and Im using it with MPLAB 7.62 without having noticed anything wrong. >>> >>> >>> >>> ----- Mensaje original ---- >>> De: Bob Axtell <engineerSTOPspamspam_OUTcotse.net> >>> Para: Microcontroller discussion list - Public. <spamBeGonepiclistSTOPspamEraseMEmit.edu> >>> Enviado: viernes 14 de septiembre de 2007, 12:25:34 >>> Asunto: [PIC] Does MPLAB v7.60a actually WORK on ICD2? >>> >>> For some reason, my XP's won't run ICD2 properly with MPLAB v60a. >>> But MPLAB v7.40 works just fine. >>> >>> Why is it always ME who has to wring out Microchip's stuff? >>> >>> --Bob >>> >>> >> >> >>

Den 2007-09-14 19:51:31 skrev Olof Larsson <KILLspamolof.larssonspamBeGonetelevilt.se>: {Quote hidden}> > Morgan Olsson skrev: >> Den 2007-09-14 17:46:51 skrev Mauricio Giovagnini <EraseMEmaugiovagniniEraseMEyahoo.com.ar>: >> >> >> Also, we broke WinXP by pluggin in a serial-USB and dumping data to it >> WinXP suddenly "detected a mouse", "autoinstalled" it, hung, and broke the filesystem :( :( >> >> Can this autodestroumyself idiocracy be turned off? >> > > I used to have that all the time when using at GPS->serial-USB->PC > setup. If the GPS was already sending NMEA messages when the USB dongle > was plugged in, XP would detect it as some kind of MS mouse most of the > time. Obvious solution is to make sure there is no traffic on the serial > port until XP has properly detected and installed the USB device. > Another solution is to allow the bogus mouse driver to be installed, > stop the incoming serial traffic (to prevent old XP from hanging) and > then select "disable this device" (or whatever the exact wording is) on > the mouse in the Device Manager. > Problem was that when rebooting, XP hang when trying to finish the install. No way around, to abort, what we could see.

On Fri, 2007-09-14 at 19:51 +0200, Olof Larsson wrote: > Morgan Olsson skrev: > > Den 2007-09-14 17:46:51 skrev Mauricio Giovagnini <@spam@maugiovagnini@spam@spam_OUTyahoo.com.ar>: > > > > > > Also, we broke WinXP by pluggin in a serial-USB and dumping data to it > > WinXP suddenly "detected a mouse", "autoinstalled" it, hung, and broke the filesystem :( :( > > > > Can this autodestroumyself idiocracy be turned off? > > > > I used to have that all the time when using at GPS->serial-USB->PC > setup. If the GPS was already sending NMEA messages when the USB dongle > was plugged in, XP would detect it as some kind of MS mouse most of the > time. Obvious solution is to make sure there is no traffic on the serial > port until XP has properly detected and installed the USB device. > Another solution is to allow the bogus mouse driver to be installed, > stop the incoming serial traffic (to prevent old XP from hanging) and > then select "disable this device" (or whatever the exact wording is) on > the mouse in the Device Manager. Yes, very annoying issue. Off the top of my head, it's the "M" character that screws Windows up into thinking it's a mouse. Why this is still an issue in windows is a mystery, they've known about it for ages. TTYL

On 9/15/07, Bob Axtell <spamBeGoneengineerKILLspamcotse.net> wrote: > John Chung wrote: > > I am using 7.6 with ICD2 right now. So far okay. > I'm stumped. Why me? I get bunches of USB comm errors, on all 3 machines, > with 7.60a. With 7.4, all 3 work fine. > > Well, I am running again on 7.40. Thanks for all the responses. > It HAS to be me.... somehow. Are you using the original ICD2 or a clone? Sometimes that makes a big difference. Xiaofan

--- Xiaofan Chen <.....xiaofancspam_OUTgmail.com> wrote: {Quote hidden}> On 9/15/07, Bob Axtell <TakeThisOuTengineer.....TakeThisOuTcotse.net> wrote: > > John Chung wrote: > > > I am using 7.6 with ICD2 right now. So far okay. > > I'm stumped. Why me? I get bunches of USB comm > errors, on all 3 machines, > > with 7.60a. With 7.4, all 3 work fine. > > > > Well, I am running again on 7.40. Thanks for all > the responses. > > It HAS to be me.... somehow. > > Are you using the original ICD2 or a clone? > Sometimes that makes > a big difference. > > > Xiaofan > -- I am using an original ICD2. Do you want the firmware number? John ____________________________________________________________________________________ Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. http://autos.yahoo.com/index.html