Embedded & Firmware Engineering

A chosen microcontroller and pinned toolchain, a bench you can debug on, bring-up and release checklists, field failure triage, power and memory budgets, and over-the-air updates with secure boot and rollback.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Embedded & Firmware Engineering, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Embedded & Firmware Engineering

Writing software for microcontrollers and devices, working within tight memory and power limits, hardware bring-up and safe over-the-air updates.

  1. Microcontroller selection for a new product
  2. Pinned toolchain and reproducible firmware build
  3. Debug probe and bench instrument set-up
  4. Memory map and linker script walkthrough
  5. Board bring-up checklist for new prototypes
  6. Bare metal or RTOS decision
  7. Hardware abstraction layer and driver boundaries
  8. Firmware version and build identity in every image
  9. Hard fault handler and crash capture
  10. Bootloader and flash partition layout
  11. Flash and RAM budget per build
  12. Hardware-in-the-loop test rig
  13. Field failure and returned unit triage
  14. Silicon errata and datasheet revision watch
  15. Vendor SDK and HAL update cycle
  16. Sleep current and power regression checks
  17. Firmware release checklist and signed images
  18. Fleet telemetry and crash dump review
  19. Lab bench and spare board inventory
  20. Component lifecycle and obsolescence watch
  21. Reading datasheets and reference manuals
  22. Interrupts, priorities and shared data
  23. DMA for peripherals without CPU load
  24. Low-power modes and wake sources
  25. RTOS tasks, queues and priority inversion
  26. Bench debugging with a logic analyser and scope
  27. Unit testing firmware on the host
  28. Embedded C pitfalls, volatile and undefined behaviour
  29. Over-the-air update with rollback
  30. Secure boot and image signing chain
  31. Watchdog strategy that catches real hangs
  32. Stack usage analysis and overflow detection
  33. MISRA C subset and static analysis for firmware
  34. Power-loss-safe storage with wear levelling
  35. Device protocol framing and versioning
  36. Manufacturing test firmware and production programming
  37. Debug port lockdown and readout protection
  38. EMC pre-compliance test session
  39. Radio certification test firmware
  40. Production line launch for a new device
  41. Staged rollout of a major firmware release
  42. Recovering units bricked by a failed update
  43. Web or app developer moving into embedded
  44. Inheriting a firmware codebase with no original author
  45. Porting firmware to a replacement microcontroller
  46. Solo firmware engineer at a hardware startup
  47. Firmware review of the schematic before layout
  48. Functional safety process for safety-related firmware
  49. Worst-case execution time and timing analysis
  50. Embedded Rust evaluation on a spare board

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Microcontroller selection for a new product

Picking a part from the first evaluation board you happen to own is how teams end up rewriting drivers a year later when flash runs out or the part goes on allocation.

First tasks

  • List every peripheral and interface the product needs in its first two revisions
  • Score three candidate parts on memory, power, security and supply
  • Order the development kit for the leading candidate
  • Write the decision and the second-source plan in the repository docs

Pinned toolchain and reproducible firmware build

Firmware that builds on one laptop with whatever compiler was installed that month will produce a different binary on the next, and a different binary can mean a different bug. Pinning the cross-compiler version, the build system and every vendor package in the repository means any engineer or the CI server can rebuild a released image byte for byte.

First tasks

  • Record the compiler version and flags the current build actually uses
  • Write a container file or setup script that installs the pinned toolchain
  • Rebuild the last release on a second machine and compare checksums
  • Turn on warnings as errors and fix or document what breaks

Debug probe and bench instrument set-up

Printf debugging over a UART gets you surprisingly far, until the bug is a hard fault before the UART is initialised or a timing glitch between two chips. A proper bench (a debug probe that supports your part, a logic analyser, an oscilloscope and a current-limited bench supply) is what lets you see what the hardware is actually doing.

First tasks

  • Check which debug probes your microcontroller's vendor and debugger support
  • Get a breakpoint and single step working on the development kit
  • Capture and decode one I2C or SPI transaction with the logic analyser
  • Label each board's safe current limit on the bench supply

Make it yours.

Install Embedded & Firmware Engineering, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.