AVR-Chat

Agreed, and that's one of the nice things about AVRs over those other 
guys...as well as simplicity of developing the hardware, which isn't 
always so easy to get started with over on the dark side.

Perhaps Tom needs to set his timers to 1, any other associated variables 
to 1, and step it through from there.  As John Samperi stated earlier, a 
delay of a few mSec in hardware at 4 MHz may take a couple of hours in 
the simulator.  I use a separate include file with variables listed.  
When I'm playing with variables I comment out the desired variable 
number and enter a lower value.  That way I know what I've been 
operating on with the fiddle method.

Get it working first, then set your timers where they need to be for the 
application.

Where the heck is Kat?  Is she hiding out again?


REB




Micro Brix wrote:

>>So, there is no fundamental reason why the simulator won't do what Mr.
>>Keller needs done.
>>    
>>
>
>
>None at all..
>
>My first app in the AVR, delivered six weeks after I first saw the 8515's
>data sheet, was developed for four weeks in sim only while I waited for
>delivery of the first 8515 silicon which I still have, date code "ES"
>(Engineering Sample).  It was heavily dependent on interrupts.
>There was no difference between simulation and the real chip.
>


[Non-text portions of this message have been removed]