Anyone have a list of devices that the Pickit3 supports, specifically PIC32 devices?
Also, I've seen a number of posts that indicate that the Pickit3 is problematic, compared to the Pickit2, but those posts are a year old. Is this still the case?
Most importantly though, I've read that each time the Pickit3 switches processor families, it needs to download new firmware. Not sure where it's downloading from, but I'm assuming it means download off the internet... ? If so, what if I'm not connected to the internet? Will it get it off my local PC, or will it just not be able to continue working?
> Anyone have a list of devices that the Pickit3 supports, specifically
> PIC32 devices?
In the readme file for the Pickit3 that comes with MPLAB.
> Also, I've seen a number of posts that indicate that the Pickit3 is problematic,
> compared to the Pickit2, but those posts are a year old.
> Is this still the case?
Don't have experience with it, but I believe many of the basic gripes have been sorted.
> Most importantly though, I've read that each time the Pickit3 switches processor
> families, it needs to download new firmware. Not sure where it's downloading from,
> but I'm assuming it means download off the internet... ? If so, what if I'm not
> connected to the internet? Will it get it off my local PC, or will it just not be
> able to continue working?
MPLAB comes with a dose of downloads that it automagically selects according to processor family. The ICDx and RealIce do the same I believe.
On Fri, Jun 22, 2012 at 8:49 PM, Neil <spam_OUTpicdude3TakeThisOuTnarwani.org> wrote:
> Anyone have a list of devices that the Pickit3 supports, specifically
> PIC32 devices?
In the Readme of MPLAB and MPLABX.
> Also, I've seen a number of posts that indicate that the Pickit3 is
> problematic, compared to the Pickit2, but those posts are a year old.
> Is this still the case?
It seems to get better but there are still many complaints.
If you want to work with PIC32, then forget about PICKit 3,
buy the ICD 3, the speed difference is significant.
BTW, Microchip has released a tool to make PICkit 3 act as
a PICKit 2. That probably says something about the
popularity of PICKit 2. http://www.microchip.com/forums/m654567.aspx
On 6/22/2012 9:26 AM, Xiaofan Chen wrote:
> ...
> If you want to work with PIC32, then forget about PICKit 3,
> buy the ICD 3, the speed difference is significant.
>
Pickit 2's are awesome (I have a few), but I'm being forced towards the Pickit 3 for using PIC32's now. The portability is great (as I travel a lot and have a small case with my Pickit2, Saleae Logic analyzer, and some custom super-small dev boards), so I'd prefer not to get an ICD, etc. I really don't do much in the way of debugging as spitting my own test values out via serial or a basic output has always been a clean/direct way to do this.
I'm looking at PIC32's for a project which would have SD/FAT, USB host, analog, digital bit-banging, and a keypad/LCD interface. I've been just barely refusing to go to ARM since I already have and am familiar with PIC dev tools and environment. But if I have to get new programmers etc, then I'm going to start re-considering ARM's, as the NXP & ST devices are tempting.
>Anyone have a list of devices that the Pickit3 supports, specifically
>PIC32 devices?
*All] PIC32 devices are supported by Pickit3 as far as I know.
>Also, I've seen a number of posts that indicate that the Pickit3 is
>problematic, compared to the Pickit2, but those posts are a year old.
>Is this still the case?
The most important missing thing when pickit 3 was released was the standalone programming application that has the pickit 2.
But I read and watched several videos talking about the release of the standalone application for pickit3 but I can't get any useful link to the app.
>Most importantly though, I've read that each time the Pickit3 switches
>processor families, it needs to download new firmware. Not sure where
>it's downloading from, but I'm assuming it means download off the
>internet... ? If so, what if I'm not connected to the internet? Will
>it get it off my local PC, or will it just not be able to continue working?
It is true that new firmwares can be downloaded to the programmer when chaning device families but
you don't need to be connected to the internet all the time. The firmwares are picked up from your MPLAB directory (v8.8x or IDE X)
On 22/06/2012 20:39, Mauricio Giovagnini wrote:
>
>> Also, I've seen a number of posts that indicate that the Pickit3 is
>> problematic, compared to the Pickit2, but those posts are a year old.
>> Is this still the case?
>
> The most important missing thing when pickit 3 was released was the standalone programming application that has the pickit 2.
>
> But I read and watched several videos talking about the release of the standalone application for pickit3 but I can't get any useful link to the app..
>
> http://www.youtube.com/watch?v=3EkNUa2nSDE
>
> http://www.microchip.com/forums/m554515.aspx
It exists and can be found with a bit of googling, but I have found it fairly useless.
>> Most importantly though, I've read that each time the Pickit3 switches
>> processor families, it needs to download new firmware. Not sure where
>> it's downloading from, but I'm assuming it means download off the
>> internet... ? If so, what if I'm not connected to the internet? Will
>> it get it off my local PC, or will it just not be able to continue working?
>
> It is true that new firmwares can be downloaded to the programmer when chaning device families but
> you don't need to be connected to the internet all the time. The firmwares are picked up from your MPLAB directory (v8.8x or IDE X)
This is the only part of the PK3 which for me is still buggy. I develop code in a VMware machine so I can port around my development setup. When changing device families in MPLABX (most often 18F to 12F) I have bricked the PK3 three times. This necessitates opening it up and reprogramming using my PK2. The fix is to do the firmware download from MPLAB8 on the host, this works flawlessly.
Aside from this my general comments are that the PK3 is much nicer and faster than the PK2. It supports a wider range of devices.
>>
>>> Also, I've seen a number of posts that indicate that the Pickit3 is
>>> problematic, compared to the Pickit2, but those posts are a year old.
>>> Is this still the case?
>>
>> The most important missing thing when pickit 3 was released was the
> standalone programming application that has the pickit 2.
>>
>> But I read and watched several videos talking about the release of the
> standalone application for pickit3 but I can't get any useful link to the
> app.
>>
>> http://www.youtube.com/watch?v=3EkNUa2nSDE
>>
>> http://www.microchip.com/forums/m554515.aspx
>
> It exists and can be found with a bit of googling, but I have found it
> fairly useless.
But in the official link of Microchip's PICKIT3 it isn't and that is, at least, a little bit weird.
It is also referenced by a Microchip personel in the forum link I added and it isn't there.
>>> Most importantly though, I've read that each time the Pickit3
> switches
>>> processor families, it needs to download new firmware. Not sure where
>>> it's downloading from, but I'm assuming it means download off
> the
>>> internet... ? If so, what if I'm not connected to the internet?
> Will
>>> it get it off my local PC, or will it just not be able to continue
> working?
>>
>> It is true that new firmwares can be downloaded to the programmer when
> chaning device families but
>> you don't need to be connected to the internet all the time. The
> firmwares are picked up from your MPLAB directory (v8.8x or IDE X)
>
> This is the only part of the PK3 which for me is still buggy. I develop
> code in a VMware machine so I can port around my development setup.
> When changing device families in MPLABX (most often 18F to 12F) I have
> bricked the PK3 three times. This necessitates opening it up and
> reprogramming using my PK2. The fix is to do the firmware download from
> MPLAB8 on the host, this works flawlessly.
The same happened to me with MPLAB X IDE v1.10 and my ICD3. I had to reprogram it with the MPLAB v8.84.
Fortunately the problem seems not to be present in MPLB X IDE v1.20 and it wasn't present in MPLAB X IDE v1.0
MPLABX 1.20 comes with a new application called IPE for programming. It
seems much better than pickit3 standalone application, and it supports all
new chips