Searching \ for 'ICD Problems' 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: 'ICD Problems'.

Truncated match.
PICList Thread
'ICD problems'
1999\07\24@092629 by Sam Laur

flavicon
face
I finally got mine...but there are constantly some problems with it. I've
got the demo program (demo877) to run a couple of times, but most of the time
I keep getting "ICD communication failed(4): cmd<7A00:1>" error boxes.
I'm using MPLAB 4.12 and Win95 (4.00.950 B), and the ICD is plugged into
COM1. It smells like a software error, since a reboot sometimes clears
things up. Also, sometimes the status line in the MPLAB-ICD dialog box gives
"ICD Stack Error:cmd<700B:2>"

I've also checked through the (very short) Troubleshooting section of the
ICD user's guide, no help there. Oh yeah - there's a sticker on the 16C73B
that says U1 (V1.23) but the self-test returns firmware version as 1.22...

1999\07\26@072334 by Laszlo Kohegyi

flavicon
face
Hi,

>I finally got mine...but there are constantly some problems with it. I've
>got the demo program (demo877) to run a couple of times, but most of the
time
>I keep getting "ICD communication failed(4): cmd<7A00:1>" error boxes.
>I'm using MPLAB 4.12 and Win95 (4.00.950 B), and the ICD is plugged into
>COM1. It smells like a software error, since a reboot sometimes clears
>things up. Also, sometimes the status line in the MPLAB-ICD dialog box
gives
>"ICD Stack Error:cmd<700B:2>"

I've been trying to make it work too. I found that before you run the
program
(f9) you should reset it (f6).

>I've also checked through the (very short) Troubleshooting section of the
>ICD user's guide, no help there. Oh yeah - there's a sticker on the 16C73B
>that says U1 (V1.23) but the self-test returns firmware version as 1.22...

I have some problem with the hardware usart. When I run the program, it is
OK.
If I try the single step, the usart transmit register seems to be always
busy.
I tried to find out something from the user's guide, but it doesn't mention
it.

Regards
Les

1999\07\26@091542 by peterc

flavicon
face
Sam Laur wrote:
>
<snip>
> COM1. It smells like a software error, since a reboot sometimes clears
> things up. Also, sometimes the status line in the MPLAB-ICD dialog box gives
> "ICD Stack Error:cmd<700B:2>"
>
<snip>

I've not used one of these ICDs, but have noticed that one of the
restrictions on the PIC program is to only use one level of stack. Is it
possible that you've got nested calls and that's what the message is
saying?

(Presumably the ICD software in the PIC requries the remaining stack
levels for it's own calls).

--
Peter Crighton

1999\07\26@104515 by Chris Cole

flavicon
face
On Mon, 26 Jul 1999, peterc wrote:

> I've not used one of these ICDs, but have noticed that one of the
> restrictions on the PIC program is to only use one level of stack. Is it
> (Presumably the ICD software in the PIC requries the remaining stack
> levels for it's own calls).

Actually, you have one LESS (not just one total) stack levels available;
This means 7 levels left on the current 16f87x parts.


Take care,
       Chris Cole
       spam_OUTcoleTakeThisOuTspamcoledd.com

1999\07\27@060933 by Sam Laur

flavicon
face
> I've been trying to make it work too. I found that before you run the
> program
> (f9) you should reset it (f6).

This was it... thanks. Seems to work OK now. I'm emulating a 16F84 with it
now, the memory layout is a bit different but it seems to work fine - once
I realised I should set ADCON1 so that PORTA is digital I/O. Also, I'm using
PORTC as a replacement for PORTB (which, as we all know, has RB3, RB6 and RB7
unavailable now). I've wired RB0 to RC0 so I can debug the interrupt function.


'ICD Problems'
2000\05\24@133147 by Jilles Oldenbeuving
flavicon
face
Hi,


I've got a problem with my new ICD. The first few hours it worked fine,
programming, debugging, eraseing, etc. But after a few hours the debugging
would not work anymore. I can program the 877, erase it etc. But single
stepping,
animate, run, reset, won't work and MPLAB v.5 comes up with: "Error
performing the requested operation"

Yes, i've got the debug tag on, so that wouldn't be the problem. Here is
some other inforation:

The selftest of the ICD returns:

>"DLL version: 1.3100
>Firmware version: 2.04
>Debug module: not exist
>Selftest: ok"

Is this allright?  Does anybody know an answer to this problem? I'd like to
hear so.

Note: the ICD was bought, not self-build. The PIC 877 is the one that was
supplied with
it.


Thanx for your time,


Jilles Oldenbeuving

2000\05\24@181351 by briang

flavicon
face
In-Reply-To: <007901bfc5a4$77052ec0$db653dc3@oldenbeuvingpc>

In response to .....jillesKILLspamspam@spam@RENDO.DEKOOI.NL

I think you have probably accidentally turned off "debug mode".

Brian Gregory.
briangspamKILLspamcix.co.uk

2000\05\27@023737 by Dan Mulally

flavicon
face
----- Original Message -----
From: "Jilles Oldenbeuving" <.....jillesKILLspamspam.....RENDO.DEKOOI.NL>
To: <EraseMEPICLISTspam_OUTspamTakeThisOuTMITVMA.MIT.EDU>
Sent: Wednesday, May 24, 2000 11:21 AM
Subject: ICD Problems


{Quote hidden}

to
{Quote hidden}

You may want to try reinstalling MPLAB. From my experience if the ICD looses
power the only way to get it to work again is to close MPLAB and reopen it.
Selecting the "reconnect" button causes it to act like it reconnected, but
it still doesn't work.

Dan Mulally

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