Notes:
1. count and marker are both volatile
2. I can get it to break with the following, as well.
if(count >250){
marker = 0; [Breakpoint Here]
count = 3;
}
It's almost like I need to have something set to zero before the
breakpoint is triggered within an if statement.
4. I get breakpoints normally when I'm not in an if statement
--- In AVR-Chat@yahoogroups.com, "englsprogeny" <englsprogeny@...> wrote:
>
> I am playing with AvrStudio. I have a cheap JTAG-ICE debugger that I
> bought on ebay.
> Item number: 300240185362
>
> The only way I can get this to hit a breakpoint [when in a loop] is to
> do the following:
>
> if(count >250)
> count = 0; [breakpoint here]
>
> Count is a loop counter. If I reset the value of count to any
> non-zero value, the breakpoint doesn't work.
>
> Also doing the following doesn't work:
>
> if(count >250){
> count = 0;
> marker = 1; [Breakpoint here]
> }
>
> Again, the only way I can get the breakpoint to consistently work is
> to code it as:
>
> if(count >250)
> count = 0; [breakpoint here]
>
> Just curious as to why this happens.
>
> Should I buy a better JTAG-ICE? Should I use something else to debug
> software? Thanks for your input.
>
> Cheers,
>
> David
>Message
Re: AVR Studio Update
2008-11-09 by englsprogeny
Attachments
- No local attachments were found for this message.