View previous topic :: View next topic |
Author |
Message |
rparks
Joined: 12 Jun 2009 Posts: 2
|
Using CCS Compiler with Microchip PICkit3 and MPLAB IDE |
Posted: Fri Jun 12, 2009 2:31 pm |
|
|
I like the CCS compiler very much and want to use it with my recently purchased Microchip's new PicKit3 ICD, within the MPLAB IDE.
I built and Programmed a PIC 18F4520 just fine using these tools. My problem is when I attempt in-circuit debugging. Breakpoints seem to work OK, and single-step operations also work sometimes, but when I reach the end of a loop (eg, the end of a while block), the statement pointer zooms off to the top of the source file, seeming to point into the .h file. Has anyone encountered this problem? Would an update to the latest version of CCS C help? BTW, I looked around but could not locate the version of the CCS C compiler I'm running.
Thanks! _________________ Bob Parks
Communications Programming, Inc |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Fri Jun 12, 2009 2:48 pm |
|
|
This thread might be about your problem:
http://www.ccsinfo.com/forum/viewtopic.php?t=37995
The compiler version is given at the top of the .LST file,
which will be in your project directory after a successful
compilation. It's a 4-digit number in this format: x.xxx |
|
|
rparks
Joined: 12 Jun 2009 Posts: 2
|
|
Posted: Fri Jun 12, 2009 4:19 pm |
|
|
Thanks very much for taking the time with this helpful info. I don't have these problems with the ICD-U40 and wonder if Microchip has any plans to improve this. _________________ Bob Parks
Communications Programming, Inc |
|
|
desinghjo
Joined: 04 Jan 2012 Posts: 2
|
PIC kit3 problems |
Posted: Wed Jan 04, 2012 5:29 am |
|
|
HI
am working with pic 18f26k22 and debugger is PIC KIT3 the code is compiled and it is connected to pic kit3 and target detected using debug mode.
I set a break point and i programmed and run the code but it doesn't stop at the break point,and so i manually halt the debug mode and it reached some point after that i used step in tab to step to the next place but i received a diff result like STEPPING TARGET FAILED.
can any one help for this. _________________ Singh |
|
|
n-squared
Joined: 03 Oct 2006 Posts: 99
|
|
Posted: Wed Jan 04, 2012 8:15 am |
|
|
hi rparks
If you hit single step again the MPLAB returns to your source.
The MPLAB goes to the top when it encounters some library functions or inline code.
BR
NN _________________ Every solution has a problem. |
|
|
bkamen
Joined: 07 Jan 2004 Posts: 1611 Location: Central Illinois, USA
|
|
Posted: Thu Jan 05, 2012 1:09 am |
|
|
n-squared wrote: | hi rparks
If you hit single step again the MPLAB returns to your source.
The MPLAB goes to the top when it encounters some library functions or inline code.
|
Right -- as a note, if you have the disassembly window open, I believe it will step through those points of mystery (library functions) code unlike having the 'C' code window (for the file it's in) open.
-Ben _________________ Dazed and confused? I don't think so. Just "plain lost" will do. :D |
|
|
|