PIC or ATMEL

Status
Not open for further replies.

Many people are willing and capable of working on a diversity of projects. All it is is another architecture, nothing more nothing less. Anyways, the AVR architecture is simplistic, the transition between the two is nothing more than remembering what registers to use and looking up different mnemonics.
 

What seems to be the problem?
 
The title of this thread should be something other then "PIC or AVR". That indicates one or the other. Had you used a more fitting title you have have saved some grief.

AtomSoft said:
Ok why is everyone basically assuming i am stupid or something?
Never give anyone that sort of opening

Your Original Post said:
I was thinking about also jumping into ATMEL.

I know this wouldnt be a smart idea since im new to pic and might get them mixed up but ATMEL looks very interesting.
You knew up front that it was an iffy idea for a beginner.

As Salgat pointed out you will learn little of value by including the AVR. You will learn the GUI and it quirks, how to use the other tools. Most everything else you can learn on a PIC or an AVR. Given that you are already using PICs there is no good reason to take up the AVR unless you intend to switch. The tool chain specific skills go out of date faster then most any other uC skill.

When you are ready, you can find variety by moving to the advanced PICs. All the spice you want and no need to learn another tool chain.

You will have a hard time finding a person teaching the subject, who thinks adding AVRs at this time would be the way to go.

I can only speak for myself, I do not think you are stupid.

EDIT: Learning a computer language other then ASM would be a good thing.

In regards to Eagle. Use the tutorials you find online. When you have a problem post it here and we can get you unstuck. A lot of us learned that way. As much as I like Eagle it takes getting used to.
 
Last edited:
AtomSoft said:
Ok why is everyone basically assuming i am stupid or something?

Well, I think you are not aware of the fact that most of the great guys hanging out here are using PICs. Its the same situation in AvrFreaks.net where most of the guys there are using AVRs.

You have committed the cardinal sin of provoking people which have a strong special interest towards a particular product and you definitely got their reactions. Likewise if you post a message with title "PIC or ATMEL" in the AvrFreaks.net you will get the very same response. I'm not a bit surprised.

I started with PIC and I use AVR too, but I have never ask the "PIC or AVR" question in the forum.
 
Lol i guess i should have known this would happen tho but... as i said before i just wanted opinions not people trying to tell me what i not capable of doing.

Anyway i have made my decision to of course stay with PIC while having a affair with AVRs.
 
LOL...
It would be impossible to give a reasonable answer to your OP without taking skill level into concideration. It should not have upset you.
 
futz said:
Limiting yourself to just one MCU type is just that - limiting. Try em all. See what they're like. Why not?

Off topic:
Very true. Wish schools and businesses would have this sentiment for the m$ universe.
 
Last edited:

The PICkit2 cost about $35. It provide both program and debug capability.
Now it even has "program-to-go, programming without a PC" feature and can work as a logic tool.
 
I use and have used both for commercial and pet projects. The PIC is vastly supported. The AVR has a free and very powerful C compiler. I am currently developing an AVR32 application. I like to use the GNU toolchain because I can develop and test my code on a linux or windows machine and even use GCC tricks and not have to worry about whether the AVR compiler will take them. It just isn't practical to develop large applications in ASM anymore so the value of the toolchain should certainly be a consideration if you expect your applications to have a significant code base.
 
Status
Not open for further replies.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…