Sign in
Search piclist
Subscribe to piclist
piclist by Keywords
12F675 | 16F628 | 16F84 | 16f877 | 16F877A | 16F88 | 18F458 | ADC | AVR | Bootloader | CAN | CCS | CRC | EAGLE | EEPROM | ICD | ICSP | IDE | JDM | LED | Macros | Microchip | MPLAB | PCB-CAD | PIC10F | Pic12f675 | PIC16F84 | PIC16F84A | PIC16F877 | PIC18 | PIC18F452 | PicBasic | PICC | PICSTART | PWM | RS-485 | RS232 | SMT | SPI | UART | USART | USB | Wireless | Wisp628 | Xilinx
Ads
Discussion Groups
Discussion Groups | Piclist | Breakpoints in MPLAB
A discussion group for the PICMicro microcontroller. Also called the Microchip PIC, this list is dedicated to the use and abuse of this fine, simple, microcontroller. Close to topic posts are welcome, ie. general electronics.
Breakpoints in MPLAB - Basic Poke - May 23 8:57:19 2008
I am having a rough time with the breakpoints in MPLAB 8.10, using
MPLAB ICD 2 as the debugger. The debugger will often stop at the line
after the breakpoint, but sometimes right on it, and sometimes on some
other line near the breakpoint. Sometimes when I put a breakpoint on a
function call, it will stop at the function header (for example "void
InitializeMCU (void)"). And the Step-Over is really flaky too. I have
compiler optimizations turned of supposedly with the -O- option.
Is it common for MPLAB to work this way? Does anyone have any ideas on
a different IDE for Microchip products that works better? IAR for
example? I heard something about CCS, any comments?
Thanks
BasicPoke
------------------------------------
to unsubscribe, go to http://www.yahoogroups.com and follow the instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
MPLAB ICD 2 as the debugger. The debugger will often stop at the line
after the breakpoint, but sometimes right on it, and sometimes on some
other line near the breakpoint. Sometimes when I put a breakpoint on a
function call, it will stop at the function header (for example "void
InitializeMCU (void)"). And the Step-Over is really flaky too. I have
compiler optimizations turned of supposedly with the -O- option.
Is it common for MPLAB to work this way? Does anyone have any ideas on
a different IDE for Microchip products that works better? IAR for
example? I heard something about CCS, any comments?
Thanks
BasicPoke
------------------------------------
to unsubscribe, go to http://www.yahoogroups.com and follow the instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )
Re: Breakpoints in MPLAB - Dennis Clark - May 23 11:27:42 2008
> I am having a rough time with the breakpoints in MPLAB 8.10, using
> MPLAB ICD 2 as the debugger. The debugger will often stop at the line
> after the breakpoint, but sometimes right on it, and sometimes on some
> other line near the breakpoint. Sometimes when I put a breakpoint on a
> function call, it will stop at the function header (for example "void
> InitializeMCU (void)"). And the Step-Over is really flaky too. I have
> compiler optimizations turned of supposedly with the -O- option.
>
> Is it common for MPLAB to work this way? Does anyone have any ideas on
> a different IDE for Microchip products that works better? IAR for
> example? I heard something about CCS, any comments?
You must not have aggressive optimizations turned on, you'd be talking
about even more bizarre stopping points! :) Yes, this is common,
especially with compiler optimizations turned on. The cursor will
appear at the closest point it can to what you have selected. Often you
will get an error that the debugger _can't_ stop on some breakpoint
spots, that gets frustrating. I like to debug without optimizations if
I can for these reasons.
DLC
> Thanks
> BasicPoke
> ------------------------------------
>
> to unsubscribe, go to http://www.yahoogroups.com and follow the
> instructions
(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )