Am 23.01.20 um 23:25 schrieb Joerg Wunsch: > As Britton Kerin wrote: > >> I guess the high-res maximums are 262.14 ms / F_CPU in MH for >> _delay_ms() and 768 us / F_CPU in MHz for _dalay_us() regardless of >> the availability of __builtin_avr_delay_cycles(), but >> the way the _delay_ms() and _delay_us() descriptions are written this >> is not entirely clear. Am I correct? > > I think you are. They work beyond that now (has not always been the > case) but lose a bit of accuracy/resolution.
For a calibrated busyloop see https://github.com/Traumflug/Teacup_Firmware/blob/master/delay-avr.c Accuracy is described in comments there. Markus -- - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/
