Ask HN: How to start learning embedded systems?
I am interested to dive into embedded systems. I am proficient in C++ and python. I am seeking some advice for best path to take for learning embedded systems.
Thank you for any advice (in advance).
Arduino with C++ appears compatible with your experience. But you might find the edit, compile, download, debug cycle rather tedious.
ESP8266/ESP32 with microPython provides REPL so is faster for experimentation and learning. For many projects it might sufficient.
RaspberryPi uses the SDcard like a "traditional" file system. Repeatedly losing / switching-off power without doing a shutdown has destroyed several cards for me. Besides, Real-time control is simply not really feasible. I agree with @bigiain, using Arduino with RaspberryPi is often a better approach. But it does require more development and debugging.
MCP23008 I/O expanders are VERY useful. Seriously recommended with ESP32 and RaspberryPi when you run out of pins.
All of the above are good for learning and small volume products.
Industrial systems tend to use ruggedized SBCs and RTOS. Linux is too bloated and non-deterministic for most real-time applications.
Large volume products are more likely to be designed from the ground-up using individual microcontrollers and support ICs. At this level you will need experience with assembly language, etc. The development cycles also often use the silicon vendor's tools.
IMHO RISC-V is going to become widely used. It is already available as a microcontroller ISA and some low-end Linux boards. If you are focused on learning, then I wouldn't invest too much effort into low-level architecture issues with ARM based SoCs. Of course, if you get to work with them professionally, then that is a very different proposition.
It’s very affordable and you can program it in C/C++ and Python. There are lots of projects on the site as well. You might also enjoy HackSpace magazine. Free downloads of issues are available at https://hackspace.raspberrypi.org/
pick one of the three big ones (raspberrypi, arduino, esp*)
My suggestion is think up or choose a project you think might be fun, then work out (or ask for advice) on which of those three choices is most suitable, and go learn how to build it.
Python is the language of choice there, too. So for the most part, you'll feel at home.
Micro Python and Circuit Python will run on a lot of the same boards Arduino IDE works with, but it's a much much smaller scene then Arduino/C++ I think.
C/C++ should probably outperform Python. Either way, op should feel at home, since they listed both languages.
In my view - and in the non-industrial/hobbyist/prototyping end of that space, I kinda divide things into "micro controller projects" where Arduino is king (but with other no-OS hardware platforms like ESP32/ESP8266 and many others, and other IDEs like Platform.io all playing catchup in market share) - and "embedded linux projects" where Raspberry Pi is similarly king but with many alternative linux capable SOC boards available too.
The Arduino/microcontroller path uses a form of C/C++ mostly (if you stick with Arduino IDE) but also MicroPython and CircuitPython. I consider this a "bottom up" approach to building computer controlled projects. You don't get Linux along with all the standard tools and utilities, you start from the event loop and write or import everything you need. This is often better for simple projects (blinky lights, PID controllers, simple automation, those are the sorts of things I've build that way), and for real time critical projects (like quad copter flight controllers) where linux on RaspberryPi can't guarantee you get the code paths running exactly when you need them. (RTOS on SOC board like RasPi solve those problems, but are a much smaller community and hence have fewer easily findable resources and examples, and also I haven't got any real experience with those (yet?))
The Linux/Raspberry Pi path - at least for me - usually gets taken when I've got ideas about some code I'd normally run on Linux, but want to do on a small machine or in a remote location with battery power. Probably 80+% of what I've built using Raspberry Pi starts out as some python or perl code (yeah, I'm old...) that I want to either run in a weird location (like in my garage, on the top of a mountain with a solar panel, on a camper van), or that I want to run as a low power inexpensive single use linux system (like my Pi Hole and my small media server).
When things get complicated, those two approaches often merge. A Raspberry Pi running python ro similar connected to an Arduino doing GPIO is a super common thing. Raspberry Pi (and most other Linux SoCs have 3.3v and fairly fragile gpio pins - it's easy to zap a Pi dead by being clumsy with connecting things to it). Arduino gpio pins are almost indestructible - they don't let the smoke out instantly of you short them to ground or Vcc/5V (you even get away with accidentally connecting them to 12V sometimes). The last hardware startup I was involved in was a product prototyped using RaspberryPi and Arduino boards, and manufactured using IMX233 SoC (very similar to a RasPi) and an ATmega328 (the micro controller on a Arduino Uno) on a circuit board we d4esigned - that ran almost unchanged code to the prototype. (I think we even shipped with the Arduino boot loader from memory? We could certainly flash new firmware to the AT328 over serial just like an Arduino.)
There is though, an entire universe of "embedded" out there I'm only fleetingly familiar with.
Cars are chock full of "embedded systems" these days, The anti lock brakes, the fuel injection, the airbag sensors - things like that are likely to be Arduino-style no-OS systems (but running on Motorola 68000 or something instead of ATmega grade microcontrolers). The dashboard and entertainment system and climate control are likely to be linux (or Android for entertainment systems?) more similar to a RasPi.
Industrial controllers are often decades old tech like SCADA, often with linux gateways more or less securely connecting their pre-security designed control planes to the internet...
Whitegoods all have microciontrollers in them these days. If I had to guess I'd say mostly Arduino-like rather than linux-based, but I din't _really_ know.