PCH and ICD2: can't get source single-step to work... ?!!

[Guest]

Hello,
I just switched from the linux PCH to the Windows version.
I'm trying to get source level debugging to work properly.
I can't set breakpoints on valid source lines, and single stepping often goes to the wrong line, and I often can't see variables ("out of scope").

What can I do about this?
Printf() debugging is becoming a time-consuming nightmare.

I was under the impression that CCS produced symbol files that mplab can use directly. Not true?

I'm using mplab 6.40 and CCS 3.182. My source code is split into several files, I have a main one that does a #include of other .h and .c files. Is this a problem?

CCS appears to have zero documentation about this (I would think) common configuration.

Help anyone?
Thanks
Jesse

[Guest]

to answer my own question...

A "driver" for MPLAB6 needs to be downloaded from CCS and installed.

Then, you can dig thru settings for the CCS compiler and turn off optimization and turn on ICD support.
It is better but still not perfect. Still problems seeing local variables in functions not in the main C file.

A tutorial from CCS demonstrating the steps required would have been very helpful. Leaving it up to users to discover on their own is not very friendly. The tutorial for mplab5 is there, and mplab 6 "coming soon". Right.

Jesse

[radian]

I have the some problem like you. May you tell me more about your decision!

I'm using ICD 2, Mplab 6.40, CCS 3.180 and new version of the driver for Mplab from CCS website.
Like you I have a main.c file that does a #include of other .h and .c files. The header files are in other directory "include".

I can debug in program memory window, but I can't debug in another one.

[radian]

My problem has solved. I switched on power from debugger to my board and switch off optimization. Now everithing is ok. - I had had a probems with power supply of my board and I think everything was from there.