Michael Rigby-Jones wrote:

>  
>
>>-----Original Message-----
>>From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] 
>>Sent: 25 November 2005 01:08
>>To: PIC List
>>Subject: [AVR] WIN AVR
>>
>>
>>What is the general opinion of WIN AVR?
>>Stable. Useful. Comparison with for-money products?
>>Code size relative to xxx.
>>Comparison with other available languages (BASIC, ...)?
>>Other?
>>
>>The price is right :-)
>>    
>>
>
>
>I have almost completed my first AVR project using a Mega 128 and WINAVR/GCC.  Initialy I disliked it because it's optimisation is poor in a few areas, especialy compared to HiTech's offerings which I have been using for years. e.g. a trival (and common) operation such as setting a bit within a multi-word variable takes something like 12-15 instructions rather than the 1 or 2 it should take.
>
>However, the raw speed of the AVR means that my usual paranoia over wasted cycles was not really justified.  Compared to the PIC I was able to write some very clean, well abstracted code and still have plenty of cycles in hand.  Also, it's optimisation is generaly very good.
>
>So far I've not come across any actual bugs in the compiled code which is a pleasant change.  The AVR Freaks forum provides pretty good support.  The latest version AVR Studio also supports GCC properly, so you can use it as a full blown IDE, though it's simulator and debugger still seem to have the occaisional problem with the .elf files generated by WINAVR (and it takes an eon to load a big elf file, a minute or so on my lowly P3 work machine.)
>
>Regards
>
>Mike
>
>=======================================================================
>This e-mail is intended for the person it is addressed to only. The
>information contained in it may be confidential and/or protected by
>law. If you are not the intended recipient of this message, you must
>not make any use of this information, or copy or show it to any
>person. Please contact us immediately to tell us that you have
>received this e-mail, and return the original to us. Any use,
>forwarding, printing or copying of this message is strictly prohibited.
>No part of this message can be considered a request for goods or
>services.
>=======================================================================
>
>  
>
I had problems with the WINAVR because I was a beginner and it will blow 
up your stack if youre not careful.  An irq will push like a dozen+ 
bytes onto the stack, and its generally a stack-glutton.  I redid that 
project in assembly to run much tighter and not blow the stack anywhere. 
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist