You are better off using avr-gcc and avrdude directly when programming an attiny.
Quote from: smeezekitty on Dec 30, 2011, 09:22 pmYou are better off using avr-gcc and avrdude directly when programming an attiny.Why?
What I do continue to wonder about however, is, are there avr-libc alternatives that are smaller / lighter, which probably break-down the functionality in avr-libc into smaller modules, s.t. you can save on program memory on the extremely tiny attiny's like attiny13 ?
I see that Arduino-Tiny google-code pages seems to allude to support for attiny13's
Sofian Audry and Samuel St-Aubin published a '13 core... http://accrochages.drone.ws/en/node/38
(figures as one of the search tags on the project)
Is that a reality ?
Or is attiny13 one of those AVRs which cannot be programmed in C ?
I see that Arduino-Tiny google-code pages seems to allude to support for attiny13's (figures as one of the search tags on the project). Is that a reality ? I don't see an option in the IDE, so thought of asking.
@falcon74, I'm not sure what you exactly look for as "more optimal libraries",
but you could take a look at the work done by the "MHV" guys (make hack void) in Australia. I believe they did some kind of optimisations. Not sure what kind, nor on which libraries, though.
Well what I meant is based on an impression I've formed (without deep insights) reading various posts is that Arduino libraries are often, not the most optimal because of the fact that the software tries to cater to several AVR uC's, with varying parametrics/functionalities. A solid case in point, which I've encountered first hand is the difference between "DigitalWriteFast" lib and the standard Digital I/O library bundled with Arduino (or as part of the core).