RP2040 Assembly Language Programming Including the RP2350 and Raspberry Pi Pico 2 (Stephen Smith)（Z-Library）

【One-Line Pitch】 A hands-on guide to programming the Raspberry Pi Pico-series (RP2040 and RP2350) in ARM assembly language, taking you from toolchain setup through hardware registers, PIO, interrupts, and floating point. Best for hobbyist makers and embedded programmers who already know some C and want to understand what actually happens at the metal. 【Book Arc】 - **Opening (~0%–12%)**: Frames the Pico-series as a $4 microcontroller without an OS, introduces the RP2040/RP2350 SoCs and the second edition's additions (RP2350, Cortex-M33, VS Code workflow, Debug Probe), and sets the "learn by doing" philosophy. - **Early (~12%–32%)**: Establishes the fundamentals of ARM assembly — why assembly still matters, number representations, instruction formats, registers, memory layout, and the GCC assembler toolchain — culminating in a first "Hello World" program. - **Middle (~32%–56%)**: Core programming mechanics: logical operators and design patterns, memory definition/alignment/load-store, function calls and the stack, macros and includes, then bridging to C and the SDK, and finally direct hardware programming (memory map, pins, SIO, PIO architecture and instructions). - **Late (~56%–76%)**: Interrupts (vector table, state saving, priorities, alarm timer, SVCall), multiplication/division/floating point including the RP2350 FPU, plus the practical development environment — breadboard wiring, Debug Probe, VS Code, SDK install, and helper scripts. - **Ending (~76%+)**: The second assembly chapter consolidates the journey with a complete first program, reverse-engineering exercise, and a summary that ties instruction-level knowledge back to writing better C and Python. 【Key Takeaways】 - **Assembly knowledge pays off beyond assembly** (Opening): The book argues that understanding the processor at the instruction level makes you a better C and Python programmer, and that learning one architecture transfers to others. (Early) - **The Pico-series is a dual-core ARM SoC, not a computer** (Early): No OS, no video, no keyboard — just CPUs, SRAM, USB, and hardware controllers. This shapes every programming decision. (Early) - **Memory and data alignment are first-class concerns** (Middle): Defining memory contents, aligning data, load/store patterns, and indexing through memory are treated as core skills, not afterthoughts. (Middle) - **Function calls require disciplined stack and register management** (Middle): Branch-with-link, nesting, parameters, return values, stack frames, and macros form a complete calling convention you must internalize. (Middle) - **Hardware registers and PIO are the path to real device control** (Middle): Setting pin functions, programming pads (including RP2350 isolation), initializing SIO, and using the PIO state machines with JMP/WAIT/IN/OUT/PUSH/PULL/MOV/IRQ/SET. (Middle) - **Interrupts demand careful state preservation** (Late): The vector table, saving processor state, priorities, and the RP2040 alarm timer are covered with a complete LED-flashing example. (Late) - **The RP2350 adds floating point and new instructions** (Late): Single-precision FPU, division instructions, and pad isolation are second-edition additions that distinguish the newer chip from the RP2040. (Late) - **Debugging needs a separate channel** (Late): Because stopping the CPU kills USB, the Raspberry Pi Debug Probe and UART are essential for real debugging with openocd and gdb. (Late) 【Reading Tips】 - **Deep-read the early chapters on registers, instruction format, and memory** — these are the vocabulary for everything later; skimming here will make the hardware chapters painful. - **Skim the toolchain setup chapter if you already have VS Code and the SDK working**, but do create the helper scripts (m-usb, m-uart, cmaked, ocdg) — they save hours. - **Treat the PIO and interrupt chapters as the hard spots** — work through the LED examples on real hardware; the PIO instruction set and timing/clock-divider concepts are where most readers slow down. - **Use the C/SDK interop chapter as your bridge** — if you come from C, this is where assembly stops feeling alien and starts feeling practical. - **Don't skip the exercises** — the book explicitly says the only way to learn is by doing, and the reverse-engineering exercise at the end is a good self-test. 【Coverage Limits】 The excerpts are heavily weighted toward front matter, table of contents, and setup material; detailed chapter content on PIO internals, interrupt programming, and floating-point examples is only partially visible. The guide reflects the book's structure and stated goals rather than a full read of every code walkthrough.