This may be somewhat contrived, but I'm going to use an illustration. Let's say you're building a desktop computer for yourself. Now, one way that you could go about do this is just to visit a site that distributes components (e.g. Newegg) and browse CPUs until you find one that you want. Then, find a motherboard compatible with the CPU that you like. Then build off that. Before you know it, you'll have chosen all of your parts.

Back to electrical engineering: often, I'll know "what kind of part" I'm looking for, and have a vague idea of what specs it should have. But simply doing a search on a components site (e.g. Digikey) will often yield tens, hundreds, maybe even thousands of results. This is staggering for someone like myself who has little experience, as it would be difficult to distinguish an appropriate general-purpose component that I could use.

How would one with little experience go about picking a central IC around which to develop one's project (assuming that such a design is appropriate)? Are there any resources that have lists of such useful or simple or commonly used ICs (transistors, op-amps, micrcontrollers, etc..)?


I think everyone probably has these thoughts at some point.

There are books/sites which recommend a bunch of "useful components" to have available. The only trouble is these things go out of date very quickly. For example the 741 and PIC16F84 are still being recommended in places even though they have both long (long long) since been surpassed.

If you know what is needed spec wise for your project (as you should do) then you can pick the components based on the specs. For example if you need 10MHz analogue bandwidth and you are using a 5V supply then you can filter opamp results accordingly. What speed does your uC need to run at 10MIPS? 40MIPS? what peripherals does it need? USB? SPI? CAN? Filter accordingly. Parametric searches are your friend here (all the decent sites like Mouser, Farnell, Digikey, etc have them)
This applies to just about everything, so there's no quick way around reading through datasheets and making an informed decision (unless you already used the part of course)

So I would say the answer is probably to jump in head first and start learning how to use the search tools properly (look at any help available) picking your way through the components, read the datasheets, learn about what the specs/graphs/etc mean.

I certainly remember being overwhelmed by all the different options and long winded datasheets, but after a while your brain gets pretty good at filtering out the info you need quickly. Still takes time though, and is not the most enjoyable task.
Of course, if you're sure of the specs and you can get someone else to do it for you that's always a good option ;-)
Keeping up to date with new chips is useful too, I sign up for all the new product notifications for various places.

  • 2
    \$\begingroup\$ It's very time consuming and can get very tedious. Sometimes (especially for one offs) I just pick a component that looks good and will do what's supposed to easily. This usually requires 'overdesigning' some circuits a lot. Picking components and balancing/restructuring designs can be so difficult, well time consuming, and is only worth it on big runs. Here is some more info, though it's on 'large scale products', on how to look for parts: youtube.com/watch?v=Qjj49bFimoo \$\endgroup\$ – Hans Dec 30 '11 at 16:22
  • 1
    \$\begingroup\$ If you think you've specified all your parameters, check out the datasheet for the cheapest part - that's an easy way to sort. \$\endgroup\$ – W5VO Dec 31 '11 at 3:20
  • 1
    \$\begingroup\$ I hope that, since it's a wiki and therefore easier to update when better parts make old parts obsolete, the list of popular parts will stay up-to-date. \$\endgroup\$ – davidcary Jan 2 '12 at 21:18

I'm going to answer this question from a very specific point of view: an electrical engineer designing something for volume production. And I define "volume production" as 1,000 to 10,000 units per year, and in production for up to 10 years. I know that this doesn't apply to many of the people here, but I think it should be interesting and informative none the less.

There are two parts to this: finding a selection of parts that would work and picking the correct part from that group.

For finding the right part I uses a variety of sources (in order of decreasing importance): My own knowledge of manufacturers and parts, information from manufacturer reps/Distributors/FAE's/Etc, searches of manufacturer web sites, and random things read from trade magazines.

For picking the right part I have to weigh many factors, including (in no particular order): cost, availability, second sources, what we use for other projects, how long we think that chip will be manufactured, how useful the rep/distributor/FAE is, and of course the performance/features of the chip itself.

Let's say that I have to design an MP3 player. For that I need a CPU, Flash, USB interface, and an audio output (I'm ignoring power).

The CPU should be a 32-bit CPU with interfaces for NAND Flash, an audio DAC, and USB interface. I would first narrow it down to a CPU architecture and a couple of manufacturers. For ARM, I would mainly look at TI. Freescale makes ARM stuff, but I hate their development tools so they are out. Analog Devices has a DSP with integrated audio DAC that could also be worth looking at. But let's go with TI. TI's web site has a nice CPU selection guide that would narrow it down to maybe 4 or 6 chips. Using that, and by talking to TI's FAE and distributor I would select one from the 4 or 6.

Finding NAND flash is somewhat easy. There are only about 4 manufacturers worth talking to, and 2 of the 4 don't work well with these "low production volumes". I'd just email the local rep/FAE/Disty with my specs and have then recommend parts. From that I would select the part to use.

Almost all of the USB interface circuitry should be in the CPU itself. Any external circuitry will be documented in the CPU datasheet and application notes. I'd just copy that. Any critical components would have been selected for me.

Reasonable audio DACs are only made by 4 companies: Cirrus Logic, TI, AKM, and Wolfson. Since this application isn't critical, any manufacturer is just as good as any other. Since I already use a Cirrus Logic DAC in another project, I would use that same part for this one. But if I had to choose, I'd search the mfg web sites to narrow it down. Then, getting quotes and opinions from the various distributors would give me the final info.

The audio output also needs some analog parts (mostly op-amps). Experience tells me which ones to consider, but there are lots of stuff on the various manufacturer web sites to help with this. Also the FAEs could be a huge help here. Honestly, choosing an op-amp might take longer than selecting the CPU! It might make sense to choose several op-amps from different mfgs that have the same package and pinouts-- so we can try different chips in the prototypes and select the best one.

From start to end, the parts selection process for this MP3 might take 2 calendar weeks. 3 weeks if you add the power supplies and battery charger. Most of this time is playing email tag with the various people, so other valuable work happens during this time. This sounds like a long time, but a mistake at this point could cost tens of thousands of dollars. It's worth taking the time.

  • 2
    \$\begingroup\$ That was quite interesting to read. As you say, I most likely won't be producing thousands of units anytime soon, but it is interesting to see the process from the perspective of the professional industry. \$\endgroup\$ – voithos Jan 2 '12 at 4:33

As others said, for one-off designs, it is not really worth spending a lot of time to absolutely minimize the cost of your design. And if you are, for example, already familiar with a particular uC family, then it often is perfectly valid to just stick with that family if it will do the job.

But if you are truly confronted with dozens or more of parts that meet your needs, then sorting by price and taking the lowest-cost one is a reasonable approach. At the very least you will gain some familiarity with a relatively low-cost part that you might be able to use on a future project where cost does matter.


Like Oli said, everyone goes through this phase, some stay in (and enjoy it!).

First note that, unless you are designing for a large production run, it does not matter that much how effective your design is. If you know the chips that can do it, it is often not worth the trouble to spends hours and hours to reduce your design from 10 to 8 chips and from $20 to $16. This (in part) explains the abundance of 741, 555, and 16f84 designs, and why PIC users almost never consider using an AVR and vice versa.

If you are designing for large volume, or are doing more or less the same type of design over and over (let's say a uC + USB interface + H bridge) you should pay attention to others that have designed similar circuits, to new product announcements, etc. In my experienxce this comes almost automatically, but it takes time.


I've found searching for a type of part, without having a specific part number, at places like digikey to be almost entirely useless.

However, if you go to some of the manufacturer's pages, almost all of them have filters to help you narrow down which parts match the specs you are looking for.

For example, STMicro has their parameteric product selector at http://www.st.com/stonline/stappl/productcatalog/app?page=productSelector - you choose the type of device you are looking for, then filter them out by voltage, package, and whatever other specs you need.

It helps to know which companies actually make the type of IC you're looking for. For most parts I take a look at STMicro, Texas Instruments, Maxim, and National Semiconductor. As an added bonus, all four of those companies will send you free samples of most of their products. They even pay the shipping. So even if you aren't sure the IC will work for your purposes, at least it won't cost you anything to find out!

And as others have said, don't worry about getting the absolute best part if its for a one off project or prototype. It's just not worth spending an hour agonizing over the difference between two almost identical parts.

  • \$\begingroup\$ Your list of vendors must reflect the details of the types of designs you do, but it seems strange if its a recommendation for a "universal" list of go-to vendors for hobbyist projects. TI is a great start for analog, power, logic and DSP. National is a good source for well-understood (80's-era) analog, as well as very specific newer products, and anyway its now a part of TI. Strangely, Nationals parts now seem to be included in TI's product search pages, but not vice versa. ... \$\endgroup\$ – The Photon Dec 31 '11 at 17:34
  • 1
    \$\begingroup\$ Maxim and ST on the other hand, each have fairly "quirky" product offerigns. And none of these is a great starting point when looking for a microcontroller for a hobby project. \$\endgroup\$ – The Photon Dec 31 '11 at 17:34

What you don't know kills you.. Don't assume parts conform to the specs and bug free.

For CPU stick to what you know. For example a prominent ARM supplier has a nasty bug in some of their ARM families that the internal flash doesn't retain data well. (Here-say info from a trusted source, so we didn't even evaluate, moved to a more proven part) So stick with proven parts for something like CPU because it would be messy to change. Pick this first. (Brains first)

Get an eval kit for anything. I like TI for anything analog and power and ST for CPUs. Just ask them to give you the eval kits and try to build the whole thing using eval kits, this is usually possible.

Stick to less number of suppliers, easier to deal with, increases your total worth of $ for the vendor hence better pricing.


protected by Nick Alexeev Apr 16 '17 at 3:24

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.