Microcontroller Programming & Flashing
An embedded program is not "run in the IDE" — it is compiled, linked, and flashed onto a chip that then boots from flash. This subject is getting a toolchain working for your board, blinking or printing over serial as a smoke test, and recovering when upload fails (wrong port, wrong board, boot button, bricked flash). Language details are in Language & toolchain.
Starting Points
- Vendor getting-started guide for your board (ESP32, STM32, AVR/Arduino, or the studio kit).
- Compilers & toolchains
- Microcontrollers & memory
Key Points
- You select the correct board, port, and flash configuration and upload a known-good sketch or firmware image.
- You implement a minimal program that drives a GPIO and reports over UART/USB serial.
- You reset, enter bootloader, and recover from a failed upload using the board's documented procedure.
- You explain what happens between source file, compiler, linker, and the image on flash.
- You keep firmware identity visible (git hash or version string) so a tester knows what is on the device.