[pjc50]

Related on EE.stackexchange: https://electronics.stackexchange.com/questions/264794/how-d...

I agree with OP's "grief factor" - difficult to estimate but really critical to your project timeline.

I'm also going to advocate my "pick something" suggestion; the first one of anything you buy in an unfamiliar product area will always be wrong. This applies to computers, cars, cameras, houses, everything; when you're entering the market you won't understand your own requirements and anti-requirements. So buy something cheap and standard then use it to understand how it's inadequate for you specifically. You'll also appreciate the expensive options.

If you've never bought a microcontroller, buy an Arduino. It may not be right but you'll have a lot of company.

[fragmede]

If we're recommending pet favorites, the Raspberry Pi Zero Wireless, despite being the newest, is now my recommended "microcontroller". There are a few tweaks needed on top of the base Rasbian distro to make it appropriate for use as a microcontroller, but with a base price of $10, it's cheaper, more powerful, and has accessories (ie - anything USB with open source Linux drivers), than some Arduinos.

Built in wifi, Linux, plus USB and GPIO, means it's perfect for the device end of an hobbiest-level IoT project.

[dragontamer]

I still consider that a 'computer' and not a microcontroller.

You will inevitably need adc functionality, possibly real time clock and battery usage.

Most servos don't need wifi or Ethernet. Instead, you will usually want to be able to read a voltage and then time how long it takes for that to change.

15 cent quartz crystal and built in adcs. Bitbanging pwm from raspberry pi is also horribly inaccurate... You need a ton of shields to just run a motor with an encoder on it... While arduino can do all that around 10mA

[photojosh]

Absolutely. It makes me cringe when the Pi-class processors get referred to as microcontrollers. They are most definitely not.

If they don't have RAM and ROM on the actual chip, and need an operating system for you to do anything with them, then they're microprocessors.

The SoC cost is not a way to differentiate them either, one of our current designs uses an 8-bit microcontroller than costs more than the Pi Zero!

[joezydeco]

It's also not something you can build a production device out of...unless your margins are so insanely large that you can afford it and nobody cares.

[dragontamer]

Ehhhh... depends really.

You can easily spend around $10 on a single filter (ex: 8-pole Filter... such as https://www.digikey.com/product-detail/en/linear-technology/...). If you need an 8-pole elliptical filter, you just go out and buy one, amirite?

The "production" competitor to the Raspberry Pi Zero is honestly something like... the Octavo Systems OSD3358. At $50, you may wonder why this device is superior... but it has integrated RAM, Open Documentation, the features that are necessary for microcontroller work (ADC, DAC, PRU/Programmable Realtime Units, RTC, on-board LDO Regulator, on-board Lithium-Ion cell balancer and Lithium-Ion manager, support for TWO Crystal Oscillators, 114 GPIO, 6 UARTs).

http://www.digikey.com/product-detail/en/octavo-systems-llc/...

Its all about your REQUIREMENTs. The Raspberry Pi Zero barely does anything aside from computer things (Ex: WiFi, USB).

Don't get me wrong, the Raspberry Pi Zero is a wonderful computer. But microcontrollers are things that can work with Thermocouples, control Active Filters, and control motors. In contrast, the Raspberry Pi burns itself out if you put an LED on its weak GPIO pins... and even "Realtime" Linux can't save you from the micro-second delay associated with the GPIO pin hardware.

[joezydeco]

My point is that if I needed to build and sell 200,000 of something over 10 years, I can't order that many from the Raspberry Pi foundation and trust the piece will still be around the entire time. And if I wanted 200,000 of the Broadcom parts, they wouldn't sell it to me in that small of a quantity.

The OSD3358 is definitely the right approach, since putting high-speed impedance/timing matched DDR lines on a board to make it work right with a modern 1GHz+ CPU is a much higher level of difficulty. Plus you will also need to make your PCB 8 or 10 layers to shield the interference which increases the cost.

I thought package-on-package (like the AM335x's predecessor, the OMAP) was the way to go, but I'm starting to like the monolithic package better.

[StavrosK]

Plus no OS to update or have hacked...

[bigiain]

I'm always a little cautious with RasPi gpio - it's so much easier to accidentally fry a RasPi than an Arduino, most thing I make that need gpio at least start out in prototype stage using an Arduino to deal with io with a RasPi (or NextThing CHIP) hanging off the side if I need more computrons than an Arduino provides.

[sureshjoshi]

The "grief factor" is how I run my life :)

I agree with "pick something" with the addendum of "pick something that someone experienced you know/trust recommended after hearing how little you know about it".

[bigiain]

Heh. My "pick something" strategy almost always turns on the "What have I got sitting around that's close enough for what I need?" Sure, and STM32 or an Atmel AT8 _might_ be a better choice, but if I've got a drawer full of Arduinos and a bunch of projects with RaspberryPis in them that haven't been powered up for months - I'll go rat those bits and use them... (Last weekend, I wanted a 6dof IMU sensor - which I could have ordered - but I just used a spare quadcopter control board with a dud baro sensor, because it was there when I wanted it... I ended up using the mags in the 9dof sensors on the flight controller as well, so win all round...)