burning PicKit2 firmware
grokakin
I am bit ashamed to come back telling my PicKit 2 clone has problem
after having been helped for it to work, but that's the way it
is :-) .
For some unkonwn reason, the clone is not recognized anymore as a USB
device, as it was before.
I haven't got anymore the programmer I used first .
Searching on the net, I found ART2003 programmer who is said to be
able to do LVP and specifically for 18F2550 pics . It is a simple
programmer which is plugged in the parallel port with no external
power supply .
Do you think it is possible to burn the Bootloader or/and OS in LVP ?
Thanks for your help and any advice on the ART2003 ,
Cédric
Xiaofan Chen
>
> For some unkonwn reason, the clone is not recognized anymore as a USB
> device, as it was before.
Have you tried to press the button and then plug PICKit 2 into the
USB port? The red LED should blink and PICKit 2 will enter
bootloader mode. Download the PICkit 2 firmware V2.32 and
then use pk2cmd to update the firmware. You can use
lsusb to confirm this.
You can also try this thread (for Windows).
http://www.microchip.com/forums/tm.aspx?m=415391
If this does not help, then the PICkit 2 bootloader is somehow
gone. In that case, you need another programmer.
> I haven't got anymore the programmer I used first .
>
> Searching on the net, I found ART2003 programmer who is said to be
> able to do LVP and specifically for 18F2550 pics . It is a simple
> programmer which is plugged in the parallel port with no external
> power supply .
>
> Do you think it is possible to burn the Bootloader or/and OS in LVP ?
> Thanks for your help and any advice on the ART2003 ,
That won't work. The PIC18F2550 on board PICKit 2 is configured to
disable LVP. You can confirm that by looking at the firmware source
code (bootmain.c).
--
Xiaofan http://mcuee.blogspot.com
grokakin
The red light gets blinking as I push the button when plugging the
PicKit2 and keeps on blinking , but lsusb doesn't display the
PicKit2 .
Have you got an idea ?
On 14 avr, 16:34, Xiaofan Chen <xiaof...@gmail.com> wrote:
>
> > For some unkonwn reason, the clone is not recognized anymore as a USB
> > device, as it was before.
>
> Have you tried to press the button and then plug PICKit 2 into the
> USB port? The red LED should blink and PICKit 2 will enter
> bootloader mode. Download the PICkit 2 firmware V2.32 and
> then use pk2cmd to update the firmware. You can use
> lsusb to confirm this.
>
Xiaofan Chen
> The red light gets blinking as I push the button when plugging the
> PicKit2 and keeps on blinking , but lsusb doesn't display the
Sorry, in that case, you have to get another programmer to reload
the firmware.
--
Xiaofan http://mcuee.blogspot.com
Jeff Post
> On Wed, Apr 15, 2009 at 7:36 PM, grokakin <cedric...@tele2.fr> wrote:
> > The red light gets blinking as I push the button when plugging the
> > PicKit2 and keeps on blinking , but lsusb doesn't display the
> > PicKit2. Have you got an idea ?
>
> Sorry, in that case, you have to get another programmer to reload
> the firmware.
Isn't the red light blinking a function of the bootloader code? Seems to me it
may be a USB problem. Since lsusb doesn't see the PICkit2, it may be cable or
power. Try it on another machine if you have access to one. Also try a
shorter cable and/or a different USB port.
As a last resort, try it on a Windows machine.
Jeff
Xiaofan Chen
>
> Isn't the red light blinking a function of the bootloader code? Seems to me it
> may be a USB problem. Since lsusb doesn't see the PICkit2, it may be cable or
> power. Try it on another machine if you have access to one. Also try a
> shorter cable and/or a different USB port.
>
> As a last resort, try it on a Windows machine.
You might be right. Your recommendation is worth trying.
To confirm it is a USB problem, the OP can try the following.
Troubleshooting step 1
1) Plug in PICKit 2
2) print out the last few lines of "demsg" by using "dmesg | tail"
Troubleshooting step 2
1) Plug in the PICKit 2 with the button pressed
2) print out the last few lines of "demsg" by using "dmesg | tail"
Normal response in both case should be like this.
usb 2-7: USB disconnect, address 4
usb 2-7: new full speed USB device using ohci_hcd and address 6
usb 2-7: configuration #1 chosen from 2 choices
--
Xiaofan http://mcuee.blogspot.com
Jeff Post
>
> To confirm it is a USB problem, the OP can try the following.
> Troubleshooting step 1
> 1) Plug in PICKit 2
> 2) print out the last few lines of "demsg" by using "dmesg | tail"
>
redirect dmesg output to a file. Tail might work on Ubuntu, but it definitely
doesn't capture the relevant data on CentOS (on my machine, the data is about
30 lines or so before the end of dmesg output).
Jeff
grokakin
Thanks very much for your help and ideas.
You were right about the cable.
There were two problems actually:
the USB cable was defective, what I discovered with a multimeter.
When I realized that, I changed the cable, lauching under XP picKit2
app, and then it appeared the OS was not present anymore.
I reloaded it and it works again .
That's a kind of sport to use this clone :-)
I am gonna do a backup on another pic18F2550 ...
Regards,
Cédric
Xiaofan Chen
> You were right about the cable.
> There were two problems actually:
> the USB cable was defective, what I discovered with a multimeter.
> When I realized that, I changed the cable, lauching under XP picKit2
> app, and then it appeared the OS was not present anymore.
>
> I reloaded it and it works again .
>
> That's a kind of sport to use this clone :-)
> I am gonna do a backup on another pic18F2550 ...
>
Glad that you get it working.
--
Xiaofan http://mcuee.blogspot.com