#DEVICE ICD=TRUE problem

[Nevillestone]

HI
I need some help here
Ive written some code and tested it using the ICD .
Had the ICD = True through out development.
Going into production I want to turn this off but finding it affects my code IE having some slower RS232 response in the production code.

Checked the list file with ICD = True
Configuration Fuses:
Word 1: 1F8C NOEXTOSC RSTOSC_HFINTRC NOCLKOUT CKS NOFCMEN
Word 2: 1F3F MCLR NOPUT NOLPBOR NOBROWNOUT BORV24 ZCDDIS PPS1WAY STVREN DEBUG
Word 3: 3F9F WDTSW NOWDT WDTWIN_SW WDTCLK_SW
Word 4: 1FFF NOWRT SCANE NOLVP
Word 5: 3FFF NOPROTECT NOCPD

And with //#DEVICE ICD= commented out
Configuration Fuses:
Word 1: 3F8C NOEXTOSC RSTOSC_HFINTRC NOCLKOUT CKS FCMEN
Word 2: 3FFD MCLR PUT NOLPBOR BROWNOUT BORV24 ZCDDIS PPS1WAY STVREN NODEBUG
Word 3: 3F9F WDTSW NOWDT WDTWIN_SW WDTCLK_SW
Word 4: 1FFF NOWRT SCANE NOLVP
Word 5: 3FFE PROTECT NOCPD



my fuses are:
//#device adc=16
//#DEVICE ICD=
//#FUSES WDT65536
#FUSES NOWDT //No Watch Dog Timer
//#FUSES XT
#FUSES RSTOSC_HFINTRC //On Power-up clock running from HFINTRC
#FUSES BROWNOUT //No brownout reset
#FUSES NOLVP //No low voltage prgming, B3(PIC16) or B5(PIC18) used for I/O
#FUSES PUT
#FUSES MCLR
#FUSES PROTECT

Checksum is the same in both compiles
Any ideas?

Thanks
_________________
Neville

[dyeatman]

You posted this on a "solved" (closed) thread.
You need to start a new thread for this.
_________________
Google and Forum Search are some of your best tools!!!!

[Ttelmah]

I've split this off Jay.

The checksum is of the code, not the fuses. Hence no change.

However turning off the ICD should most definately not cause a slow down.
My guess would be that it is being caused by some other physical issue.
For example the ICD provides a ground, and when this is turned off
and the cable detached, this changes the behaviour. Also remember
that when the ICD is attached it pulls up the MCLR pin. Is this possibly
floating?.