As always Caleb I am amazed by the way you seemingly effortlessly jump between platforms. But it occurs to me that where I would have a few different chips and transistors on my workbench, guys like you now have a few different boards. Getting an MCU project going from scratch would be a huge undertaking these days, but the boards do most of the donkey work for you. The effort is now in the programming and interfacing (which is where you excel). Very nice show.
It is really very diversified varieties of boards covered by one person. Raspberry-Pi and chipkit module combination will be really helpful stuff for armature electronics developers, otherwise if one know embedded system design he can directly program Raspberry-Pi. But overall it is very good video explanation of wide variety of boards.
I have used several of the boards you mentioned and plan to eventually get around to a couple mentioned that I don't have yet. One new one I recently picked up was the Atmel ATSAMD20-XPRO for their new Cortex M0 processor.
I wanted to get some experience with the low end Cortex ARM processors. One thing that really pushed me towards the Atmel board was their free development system. It is based on Visual Studio, which admittedly is a hog but I am familiar with it, and it comes bundled with the GCC compiler already integrated.
Most of the other development boards require a higher end 3rd party development system that is either time limited, code space limited or cost several $K for the professional version. If I was working on a commercial product I might have gone a different route, but this is a self funded learning project that will probably extend over many months on a time as available basis.
Freescale and STM offer some pretty slick and inexpensive development boards too. Freescale has their Freedome boards for just over $12 and the ST's Discovery boards are about the same. On the software side...Freescale offers their software for free with a reasonable code size limit, and mbed has a free online compiler, downloader, etc that supports a number of these smaller dev boards.
Never before has there been such a plethora of dev boards that cater to so many different skill sets.
It is easy for me to jump back and forth because I do EXTREMELY SIMPLE THINGS. I'm usually doing beginner level things, I often just have a nack for presentation that makes it look like maybe it is is more complex than it actually is.
@Caleb - don't put yourself down....You've said several times that you are not an engineer (nor am I so I sympathise) but you seem a lot more capable than some engineers I have known. It's ability that counts. Have a good Christmas.
I'm a semi-novice like yourself and found that my go to dev board is simply an ATMega32a (in the 40pin DIP format) plugged into a solderless breadboard. I love the way the I/O pins all the ports are in bit order. I keep a handful of what I call "blinkeys" (an LED with a limiting resistor attached) around and plug them into the ports where needed.
The code is easily ported to smaller ATMega chips or even over to the Arduino.
Interesting about the Red Bull PCB. I am wondering if its just the PCB design that makes it more fun or if they actually added anything new to it? I have a few of the TI dev kits and like you have yet made the time to tinker with them, the Atmel STK500, STK600, Nordic nRFgo Motherboard, many Cypress PSoC flavors (PSoC is my favorite platform from both a technical and personal viewpoint), and I keep a LabJack U6 which I consider more of a development platform rather than a DAQ as it is marketed.
If you are interested my company is experimenting with a run of "Made in the USA" USAduino™ boards based on the Uno R3 i.e. a clone but with a silk screen of the US Flag 100% PCB and assembly "Made in the USA" less the components of course. As well as compliance with the Arduino and LUFA terms so it is respectful of the open source spirit unlike the many existing clones. Check out www.edtrication.com if you are curious.
I agree with poster below:"Do not put yourself down." The results matter far more than the label ever will.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.