Ground Embedded KO Subscribe

Roadmap / Foundations

Computer Architecture

You need memory maps and interrupts to read a datasheet or reference manual.

Goal Explain how your C code actually executes inside the chip.

  1. 01
    Von Neumann and Harvard

    Whether code and data travel the same path or separate ones.

    Read the note KR

  2. 02
    Inside the CPU

    Registers, the ALU, the program counter, and the fetch-execute loop.

    Read the note KR

  3. 03
    Pipelines

    Overlapping several instructions, and why branches are slow.

    Read the note KR

  4. 04
    Memory hierarchy

    Registers, cache, SRAM, Flash: the faster, the smaller and costlier.

    Read the note KR

  5. 05
    Memory map

    Code in Flash, variables in SRAM. Everything in an MCU has an address.

    Read the note KR

  6. 06
    Buses and peripherals

    Peripheral registers live at memory addresses too. AHB, APB and memory-mapped I/O.

    Read the note KR

  7. 07
    Stack and heap

    The stack that grows with every call, and why embedded code is wary of the heap.

    Read the note KR

  8. 08
    Interrupts and exceptions3D lab

    Stop, save state, jump to a handler, and return.

    Read the note KR

  9. 09
    DMA

    Hardware that moves data between memory and peripherals without the CPU.

    Read the note KR

  10. 10
    ARM Cortex-M overview

    M0, M3, M4, M7, and how MCU families such as STM32 are organised.

    Read the note KR