After updating to v3.183 I have error "Target not in de

franckcl · Joined: 12 Sep 2003 Posts: 32 Location: France (Paris)

hello,

(using ICD2, PCHW, PIC18F6520)

I have updated my compiler from v3.182 to 3.183 and now I have this error message :

"ICD0083: Target not in debug mode, unable to perform operation"

I don't anderstand why and if I re-install the old version v3.182, there is no problem.

In my code I have the line #device ICD=TRUE

Thank you
Franck

martin gordon · Joined: 15 Sep 2003 Posts: 6 Location: Edinburgh

franckcl

It is usually a good idea to email CCS support when you find this type of problem so that they may investigate

Are you using MPLAB?

Martin

franckcl · Joined: 12 Sep 2003 Posts: 32 Location: France (Paris)

Ok, but may be some one had the solution.
I am writing mail to CCS.
Franck

Mark · Joined: 07 Sep 2003 Posts: 2838 Location: Atlanta, GA

Read this post. They made changes in that area in 3.183

http://www.ccsinfo.com/forum/viewtopic.php?t=18024&highlight=fuse+settings+forced+icd+mode+changed+parts

radian · Joined: 12 Jan 2004 Posts: 7

If your target doesn't own supply try this:

"Debugger->Settings->Power"

And check "Power target circuit from MPLAB ICD 2 (5V VDD)

radian · Joined: 12 Jan 2004 Posts: 7

Excuse me! I didn't see that your debugger running on the CCS 1.182. I have the alike problem and it was my neligence.

martin gordon · Joined: 15 Sep 2003 Posts: 6 Location: Edinburgh

The problem apear to be fixed by the new release. Quote

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 3.184

Recent changes include:
3.184 A problem with fuses in the ICD=TRUE mode has been fixed
3.184 A new built in function CLEAR_INTERRUPT has been added

I have loaded and in a quick test it seems to have fixed my problem

Martin

franckcl · Joined: 12 Sep 2003 Posts: 32 Location: France (Paris)

Yes , the problem has been fixed in the new release 3.184
Thank you
Franck

renato · Guest

Why CCS people still have the problem of things that works in previous versions stop working in new releases?
This shouldn't happen!! We can't trust in the compiler, is a mess .

arga · Joined: 09 Sep 2003 Posts: 22

All this time I still can't understand why CCS rushes out to post an update of their compiler only to release another update to fix a bug from the last release, which was not there in the first place prior to the last update.
Are they trying to beat a competition of sort?

Can't they not spend a little more time to thoroughly check the update before releasing it?

That's why I can't see any value (just yet) updating until they address this issue. It causes grievance to users, what with the productivity downtime trying to figure out what the problem is only to realise that it's due to the release of a bugged compiler.

And I don't think an employer would be happy to hear that the program don't work after forking out some amount to pay for the maintenance, therefore qualifying for an update.

I've read in this forum of a guy who bought a CCS compiler, only to be provided with a newly released version that had a bug, which wasn't there in the previous version.

Guest · Posted: Thu Jan 15, 2004 7:01 pm

I'd wait at least a week before using any new version, not excusing anything, just stating fact, unless you want to be a beta test.

They (CCS), also are posting "stable" versions as well now, 3.148 seems to be the last goldern version although I never found a problem with 3.180.

They (CCS) are a small company so I imagine this method is most cost effective for them. I also use the C18 compilier from MicroChip, and updates roll out very slowly for it, although the testing does seem to be better.