On Sun, Apr 18, 2010 at 11:00 PM,  <[email protected]> wrote:
>>> feature allows breaks upon an access across a range of addresses.  However,
>>> theOpenOCD wp command does not support this
>>
>>In what sense "not support"?  I hae certainly configured and used OpenOCD
>>watchpoints with of 64 KByte size, thus, "a range of addresses".  (And ISTR
>>larger ranges, where hardware allows.)
>
> Does the size argument to the wp command refer to the size of a block of
> memory? I assumed it meant the size of a single access (byte, half-word, or
> word). Ditto for the size argument to the bp command (2 for thumb mode, 4 for
> arm mode). Indeed, the xscale implementation of wp returns an error if not 1,
> 2, or 4. And the same code subsequently ignores that argument, so if size
> refers to a memory range, xscale doesn't support it. If my interpretation of
> the argument is incorrect, perhaps the correct remedy is to use the mask
> capability of the xscale debug hardware to implement the command correctly.

I don't know this code well enough to say what the size is for, but I believe it
is for 1, 2 or 4 bytes. How the mask is then used, I haven't read up on.

> I'll take a look at the implementation in other targets. It would be good to
> patch the documentation to clarify the meaning.

I think both documentation and code could do with an overhaul here....

-- 
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html


Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to