View previous topic :: View next topic |
Author |
Message |
Douglas Kennedy
Joined: 07 Sep 2003 Posts: 755 Location: Florida
|
24FJ256GB210 |
Posted: Wed Nov 09, 2011 7:48 am |
|
|
The 24FJ256GB210 will accept a download via CCSLOAD and starts running correctly...the test is a simple flash a led see below.. The issue is it won't run within the CCS IDE using the CCS debugger. The code inluding the CCS debug code downloads just fine but the debugger won't start running ..the message is ...can't start check oscillator and MCLR. The diagnostics are all OK ( the OSC and Vpp are good)..the diagnostics report the xtal correctly as 8Mhz. The programmer is a ICD U64 with the software as v 4.033 firmware 2.91 hardware rev 2 ( the latest). Most of the time errors are of my own making but this one might not be.
Has anyone got the debugger to work with the 24FJ256GB210?
By the way the debugger works great with the 24HJ256GP210 that I tested in the same target board with the same test program.
Code: | #include <24FJ256GB210.h>
#include <time.h> //standard C time library
//#FUSES WPRES32 //Watch Dog Timer PreScalar 1:32
//#FUSES WPOSTS1 //Watch Dog Timer PostScalar 1:1
//#FUSES CKSFSM //Clock Switching is enabled, fail Safe clock monitor is enabled
#fuses HS,ICSP2,PR_PLL,PLL2,NOJTAG
//#use delay(xtal=8mhz) //// compiler sets fuses and PLL values automatically
#use delay(clock=32mhz,xtal=8Mhz)
#use fixed_IO(E_outputs = PIN_E0,PIN_E0,PIN_E1,PIN_E1,PIN_E2,PIN_E2)
#use rs232(debugger)
void main()
{
int8 i=0;
///// use 3.3v ICDU64 programmer
//// ETT demo PIC32 KIt board doesn't have telco pin 6 blue wire connected
char cmd;
struct_tm write_clock, read_clock;
//setup_rtc(RTC_ENABLE,0); //enables internal RTCC
setup_spi( FALSE );
setup_spi2( FALSE );
setup_timer1(TMR_DISABLED|TMR_DIV_BY_1);
printf("hello\n\r");
while(1)
{
// printf("i=%u\n\r",i++);
delay_ms(200);
output_toggle(PIN_A0);
output_toggle(PIN_A1);
output_toggle(PIN_A2);
output_toggle(PIN_A3);
output_toggle(PIN_D8);
}
} |
|
|
|
Douglas Kennedy
Joined: 07 Sep 2003 Posts: 755 Location: Florida
|
|
Posted: Wed Nov 09, 2011 4:23 pm |
|
|
I tried with the 24FJ256GA110 and the same issue. It will run outside the debugger and will compile and load within the IDE but the debugger is having issues with the OSC and MCLR. The diagnostics indicate everything is OK osc and Vpp.
Maybe this is a 24FJxxxx issue and the CCS debug code. |
|
|
Douglas Kennedy
Joined: 07 Sep 2003 Posts: 755 Location: Florida
|
Resolved by CCS support |
Posted: Thu Nov 10, 2011 11:17 am |
|
|
Thanks to a quick response from CCS support, the command
#device ICD=2 in the code is necessary for the CCS debugger to function. |
|
|
lindermat
Joined: 21 Nov 2011 Posts: 11
|
CCS LOAD not erasing PIC24FJ256GB210 |
Posted: Mon Nov 21, 2011 12:43 pm |
|
|
Hello all,
I know this may have been answered, but I have searched and can't find an answer. In my design I'm using a PIC24FJ256GB210 and I connect using the ICD1 set of pins and an ICD-U64 USB.
Everything seems to program ok, I don't get the verification error anymore (the ICD=2 issue) but I am still having problems. CCSLOAD says the hex file is fine and it says the chip programs ok and is running. It also says it's ok when I erase it, but when I click to verify it is blank, it comes back that the chip is NOT erased!
I saw someone said to run it at 5 volts, but this is strictly a 3.3volt only part!
Any thoughts?
Thanks,
P.S. In the "settings" tab it says the target voltage is 5 volts, but on the "diagnostics" tab, it correctly shows it at 3.3 volts. |
|
|
lindermat
Joined: 21 Nov 2011 Posts: 11
|
wrong fuses in hex file solved |
Posted: Tue Nov 22, 2011 12:33 pm |
|
|
Just in case anyone else is having this issue, here is the reply from CCS:
"Your chip stores the configuration words in memory in the reverse order from other chips. The CCSLOAD viewer did not account for that and showed
assumed the words were in the standard order. The effect was it showed
word 4 for what should have been word 1 and so on."
So, get version 4.127 if you have this problem |
|
|
|