AVR-Chat

I notice that just before the crash you are setting the device pinb5 to an output pin, is the pull up enabled when set as an input ?

Might be an idea to insert an intermediate state, might possibly be getting a vcc to 0v power short, (see section 12.2.3 int the datasheet) this could be giving you the glitch, what is the PORT REG value before you switch to an output ? Is an intermediate state required ?

Regards

--- In AVR-Chat@yahoogroups.com, David VanHorn <microbrix@...> wrote:
>
> On Sun, Mar 29, 2009 at 5:48 PM, Jim Wagner <wagnerj@...> wrote:
> > Hmmm. ...
> >
> > Can you set a "variable watch" that triggers on a memory value that
> > should not change but IS getting changed? I don't remember if Studio
> > has that.
> 
> I have that in code, no triggers.
> 
> > Another possibility is that you are getting a corrupted stack (ie,
> > unmatched push/pops or something that writes into area used by stack)
> > and you are returning to a place in ROM that is the middle of a two-
> > word instruction so that everything subsequent is really messed up.
> > Been there, done that!
> 
> Yup, I have a stack guardian, it's not hitting that either, and when I
> look at ram, it looks ok.
> >16 bytes free between the bottom of the stack and the guardian.
> 
> 
> > Jim
> >
> > On Mar 29, 2009, at 2:23 PM, David VanHorn wrote:
> >
> >> I added a full vector table, and every entry for the unused ints sets
> >> "sanity_flag" to some unique value.
> >> There's a task that checks sanity flag for any non-zero value, and
> >> it's never triggering.
> >>
> >>
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> 
> 
> 
> -- 
> There is no computer problem which cannot be solved by proper
> application of a sufficiently large hammer.
>