Another quick question, is there anyway to work around these issues by say creating your own libraries for these instances?
My assumption is that since it is so much easier to use, that you must lose something.So, my question is what do you give up by using Arduino vs. straight up AVR through one of the above mentioned methods?Do you lose speed, do you lose some flexibility?Any comments would be appreciated.
The most obvious is digital write vs PORT, digital write might take 40us PORTB |= (1<<PB2); might take 4us. Or lets say you want to talk to a serial device that uses odd parity, you might have to go out and tickle some registers manually.QuoteAnother quick question, is there anyway to work around these issues by say creating your own libraries for these instances?yea theres nothing stopping you from dropping AVRGCC (which is not the same as whats used in studio, but its AVR and C++) or ASM code in the middle of an avr sketch or library other than its harder for average users to read / change, and narrowing portability (like registers dont always stay the same in different AVR's)
not that I am aware of i2c supports normal and fast mode, serial supports 2400-115200 baud out of the box, with people pushing that up to 1Mbps, since they use the internal hardware