Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Something else to consider...</p> <p>You need to decide what it is you want the kid to learn. There are a lot of different kits you can buy (see above answers for a lot of good ones); however, keep in mind that kits are made to get the user up and running quickly, usually to evaluate some microcrontroller or interface chip.</p> <p>For <em>really</em> teaching someone embedded systems, "quickly" isn't necessarily the best way to go. The kits will provide some IDE (Interactive Development Environment) that adds multiple levels of abstraction between the student and the topic of "learning firmware". As a result, the kid may be writing "hello world" apps the first day, but still doesn't have a clue what the difference is between RAM/ROM/Address/Data/etc...</p> <p>Bottom line... these days, there are so many kits out there, you really have no choice but to just pick one (see other answers for good suggestions); however, if you <em>really</em> want the kid to learn the fundamantals, then after he writes the "hello world" app, and makes a few LEDs blink. Stop him there, and teach him whats behind all that.</p> <p>Yep, that didn't directly answer your question, but hopefully it will guide you in how to <em>really</em> teach him the "meat". A good place to start for this may be a book I wrote a few years ago: "Embedded Systems Firmware Demystified". There are others as well, like "Programming Embedded Systems in C and C++". My book also introduces a boot monitor that is a good place to start for learning firmware. Check out <a href="http://www.umonfw.com" rel="nofollow noreferrer">http://www.umonfw.com</a> for info on that. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload