Searching \ for '[PIC] ICD2 so SLOOOOWWW!' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'ICD2 so SLOOOOWWW!'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] ICD2 so SLOOOOWWW!'
2006\08\13@141247 by Harley Shanko

flavicon
face
I'm getting back to a project after more than a year.  Uses a PIC16F871.
When I Run, Step, or Stop, the ICD2 it takes like 13 seconds to update
memory.  Makes for very annoyingly slow debugging.

I just changed to MPLAB 7.4; thought that might help somehow.  The old ICD2
OS is still listed as ICD01020700.

Does anyone know why it is this slow?  I don't recall such slowness before.
Sure takes the 'joy' out of debugging one's source.

Harley

2006\08\13@142214 by Herbert Graf

flavicon
face
On Sun, 2006-08-13 at 11:14 -0700, Harley Shanko wrote:
> I'm getting back to a project after more than a year.  Uses a PIC16F871.
> When I Run, Step, or Stop, the ICD2 it takes like 13 seconds to update
> memory.  Makes for very annoyingly slow debugging.
>
> I just changed to MPLAB 7.4; thought that might help somehow.  The old ICD2
> OS is still listed as ICD01020700.
>
> Does anyone know why it is this slow?  I don't recall such slowness before.
> Sure takes the 'joy' out of debugging one's source.

13 seconds? Sounds like you are "watching" alot. The time it takes the
ICD2 to "update" depends on how much you are watching. If you have the
RAM window open I can see it taking that long to update.

Otherwise, are you connecting through USB?

Thanks, TTYL

2006\08\13@143336 by Mike Harrison

flavicon
face
On Sun, 13 Aug 2006 11:14:42 -0700, you wrote:

>I'm getting back to a project after more than a year.  Uses a PIC16F871.
>When I Run, Step, or Stop, the ICD2 it takes like 13 seconds to update
>memory.  Makes for very annoyingly slow debugging.
>
>I just changed to MPLAB 7.4; thought that might help somehow.  The old ICD2
>OS is still listed as ICD01020700.
>
>Does anyone know why it is this slow?  I don't recall such slowness before.
>Sure takes the 'joy' out of debugging one's source.
>
>Harley

Helps a lot if you close any watch/memory/SFR windows you're not using

2006\08\14@162413 by Harley Shanko

flavicon
face
------------------------------

>13 seconds? Sounds like you are "watching" alot. The time it takes the
>ICD2 to "update" depends on how much you are watching. If you have the
>RAM window open I can see it taking that long to update.

>Otherwise, are you connecting through USB?

>Thanks, TTYL

No RAM window open, just SFRs and File Register windows and of course the
.asm file
------------------------------

>Helps a lot if you close any watch/memory/SFR windows you're not using

But, one needs to watch SFR, IMO, for most debugging.
------------------------------

>Are you using COM port interface or USB interface ? USB works much
>faster than COM interface.

>regards,
>palani

I am using the USB i/f.
------------------------------

Thanks to all who had suggestions.  I recall originall, it seems it only
took a second or two to step to the next instruction.  No fun being in
'debuggers hell deep in molassas!'


2006\08\14@164135 by Herbert Graf

flavicon
face
On Mon, 2006-08-14 at 13:26 -0700, Harley Shanko wrote:
> >Helps a lot if you close any watch/memory/SFR windows you're not using
>
> But, one needs to watch SFR, IMO, for most debugging.

But all of them? Depending on the PIC it can take a LONG time to update
the whole SFR window. Put only the SFRs you actually need to watch in
the "watch" window, close the SFR window and see if it improves the
speed.

> Thanks to all who had suggestions.  I recall originall, it seems it only
> took a second or two to step to the next instruction.  No fun being in
> 'debuggers hell deep in molassas!'

It should only be a second or two.

Only other case I can think of is if you are single stepping, and the
line of code you are at resolves to several op codes, it can take many
"steps" to actually get to the next line of code. This can happen in
HLLs, where one line of the HLL actually translates into several lines
of ASM, resulting in the "single" step taking quite a while.

Personally I never single step, I always use break points, much faster.

TTYL

2006\08\14@165504 by Mike Harrison

flavicon
face
On Mon, 14 Aug 2006 13:26:08 -0700, you wrote:

>------------------------------
>
>>13 seconds? Sounds like you are "watching" alot. The time it takes the
>>ICD2 to "update" depends on how much you are watching. If you have the
>>RAM window open I can see it taking that long to update.
>
>>Otherwise, are you connecting through USB?
>
>>Thanks, TTYL
>
>No RAM window open, just SFRs and File Register windows and of course the
>.asm file

File registers = RAM!
Close those windows, setup a watch for just the things you really need.


2006\08\15@142018 by Harley Shanko

flavicon
face
Mike Harrison wrote:
  File registers = RAM!
  Close those windows, setup a watch for just the things you really need.
------------------------------

Thanks Mike,
I looked at Help on Watch Windows.  Have been using MPLAB for years, off and
on.  Never realized the value of Watch Window before.  That really helped.
Now looking at about 1/2 dozen items, it is down to 1-2 seconds.  MUCH more
tolerable.

Again thanks to all you made suggestions on this matter.

More... (looser matching)
- Last day of these posts
- In 2006 , 2007 only
- Today
- New search...