Hardware breakpoints fail on LPC2106/01 not LPC2106/00

Development Boards MicroMod
1

I’ve loved working with my Olimex LPC-2106 eval board for the past year or so.

I finally made my own PCB design and built it up this week. But, it uses the

LPC2106/01 chip rather than the LPC2106/00. I didn’t think it was going to

be a big deal.

Just about everything works great: Downloading to flash, executing code etc.

However, gdb and openocd just fly right past hardware breakpoints!

Any idea as to what’s going on? Thanks!

David

Note: I’m still using OpenOCD 0.2.0

2

Well I’ve upgraded from OpenOCD 0.2.0 to 0.4.0, that was fun (not!).

(Involved libusb-win32 driver gymnastics and cfg file changes.)

My ARM-USB-OCD works well with the new setup.

The point? Code download and execution works fine, but hardware breakpoints are

still ignored on the LPC2106/01. Drat.

Next task: upgrade to latest version of gdb.

David

3

Solved:

I had been using:

reset_config trst_and_srst separate trst_open_drain srst_open_drain

I thought the srst and trst issues were board layout caused, rather than LPC silicon.

So I am now (of course) using:

reset_config trst_and_srst srst_pulls_trst trst_open_drain srst_open_drain

Well, I can say, I had the opportunity to upgrade OpenOCD and learned how to really put it

through its paces.

What a maroon! (http://www.urbandictionary.com/define.php?term=maroon)

David

4

I use JTAG hardware breakpoints on the 2106/00 and /01 via J-Link.