Thank you all for input,There is sooth in what you all say and I tend to agree. However, where does it stop?If it takes longer to write something because I don't trust any libraries I waste time writing my own. If I trust them, I may need to spend time fixing IF they break (and I know that's likely at some point). I've done just NOP loops sometimes but it's not as nice as being able to specify number of microseconds directly. I'm using my timers for other things and I don't want to add ifs when triggered either in or outside ISRs. I found that the compiler does support "__builtin_avr_delay_cycles" but the 20100110 delay.h doesn't use it; there is a new delay.h that uses it here: http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=100131&postdays=0&postorder=asc&sid=ea59a79d21c3eae4542bb467153721df I think some faith can work sometime :-) Thanks again, Cat [Non-text portions of this message have been removed]
Message
RE: [AVR-Chat] Delay functions and "__builtin_avr_delay_cycles".
2011-07-05 by Cat C
Attachments
- No local attachments were found for this message.