about - 8 and 16 MHz - this doesn't lose precision.) by three to fit these numbers into a byte. the fractional number of milliseconds per timer0 overflow.
#define MILLIS_INC (MICROSECONDS_PER_TIMER0_OVERFLOW / 1000) Result is 16384us/16cc = 1024 us/T0_OVF the whole number of milliseconds per timer0 overflow #define MICROSECONDS_PER_TIMER0_OVERFLOW (clockCyclesToMicroseconds(64 * 256)) -> 64 clock cycles / 16 clock cycles = prescaler:4 TMR0 w prescaler:4 -> (1us/1 tick) per 64 clock cycles TMR0 w/o prescaler -> (1us/1 tick) per 16 clock cycles the overflow handler is called every 256 ticks. This is the Arduino version: // the prescaler is set so that timer0 ticks every 64 clock cycles, and the Also I haven't started to modify the micros function to tune it to work with PIC system. void function1(void) This is my first attempt with doing some modifications for lines that didn't work with the PIC. This code compiles without any problem in Arduino IDE. But these problems exist when using MPLAB, but in Arduino it doesn't, and I think the reason is that C++ in Arduino, doesn't care about returning from a void. eagle1 Yes, I know what is a void and non-void functions are. It looks like your coroutines use static variables. I took a time to understand how they work and I have a general idea, and I modified them as well. I haven't done much of a thorough testing on how they take up from the program size, but I remember they don't take much, because when the function finishes, the variables work like local variables and they expire. Eagle1 Yes, I wanted to post the method which I want to use the millis and micros.
0 kommentar(er)
