PicKit 2 WARNING (problem solved)
in [Design]
|
Prev: atlantic research corporation interview 6600 disk
Next: Adjustable constant current source 0.5 uA microAmps to 2 Amps
From: Robert Baer on 17 Sep 2009 03:30 IanM wrote: > E wrote: >>>> Have you tried updating it (tools ->Download Pickit2 Operating System) >>>> I have noticed it tends to lose its operating system if mishandled. >>> No, but i think that i cannot do that as i fully expect the file to >>> be over a few megs in size (am on dial-up). >> >> Megabytes on a pic? >> Its actually 27 kB zipped from microchip website >> > No website access required. > Look for PK2Vnnnnnn.hex in your PICKit2 directory. nnnnnn is numeric > and depends on the firmware version No. If present, download it using > the PICKit2 application. > > If *that* doesn't work, go online and grab PK2CMDv1-20.zip (118KB of > command line programmer software for the PICKit2) from Microchip. > <http://ww1.microchip.com/downloads/en/DeviceDoc/PK2CMDv1-20.zip> > unpack it and start a command prompt in its directory. Plug in the > PICKit2, with no target circuit connected, direct to a USB port and run: > > PK2CMD -S# > > to view connected PICKit2's. If it doesn't see it, re-plug with the > button held down (forces bootloader mode - Busy led flashes) then > release the button and try again. > If it sees it, especially if it sees 'bootloader', run > > PK2CMD -D PK2V023200.hex > > If it succeeds, re-plug the PICKit2 and run the GUI software, check it > finds the pod then use tools->troubleshoot... and a multimeter to verify > the ICSP interface is functional. > > If you are still stuck after that you have two possible options, raise a > support request with Microchip, or crack the case and reprogram the > PIC182550-I/SO via J1 the ICSP pads using another known good programmer. > If it fails, order that PIC, replace the U1 chip and program the new > chip with the firmware the same way. > Resolved! Could not download PK2Vnnnnnn.hex, so went to your step #2. Got the PK2CMDv1-20.zio, unpacked it and PK2CMD -S# gave: Unit 0, no ID, firmware 2.32.00, operation succeeded (no mention of bootloader). So, ran PK2CMD -D PK2V023200.hex and got: error in opening hex file (damn!). Fortuanetly somewhere in the PIC directories i found another copy and got OS update successful. Tried next step, re-plugged the PIC pod, ran the gooie software and it worked. Lastly, i tried the pod to erase the "bad" PIC and then re-programmed it - then tried it in my app. WORKS! ** So now i have !two! PIK2 pods, some newer (but "old" disks) and a puzzle. How did that pod's OS get damaged?
From: IanM on 17 Sep 2009 04:13 Robert Baer wrote: > IanM wrote: >> E wrote: >>>>> Have you tried updating it (tools ->Download Pickit2 Operating System) >>>>> I have noticed it tends to lose its operating system if mishandled. >>>> No, but i think that i cannot do that as i fully expect the file >>>> to be over a few megs in size (am on dial-up). >>> >>> Megabytes on a pic? >>> Its actually 27 kB zipped from microchip website >>> >> No website access required. >> Look for PK2Vnnnnnn.hex in your PICKit2 directory. nnnnnn is numeric >> and depends on the firmware version No. If present, download it using >> the PICKit2 application. >> >> If *that* doesn't work, go online and grab PK2CMDv1-20.zip (118KB of >> command line programmer software for the PICKit2) from Microchip. >> <http://ww1.microchip.com/downloads/en/DeviceDoc/PK2CMDv1-20.zip> >> unpack it and start a command prompt in its directory. Plug in the >> PICKit2, with no target circuit connected, direct to a USB port and run: >> >> PK2CMD -S# >> >> to view connected PICKit2's. If it doesn't see it, re-plug with the >> button held down (forces bootloader mode - Busy led flashes) then >> release the button and try again. >> If it sees it, especially if it sees 'bootloader', run >> >> PK2CMD -D PK2V023200.hex >> >> If it succeeds, re-plug the PICKit2 and run the GUI software, check >> it finds the pod then use tools->troubleshoot... and a multimeter to >> verify the ICSP interface is functional. >> >> If you are still stuck after that you have two possible options, raise >> a support request with Microchip, or crack the case and reprogram the >> PIC182550-I/SO via J1 the ICSP pads using another known good >> programmer. If it fails, order that PIC, replace the U1 chip and >> program the new chip with the firmware the same way. >> > Resolved! > Could not download PK2Vnnnnnn.hex, so went to your step #2. > Got the PK2CMDv1-20.zio, unpacked it and > PK2CMD -S# > gave: Unit 0, no ID, firmware 2.32.00, operation succeeded (no mention > of bootloader). > So, ran > PK2CMD -D PK2V023200.hex > and got: error in opening hex file (damn!). Fortuanetly somewhere in > the PIC directories i found another copy and got OS update successful. > Tried next step, re-plugged the PIC pod, ran the gooie software and it > worked. > Lastly, i tried the pod to erase the "bad" PIC and then re-programmed > it - then tried it in my app. > WORKS! > ** > So now i have !two! PIK2 pods, some newer (but "old" disks) and a puzzle. > How did that pod's OS get damaged? > Glad to have been of help. I suspect that the pod got damaged by a glitch on the USB power or circuit power causing a random jump. Once in a while such a glitch will end up in the bootloader at just the right point to wipe a block of the OS. As long as the recovery procedure is known, its no big deal. Are both your pods red button ones? If not, there is an upgrade reccomended (3 resistors) to support ICD operation and improve recognition if briefly disconnected. -- Ian Malcolm. London, ENGLAND. (NEWSGROUP REPLY PREFERRED) ianm[at]the[dash]malcolms[dot]freeserve[dot]co[dot]uk [at]=@, [dash]=- & [dot]=. *Warning* HTML & >32K emails --> NUL:
From: Robert Baer on 18 Sep 2009 03:52 IanM wrote: > Robert Baer wrote: >> IanM wrote: >>> E wrote: >>>>>> Have you tried updating it (tools ->Download Pickit2 Operating >>>>>> System) >>>>>> I have noticed it tends to lose its operating system if mishandled. >>>>> No, but i think that i cannot do that as i fully expect the file >>>>> to be over a few megs in size (am on dial-up). >>>> >>>> Megabytes on a pic? >>>> Its actually 27 kB zipped from microchip website >>>> >>> No website access required. >>> Look for PK2Vnnnnnn.hex in your PICKit2 directory. nnnnnn is numeric >>> and depends on the firmware version No. If present, download it >>> using the PICKit2 application. >>> >>> If *that* doesn't work, go online and grab PK2CMDv1-20.zip (118KB of >>> command line programmer software for the PICKit2) from Microchip. >>> <http://ww1.microchip.com/downloads/en/DeviceDoc/PK2CMDv1-20.zip> >>> unpack it and start a command prompt in its directory. Plug in the >>> PICKit2, with no target circuit connected, direct to a USB port and run: >>> >>> PK2CMD -S# >>> >>> to view connected PICKit2's. If it doesn't see it, re-plug with the >>> button held down (forces bootloader mode - Busy led flashes) then >>> release the button and try again. >>> If it sees it, especially if it sees 'bootloader', run >>> >>> PK2CMD -D PK2V023200.hex >>> >>> If it succeeds, re-plug the PICKit2 and run the GUI software, check >>> it finds the pod then use tools->troubleshoot... and a multimeter to >>> verify the ICSP interface is functional. >>> >>> If you are still stuck after that you have two possible options, >>> raise a support request with Microchip, or crack the case and >>> reprogram the PIC182550-I/SO via J1 the ICSP pads using another known >>> good programmer. If it fails, order that PIC, replace the U1 chip and >>> program the new chip with the firmware the same way. >>> >> Resolved! >> Could not download PK2Vnnnnnn.hex, so went to your step #2. >> Got the PK2CMDv1-20.zio, unpacked it and >> PK2CMD -S# >> gave: Unit 0, no ID, firmware 2.32.00, operation succeeded (no >> mention of bootloader). >> So, ran >> PK2CMD -D PK2V023200.hex >> and got: error in opening hex file (damn!). Fortuanetly somewhere in >> the PIC directories i found another copy and got OS update successful. >> Tried next step, re-plugged the PIC pod, ran the gooie software and >> it worked. >> Lastly, i tried the pod to erase the "bad" PIC and then >> re-programmed it - then tried it in my app. >> WORKS! >> ** >> So now i have !two! PIK2 pods, some newer (but "old" disks) and a >> puzzle. >> How did that pod's OS get damaged? >> > Glad to have been of help. I suspect that the pod got damaged by a > glitch on the USB power or circuit power causing a random jump. Once in > a while such a glitch will end up in the bootloader at just the right > point to wipe a block of the OS. As long as the recovery procedure is > known, its no big deal. > Are both your pods red button ones? > If not, there is an upgrade reccomended (3 resistors) to support ICD > operation and improve recognition if briefly disconnected. > Both have red buttons. Isn't it really nice that the ZIP i downloaded had a bad .HEX file? I bet that EVERYONE else that downloads that ZIP has *zero* problems.
From: Robert Baer on 18 Sep 2009 03:52
IanM wrote: > Robert Baer wrote: >> IanM wrote: >>> E wrote: >>>>>> Have you tried updating it (tools ->Download Pickit2 Operating >>>>>> System) >>>>>> I have noticed it tends to lose its operating system if mishandled. >>>>> No, but i think that i cannot do that as i fully expect the file >>>>> to be over a few megs in size (am on dial-up). >>>> >>>> Megabytes on a pic? >>>> Its actually 27 kB zipped from microchip website >>>> >>> No website access required. >>> Look for PK2Vnnnnnn.hex in your PICKit2 directory. nnnnnn is numeric >>> and depends on the firmware version No. If present, download it >>> using the PICKit2 application. >>> >>> If *that* doesn't work, go online and grab PK2CMDv1-20.zip (118KB of >>> command line programmer software for the PICKit2) from Microchip. >>> <http://ww1.microchip.com/downloads/en/DeviceDoc/PK2CMDv1-20.zip> >>> unpack it and start a command prompt in its directory. Plug in the >>> PICKit2, with no target circuit connected, direct to a USB port and run: >>> >>> PK2CMD -S# >>> >>> to view connected PICKit2's. If it doesn't see it, re-plug with the >>> button held down (forces bootloader mode - Busy led flashes) then >>> release the button and try again. >>> If it sees it, especially if it sees 'bootloader', run >>> >>> PK2CMD -D PK2V023200.hex >>> >>> If it succeeds, re-plug the PICKit2 and run the GUI software, check >>> it finds the pod then use tools->troubleshoot... and a multimeter to >>> verify the ICSP interface is functional. >>> >>> If you are still stuck after that you have two possible options, >>> raise a support request with Microchip, or crack the case and >>> reprogram the PIC182550-I/SO via J1 the ICSP pads using another known >>> good programmer. If it fails, order that PIC, replace the U1 chip and >>> program the new chip with the firmware the same way. >>> >> Resolved! >> Could not download PK2Vnnnnnn.hex, so went to your step #2. >> Got the PK2CMDv1-20.zio, unpacked it and >> PK2CMD -S# >> gave: Unit 0, no ID, firmware 2.32.00, operation succeeded (no >> mention of bootloader). >> So, ran >> PK2CMD -D PK2V023200.hex >> and got: error in opening hex file (damn!). Fortuanetly somewhere in >> the PIC directories i found another copy and got OS update successful. >> Tried next step, re-plugged the PIC pod, ran the gooie software and >> it worked. >> Lastly, i tried the pod to erase the "bad" PIC and then >> re-programmed it - then tried it in my app. >> WORKS! >> ** >> So now i have !two! PIK2 pods, some newer (but "old" disks) and a >> puzzle. >> How did that pod's OS get damaged? >> > Glad to have been of help. I suspect that the pod got damaged by a > glitch on the USB power or circuit power causing a random jump. Once in > a while such a glitch will end up in the bootloader at just the right > point to wipe a block of the OS. As long as the recovery procedure is > known, its no big deal. > Are both your pods red button ones? > If not, there is an upgrade reccomended (3 resistors) to support ICD > operation and improve recognition if briefly disconnected. > Thanks loads! |