| View previous topic :: View next topic |
| Author |
Message |
jameszum
Joined: 31 Jan 2012
Posts: 14
|
| ICD-U64 debug not working |
 Posted: Mon Dec 10, 2012 11:18 am |
 |
|
I have been using the ICD-64 for a while now and I have a continuing problem where the debug mode won’t work. I have the following code which will load and “RUN” but will not run in debug mode. When trying to run in debug mode I get the following error. Please note that the unit would debug on Friday but won’t this morning.
This problem happens a lot with the ICD-U64 and the system will start and stop "debugging" at will.
Return error
“Could not start target: The target was not halted after reset. Check the target oscillator and MCLR. Make sure the target clock matches the clock fuse and the target is oscillating. Use View/Valid fused to find the correct clock fuse.”
The only line change in the code was between now and Friday was
| Code: |
printf("enter number\n\r");
k=getc();
|
| Code: |
//#include <BST1.h>
#include <24F32KA301.h>
#device ICD=TRUE
//#FUSES WPRES32 //Watch Dog Timer PreScalar 1:32
#FUSES WPOSTS1 //Watch Dog Timer PostScalar 1:1
#FUSES NOIESO //Internal External Switch Over mode disabled
#FUSES OSCIO //OSC2 is general purpose output
#FUSES noCKSFSM // Clock Switching is disabled, fail Safe clock monitor is disabled
#FUSES NOWINDIS //Watch Dog Timer in Window mode
#FUSES WDT_NOSL //Watch Dog Timer, disabled during SLEEP
#FUSES NOBROWNOUT //No brownout reset
#FUSES NOPUT //No Power Up Timer
#fuses ICSP3 // ICD uses PGC3/PGD3 pins pins 9 PGED3, 10 PGEC3
#fuses DEBUG // Debug mode for use with ICD
#FUSES NOWDT // No Watch Dog Timer
#FUSES MCLR // Master Clear pin enabled
#FUSES FRC // Internal Fast RC oscillator with PLL
#use delay(clock=8000000)
#use rs232(uart1, baud=9600, bits = 8, parity = N,errors )
void main()
{
long k;
setup_spi( FALSE );
setup_spi2( FALSE );
setup_timer1(TMR_DISABLED|TMR_DIV_BY_1);
while(1)
{
printf("enter number\n\r");
k=getc();
printf("this is a test %5d \n\r",k);
delay_ms(500);
}
}
|
I am checking out a new PC board and just using some simple tests to ensure that all the connections are in the correct place. |
|
 |
oxo
Joined: 13 Nov 2012
Posts: 219
Location: France
|
|
| Posted: Sat Dec 15, 2012 2:50 am |
|
|
I have this all the time.
I work from home 4 days out of 5, and it always works perfectly on the pc in the office, but intermittently on the one at home.
But.. I still have no idea. |
|
|
craigmercer
Joined: 04 Dec 2012
Posts: 2
|
|
| Posted: Thu Dec 20, 2012 11:08 am |
|
|
Hi I have the same problem happening lately. I would be able to debug each and every time, but recently I can not and get the same error message.
I even ordered a new ICD64 and it still don't work; I though that maybe because the one I used was so old that it gave out.
I am stumped! |
|
|
craigmercer
Joined: 04 Dec 2012
Posts: 2
|
|
| Posted: Fri Dec 21, 2012 11:29 am |
|
|
| I tried uninstalling all programs and reinstalling them. Once I did this it now the debugger works for me:-) |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
