Exact match. Not showing close matches.
PICList
Thread
'[PIC] MPLAB 10 and ICD support'
2009\10\27@052457
by
Artem Zezyulinskiy
Hi all!
Recently, I have assisted a Microchip forum, where I have heard from the
Microchip staff that they will jump around MPLAB 9 and they will release
directly MPLAB 10. This IDE will be very different from what we use now.
They say that ICD2 and Pickit2 will not be recommended (but supported)
for work with MPLAB 10.
I wonder if ICD2 will support the new chips from Microchip or it will be
only for ICD3?
The RealICE is still a hi end debug tool and ICD3 is a replacement for ICD2.
What do you think about it?
PS. sorry for my English - I continue to learn it :)
--
Artem
2009\10\27@053943
by
Jo Scherpenisse
Why is Pickit 2 not recommended?
It works fine for me.
Jo.
----- Original Message -----
From: "Artem Zezyulinskiy" <spam_OUTartemzezTakeThisOuT
sedatelec.com>
To: "Microcontroller discussion list - Public." <.....piclistKILLspam
@spam@mit.edu>
Sent: Tuesday, October 27, 2009 10:23 AM
Subject: [PIC] MPLAB 10 and ICD support
{Quote hidden}> Hi all!
>
> Recently, I have assisted a Microchip forum, where I have heard from the
> Microchip staff that they will jump around MPLAB 9 and they will release
> directly MPLAB 10. This IDE will be very different from what we use now.
>
> They say that ICD2 and Pickit2 will not be recommended (but supported)
> for work with MPLAB 10.
>
> I wonder if ICD2 will support the new chips from Microchip or it will be
> only for ICD3?
>
> The RealICE is still a hi end debug tool and ICD3 is a replacement for
> ICD2.
>
> What do you think about it?
>
> PS. sorry for my English - I continue to learn it :)
>
> --
> Artem
>
> --
2009\10\27@054848
by
Alan B. Pearce
>I wonder if ICD2 will support the new chips from Microchip
>or it will be only for ICD3?
The advertising on the Microchip web site already says the ICD2 is not
recommended for use with new devices. Due to various limitations with the
internal hardware of the ICD2 I doubt that it will continue to be supported
for new devices. Also note that Microchip are running a program to trade in
an ICD2 and get 25% off a new debug tool, such as an ICD3 or Real ICE. Note
that some revisions of the ICD2 will not work with Vista 64 (not sure about
Vista 32, but it may be that as well) due to internal hardware problems in
the ICD2.
>The RealICE is still a hi end debug tool and ICD3 is a replacement for
>ICD2.
Essentially yes, but when you look at the Real ICE feature list it does have
significant extra features. The ICD3 is also a lot faster than the ICD2 as
it can run at USB2 High Speed, where the ICD2 can run at only Full Speed,
and it has a lot more debugging features for the higher end target chips.
2009\10\27@062814
by
Artem Zezyulinskiy
For new MPLAB and new chips
Jo Scherpenisse a écrit :
> Why is Pickit 2 not recommended?
> It works fine for me.
> Jo.
>
> {Original Message removed}
2009\10\27@063501
by
Artem Zezyulinskiy
Alan B. Pearce a écrit :
> The advertising on the Microchip web site already says the ICD2 is not
> recommended for use with new devices. Due to various limitations with the
> internal hardware of the ICD2 I doubt that it will continue to be supported
> for new devices.
Ok
> Also note that Microchip are running a program to trade in
> an ICD2 and get 25% off a new debug tool, such as an ICD3 or Real ICE.
It is only for ICD3 not for Real ICE, right?
> Essentially yes, but when you look at the Real ICE feature list it does have
> significant extra features. The ICD3 is also a lot faster than the ICD2 as
> it can run at USB2 High Speed, where the ICD2 can run at only Full Speed,
> and it has a lot more debugging features for the higher end target chips.
>
but real ice have trace capability. It is really useful?
--
Artem
2009\10\27@102004
by
Tamas Rudnai
On Tue, Oct 27, 2009 at 10:33 AM, Artem Zezyulinskiy
<artemzez
KILLspamsedatelec.com> wrote:
> but real ice have trace capability. It is really useful?
In my opinion analysing the tracebuffer is one of the most useful
thing when you are dealing with complex code. So for example you can
look back when a variable set into a wrong value or at which point
your function got called or what branch of program flow it went before
the wrong value set. Sometimes is much better than conditional
breakpoints.
Tamas
>
> --
> Artem
>
> -
2009\10\27@161210
by
cdb
More... (looser matching)
- Last day of these posts
- In 2009
, 2010 only
- Today
- New search...