Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
Discussion Groups | LPC2000 | CrossWorks Debugger loosing breakpoints?
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
CrossWorks Debugger loosing breakpoints? - Markus Zingg - May 10 18:29:16 2008
Hi Group
When I debug in CrossWorks (Release 1.7 build 6) I often loose all the
two hardware breakpoints. With "loose the breackpoints" I mean that even
though NO breakpoints (or only one) is set, CrossWorks tells me that no
more breakpoints are available.
It most often happens when I either hit a breakpoint that was set and
then try to singlestep (even though only ONE breakpoint is used) or if I
use previousely the "run to" (with no other breakpoint set) and then try
to continue.
Is this a bug or am I doing something wrong? Does it eventually relate
to the JTAG dongle I'm using (AmonTec JTAG tiny in my case).
TIA
Markus
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
When I debug in CrossWorks (Release 1.7 build 6) I often loose all the
two hardware breakpoints. With "loose the breackpoints" I mean that even
though NO breakpoints (or only one) is set, CrossWorks tells me that no
more breakpoints are available.
It most often happens when I either hit a breakpoint that was set and
then try to singlestep (even though only ONE breakpoint is used) or if I
use previousely the "run to" (with no other breakpoint set) and then try
to continue.
Is this a bug or am I doing something wrong? Does it eventually relate
to the JTAG dongle I'm using (AmonTec JTAG tiny in my case).
TIA
Markus
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )