WIP - Investigations into Embedded

Thought Dump

• In my experience, the hardest part about starting with embedded is setting up the toolchain. There're often multiple software programs needed for editing, compiling, emulation, and flashing. You need specific hardware to interface with the particular microcontroller you're targeting. You also need to make sure that your compiler can properly target the specific hardware you want to work with.

  • In Sum: Make sure you have a Code Editor, Microcontroller, Compiler (which can target the microcontroller), Emulator (+ other code checkers), Flasher Program, Bootloader Hardware, and Microcontroler paraphernalia (i.e. NV memory module).

• Most of the reason to use an embedded system is to help manage something automatically in meatspace. Therefore, embedded systems typically have to respond to events in real time. They frequently make use of Real-Time Operating Systems (RTOS) in order to manage.

  • Scheduling theory was covered in CPEN333 (Lecture 19)

• All about makefiles -> "Makefiles are used to help decide which parts of a large program need to be recompiled [...] Make can also be used beyond compilation too, when you need a series of instructions to run depending on what files have changed".

  • I have never tinkered with a makefile myself but they're good to know about.

Microcontrollers I have worked with:

μControllers	Manufacturer	Environment	Recall From...
STM32	STM	STMCube IDE	Capstone Lab-in-a-Pack
PIC family	Microchip	MPlabX IDE, CrossIDE	ELEC 291 Final Project
AT family	Atmel	CrossIDE	ELEC 291 Lab 1-3
Teensy	PJRC	Arduino	ELEC 391