AVR-Chat

Since you know exactly when it trips, set up the simulator to break a couple
hundred cycles prior to the fault and single step your way to bliss.
Eventually you will see the error.

-----Original Message-----
From: David VanHorn [mailto:dvanhorn@cedar.net]

>
>Include an extra instruction in the Stack_Check just to force the
simulation software to use different size of memory, etc, and see if the
problem happens again at 6513 count.


Even more fun, I put an extra NOP in the main loop, with the main routines
enabled.
What would you guess?

I start the clock at reset, and let it run till I hit panic.

Without the NOP, 55074 uS every time.
With the NOP, 34594uS every time.
Two nops, 38609, every time.

I'm not seeing a pattern here.