evandude said:
If I was starting from scratch I am not so sure which I'd choose.
After using both, I would recommend PIC to new comers, no doubt. It has much less to learn when one is starting. The whole programming setup is in one HEX file which includes object code, configuration fuses settings and possibily EEPROM data. While in the AVR camp, programming are done using separate files. The AVR fuse configuration issues may take longer time to fully understand the gotchas hiding in the back.
evandude said:
I chose PICs long ago because it's what people around me used, primarily, and I had hardly heard of AVR's. Today, I am constantly seeing all sorts of great projects built with AVR's, and it seems like they've got a huge user base (like avrfreaks.net)
I can think of several reasons:
a) AVR got what PIC have, priced about the same as PIC but upto four times faster than a PIC at the same crystal frequency
b) A free and very powerful GCC C ompiler for the AVR family
c) easy to make programmers with full details, parallel port based, serial port based or even USB. Most of them use no 12V involved, suitable for all(well most) AVRs.
d) simple, easy to build JTAG (the equivalent of ICD2 in AVR world) debugger
evandude said:
Again, take this all with a grain of salt, I've got no real experience with AVR's, just PICs, but just know that I'm certainly no AVR evangelist (nor PIC evangelist, for that matter)
I like both. They have their pros and cons under different situations. One don't have to choose to stick to one particular type.
@Sceadwian:
You keep recommending the M8, which does not have any debugging setup up available for it except using real ICE. Any reason why not the M88 as it is about the same price, pin compatible, same size Flash/SRAM/EEPROM and comes with debugwire features.