AVR-Chat

On Apr 15, 2005, at 6:43 PM, Chuck Hackett wrote:

> Well, I discovered part of my problem.  The program I'm working with
> was originally written for the ImageCraft C compiler and I'm using
> WinAVR(gcc).  I tried to convert everything as well as I could but
> apparently something I don't understand is going on because I
> downloaded the trial version of ImageCraft V7 today and the program ran
> the first time!  I'm thinking that it has something to do with the
> differences in support for stdout (usart) but I haven't nailed it down.

I see a different religious thread there, that of casually using 
library stdio, malloc, etc, in an embedded application. I'm against it. 
Your project may be, "written in C", but its running in a totally 
different environment than a Unix server.

Before committing to avr-gcc for my current project, and my employer's 
future, I spent a good bit of time looking at the code it generated, 
the mechanism for supporting IRQ, and the startup code before main() 
was called. Avr-gcc passed.

Recently my project was in need of memcpy(). I added the required 
#include, made my call to memcpy(), and before trying to run code the 
first time dug into the output of avr-objdump -DS to see what got 
added. Again was pleased at what I found. Was better than writing my 
own, which I would have left in C because its not important enough to 
my project to create my own. Normally, and I still may do so, I'd copy 
the source out of the library and place it in my project rather than 
link against a provided library.

--
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.