Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

WHY PIC MICROCONTROLLERS

Status
Not open for further replies.

sofia

Newbie level 5
Joined
Jan 10, 2005
Messages
8
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
145
I have some experience of working on the Atmel Microcontrollers (89c51, 89c52). Whenever i am on the internet (forums, websites etc etc) or read some magzine......every1 talks abt PIC micros....i wanna know that WHATS SO SPECIAL ABOUT THE PIC MICROCONTROLLERS, what PIC microcontroller can do and Atmel microcontroller (like 89c51, 89c52) cannot.

stop using CAPS LOCK here!!!
Or do you mean to yell and shout here???
/davorin
 

I suggest you yourself find out. There are ebooks on PIC here.
89c51, 89c52 are CISC machines where as PIC are RISC machines (Harward Architecture)
with features like WDT, PWM, ADC onchip. They are faster compare to 89c51 and 89c52.
Since PIC is a RISC microcontroller, that means that it has a reduced set of instructions, more precisely 35 instructions . (ex. Intel's and Motorola's microcontrollers have over hundred instructions) All of these instructions are executed in one cycle except for jump and branch instructions. According to what its maker says, PIC16F84 usually reaches results of 2:1 in code compression and 4:1 in speed in relation to other 8-bit microcontrollers in its class.
 

I don't like PIC's 8bit uC.more dificult to program,the ONLY reason to select it MAY BE CHIPEAP than others.
 

just 35 instructions for the 16F series and you call that difficult to program???

well sofia actually PIC micros have been here for quite a while. the family of PIC microcontrollers is huge and it is still growing. a great number of people have worked with PICs and therefore there is a huge amount of code for PICs available on the internet. as opposed to the 8051 derivatives it is based on a RISC architecture so it is easy to program. if you have some experience with microcontrollers then you wouldnt have any difficulty understanding the capabilities of PIC microcontrollers. go to the microchip website and see for yourself the numerous applications where PICs are being used.

and if you have any more questions plz do ask
 

PIC, I can find some pin-to-pin compatible taiwan brand ICs (at least half price as compared to original one) to replace while I got a very few choice for 8051 ones.
 

Hi trigger74,

Please give the replacement brand with pin to pin compatibility to PICs
Thanks
g579
 

samcheetah said:
just 35 instructions for the 16F series and you call that difficult to program???
hai
I think reduced instruction set really made programing difficult rather than making it easy.just consider the multiplication of 8 bit numbers, 8051 can do it straight ,but in PIC 'you' have to do that.
PIC or 8051 , generally only a matter of choice but for certain applications one family may seem to be easier than other.
If you think PIC is faster because of 1 instruction in 4 clocks,there are 8051 derivatives which executes 1 instruction in one clock.(Cygnal).
Better to be at least femilier with both!

Picstudent
 

Here are my experiences.

I have worked with 8051's and their derivatives. No other micro family can claim as many manufacturers of compatible parts than the old 8051. The advantage was that they were all compatible even at binary level (ie the hex file from one would work in another, provided you didn't use any "special features" of the variant). All the other MCU families in general are only source code compatible.

As for 8-bit micro's - I think the nicest and the easisest to use are the Atmel AVR's.
I have tried PICs, but have been burnt too many times with the subtle differences between the variants. The variants are both the advantage and the disadvantage of the PICs. You can usually find a PIC to fit your application, but the little differences between them make it very hard to write reuseable code.


For a normal MCU project where the codeing and design cost rather than the actual component cost is the biggest factor, you simply make a general purpose board with the biggest member of the family (the Mega128) and populate it with components (like interface driver chips) and connectors as necessary for each project. You really don't need all the MCU variants unless your product is a mass produced cost sensitive item.

A real advantage with the AVR is that it was designed to be programmed in C - the instruction set lends itself to very efficient C programming. Most C constructs transform directly into AVR instructions - almost all of which run in 1 clock cycle in all AVRs.

Best of all, Atmel makes a top notch developer kit (STK-500) for US$79 and there are free (GCC) as well as low cost commercial (Imagecraft and Codevision) compilers that are very good quality (their demos are perfectly useable for most hobby applications as well - the limitations are not too severe)

PICs are popular but I think AVRs are the best 8-bit micros. If you need anything faster, you might as well go with 32-bit ARM's.
Check out www.avrfreaks.net for more info.
 

Well, when I first started using the 8051 it was said to be a RISC MCU, but since
then the PIC has reduced the number of instructions even more... :wink:

I don't regard having to use more of fewer instructions to do something, that can
be done with one instruction, as an improvement. Code written in 8051 assembler
is much easier to follow than PIC code. If one uses a high-level language this
it is of course of no importance.

I seldom see any comments about the great boolean processor operations that the
8051 has. It has 9 more bit operations than the PIC - for instance "JB" that performs
a jump if a bit is set.
Not only the registers are bit-addressable but also a part of the internal RAM, which
gives you 144 bit variables to be used by the boolean processor.
A great asset, if you know how to use it.

Just my two cents.

/Rambo

PS And yes, I like Pascal too. :wink:
 

Check this link for one of the brand: **broken link removed**
where you can replace PIC (low grade versions).

But you need software to change the code into their format and use OTHER programmer to program the chip, for example, Hi-Lo system ALL-11 series universal programmer.

There are other brands also can do the same but I forget their exact brand names, something like EMC, madison.......
 

sofia said:
I have some experience of working on the Atmel Microcontrollers (89c51, 89c52). Whenever i am on the internet (forums, websites etc etc) or read some magzine......every1 talks abt PIC micros....i wanna know that WHATS SO SPECIAL ABOUT THE PIC MICROCONTROLLERS, what PIC microcontroller can do and Atmel microcontroller (like 89c51, 89c52) cannot.

stop using CAPS LOCK here!!!
Or do you mean to yell and shout here???
/davorin

Because the pic micro are easier to find on the market
 

sofia said:
I have some experience of working on the Atmel Microcontrollers (89c51, 89c52). Whenever i am on the internet (forums, websites etc etc) or read some magzine......every1 talks abt PIC micros....i wanna know that WHATS SO SPECIAL ABOUT THE PIC MICROCONTROLLERS, what PIC microcontroller can do and Atmel microcontroller (like 89c51, 89c52) cannot.

Im not looking to start a "uC War , and i dont know the specs of the latest pics like the DsPic" but IMHO the Atmel AVR is much faster than the pic , has same features like timers,pwm,hardware-I2C , SPI , more Ram/Flash , has Free development via GCC , has an excellent Simulator Free.

As i see it PIc came first and has a tremendous code base , and Microchip has made many more usable APP-Notes (he..he) even i sneek over there to get some for some of my AVR projects.

I chose AVR and will prob soon also do ARM , and i have not regretted it.

And have a fine functional FREE development suite.

/Bingo
 

I would reformulate your question as follows:

Microchip is becoming ubiquitous in the media... what does Microchip have than Atmel (or whatever) doesn't ?

so, the answer comes implicit in the question: A MORE AGGRESSIVE MARKETING STRATEGY.

sorrry for the caps... you shouted first!. :)

Regards
 

I guess that the success of the PIC was that Microchip was the first to provide:
- A single chip MCU with almost no external parts.
- EPROM and OTP parts. And more important an EEPROM part (16c84)
- Easy to program with full info. on the programming algorithms. including an app
note describing a simple programmer.
- Good datasheets online.
- Free development tools online.
- Cheap parts.

This made it possible to get the chip for a few dollars, build a programmer for a few more, download the MPASM and start making proyects. Perfect for the thousands of experimentors who where waiting for something like this.
 

Bingo600 said:
Im not looking to start a "uC War , and i dont know the specs of the latest pics like the DsPic" but IMHO the Atmel AVR is much faster than the pic , has same features like timers,pwm,hardware-I2C , SPI , more Ram/Flash , has Free development via GCC , has an excellent Simulator Free.

As i see it PIc came first and has a tremendous code base , and Microchip has made many more usable APP-Notes (he..he) even i sneek over there to get some for some of my AVR projects.

I chose AVR and will prob soon also do ARM , and i have not regretted it.

And have a fine functional FREE development suite.

a "uC war" will initiate whenever you talk about compairing between PIC, 8051, AVR or any other microcontroller. its just natural :D

ill tell you how. look you said that AVRs are faster than PICs right???? and thats why you have decided to choose AVRs over PICs. but believe me you usually dont need speed in control applications at all. most of the time the microcontroller is waiting for you to do something or wasting clock cycles. of course there are exceptions where you need speed. but plz dont compare the working of microcontrollers to Intel or AMD microprocessors where you have to run and OS, do multitasking and that type of stuff.

see how that works???? for everything you say for AVR there will be someone to prove it wrong. and then you will say something else and this process will go on. such discussions usually go upto 3-4 pages before the moderators warn the memebers and delete the discussion :D

so what should you do then?? well just do what makes you feel good. if you want to work with AVRs then do so. if you feel that AVRs do the job you want to do then go for it. its just a matter of choice. all microcontrollers can do everything imaginable in one way or the other. so just pick one and start building projects.

have fun
 

Yeah... I agree, selecting a low-end MCU usually is a matter of choice.
Personally, what makes the decision is the feeling I get when I put my hands on the evaluation toolset, and ask myself "how much will I pay for this piece of shit?"
 

samcheetah said:
a "uC war" will initiate whenever you talk about compairing between PIC, 8051, AVR or any other microcontroller. its just natural :D
..
..
so what should you do then?? well just do what makes you feel good. if you want to work with AVRs then do so. if you feel that AVRs do the job you want to do then go for it. its just a matter of choice. all microcontrollers can do everything imaginable in one way or the other. so just pick one and start building projects.

have fun

Verry well spoken(written) ...

I do agree :)

I wonder if one of them are going to release a lowcost mcu with an ethernet PHY
like the Rabbit but , for a PIC/AVR.
But then again ethernet might be a better job for ARM , and i do see a lot of those popping up at low prices.

/Bingo
 

Re: Other way to see this...

Perhaps, what matters is how you did approach micros.

In my case, I started with the Z80 and I was happy to have so many instructions doing so many things (except brushing teeth...).

Later the 8052 with an also complete set was a joy, even more with the fun of using BASIC.

After so many years inactive, because going at sea for long periods I run across PICs and a reduced set struck me as so nice so I jumped into this train.

After investing (time and efforts) plus an expensive but not fast at all Picstart programmer I will stick to PICs perhaps for some time before looking outside again.

They have loads of erratas, some awful things like "read-modify-write" for output ports but is what I've learnt to live with.

Years ago, I asked one contributor in another forum, about how he selected micros. He is an EE designing for a major company and he didn't talk about preferences. Not at all. He mentioned convenience, availability or performance based on a list of features for each brand.

Even if I tend to feel like I am a PIC fan I find that this is not a religion.

Starting a war on this or about "C and assembler" is wasting time.

Being able to afford more expensive lines I would like to give a try to something on the 16 bits field.

My idea, don't spend time. Choose one and go.

Happy programming to you all!

Buena suerte

Agustín Tomás
 

Hi All!

I personally prefer the AVRs especially the ATMega series.
But I also use 8051/52 and verry seldom Pic mcus.

If I want to rebuild a project, then of course I would not convert the original code to fit into an AVR, instead I use the opportunity to broaden my horizon and use the mcu the developer has used, study the code and think is this a better mcu than my loved AVR.

Till yet the answer was no, but time will tell a different story maybe,...

And there is also a special AVR forum which I really like, at least until the made a redesign, somedays ago,...

Cheers
Rubi
 

as a joke, 2 very good reasons to prefer PICs:
- free samples available (sorry for AVRs)
- huge lots of projects with source code on the internet
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top