AVR-Chat

>
>With complex systems like this, I've always found tracer tags to be
>very useful, proving that it's operating the way I think it is.  In
>this case, if you have a spare port, or even just a pin, use it to
>indicate where in the code things are.

We've done a bit of this, unfortunately, it's probably a bad pointer.


>If that doesn't work, then expand the logic analyzer.  Keep the debug
>pin operation as above, but track the address/data lines to the
>sram.  Flag every time a write happens to 0x3b1, and verify that the
>debug pin is being toggled around it.  This will prove that the
>writes are or aren't happening at places in code where you expect
>them to be happening.

Did I mention that it's internal SRAM?