On 18/08/2010 15:35, Isaac Marino Bavaresco wrote:
>
> The behavior and flexibility of the breakpoints depend more on the
> device than the ICD itself.
>
> The debugging hardware lies inside the device, and more sophisticated
> devices have more powerful debugging hardware. For instance: PIC16s have
> only very simple breakpoints, while dsPICs have very customizable
> complex breakpoints.
>
> What device are you using?
>
> Of course if MPLAB IDE doesn't expose the interface you can't use it,
> even if the hardware supports it.
>
>
> Even if such breakpoint type existed, I don't think there is an option
> to trigger it when a SFR changes by itself. What I know for sure is that
> it can be triggered when the memory position is READ or WRITTEN by the
> firmware. There is the special case of the breakpoint being triggered
> when a specific value is written to a specific address, this is the
> closest to your needs that is available.
Understood. Well I'm using an 18F8627, and just wanted to halt execution=20
if ever the SPI received anything other than say 0x55, without having to=20
write a trap in code for it. Perhaps that's what I'll do instead... the=20
unwanted character is probably just as unpredictable whether watched by=20
the debugger itself or my code.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.