Re: [avr-gcc-list] Newbie questions about Procyon AVRlib

[Chris Kuethe]

AVRlib and AVR-libc are aimed at two different layers of your software stack.

AVR-libc provides ... well... a lot of stuff that you've come to
expect from a C runtime. AVRlib provides more complicated, application
layer features - IP stack, FAT file system, GPS protocols, LCDs. All
things that have no business in your runtime library but that are
likely to be widely useful anyway. It's like GLib - lots of handy
routines, widely used, doesn't need to be part of libc.

http://ccrma.stanford.edu/courses/250a/docs/avrlib/html/index.html
http://www.nongnu.org/avr-libc/user-manual/modules.html

On Sun, Sep 28, 2008 at 1:07 PM, Clemens Koller <address@hidden> wrote:
> Joe Strout schrieb:
>>
>> I'm trying to get beyond the "blinky light" stage of my AVR (specifically
>> ATmega168) coding, and Procyon AVRlib looks like a great way to avoid
>> reinventing the wheel.
>
> I don't know much about the status of Procyon AVRlib, but I can recommend
> using AVR Libc, which might save you quite some work and it is definitely
> an active project.
>
> http://www.nongnu.org/avr-libc/
>
> Regards,
>
> Clemens
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?