Re: pic -> avr?
David McNab <[email protected]>
| Newsgroups | gmane.comp.hardware.microcontrollers.gnupic |
|---|---|
| Message-ID | <[email protected]> |
Chen Xiao Fan wrote: > If you want to use AVR for production, please do not switch. > Atmel is one of the worst company to work with if your > annual quantity is not in millions. 8>< Thanks a million, Xiaofan, for you candid comments. The above, alone, has put me off switching to AVR. One experience I do /not/ need is to have a product gearing up for sales in the thousands, only to suffer mcu supply problems, or be told at unpredictable times that I have to re-tool and re-code. PICs aren't the most brilliant chips, but the 18F has atoned for many of the sins of the 16F and samples are abundant. Also, I've got a gutsy home-grown toolchain for it now. Thanks again. Seems I'll be staying with 18F devices for a while yet. Cheers David > > Regards, > Xiaofan > > ----- Original Message ----- > From: "David McNab" <[email protected]> > Newsgroups: gmane.comp.hardware.microcontrollers.gnupic > Sent: Sunday, August 28, 2005 9:34 AM > Subject: pic -> avr? > > > >>Hi all, >> >>I'm interested in hearing from people who use (or have used) both PIC >>and AVR devices. >> >>Particularly, 18Fxxx PICs versus ATMega32, since they have some >>similarities such as 32k program memory and 40-pin DIP availability. >> >>I've only been using PIC, and have got pretty comfortable with a range >>of PIC devices - programming them, using them in hardware, and writing >>software for them etc. >> >>However, some people have been urging me to switch to AVR devices >>instead, arguing that the AVR architecture and instruction set are way >>superior. >> >>Is AVR really worth the switch, given that I'll need to: >>- build a new programmer board >>- build test project boards >>- get used to new toolchains and instruction set? >> >>What are the practical pros and cons of AVR versus PIC? >> >>-- >>Cheers >>David > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > >