Getting Started with FPGAs (Russell Merrick)（Z-Library）

# Getting Started with FPGAs — Reading Guide ## 【One-Line Pitch】 A hands-on, beginner-friendly introduction to FPGA design that teaches you to think in parallel rather than serial, with every concept explained in both Verilog and VHDL. Perfect for software developers, electronics hobbyists, or students who want to understand how FPGAs actually work and build real projects on affordable hardware. ## 【Book Arc】 - **Opening (~0%–6%)**: Sets expectations for who the book serves (no prior Verilog/VHDL needed, some programming exposure helpful) and outlines the project-based approach using low-cost Lattice iCE40 boards. - **Early (~6%–24%)**: Introduces FPGA fundamentals — digital logic, look-up tables (LUTs), flip-flops, combinational vs. sequential logic — and explains why parallel thinking is the core mental shift from conventional programming. - **Early–Middle (~24%–39%)**: Covers the FPGA build process (simulation, synthesis, place and route), testbench writing, and common building blocks like multiplexers, shift registers, LFSRs, RAM, and FIFOs. - **Middle (~39%–52%)**: Explores FPGA history, real-world applications (telecom, finance, defense, space), and how FPGAs compare to microcontrollers and ASICs — context for choosing the right tool. - **Late (~52%–75%)**: Dives into state machines, FPGA primitives (block RAM, DSP blocks, PLLs), and numbers/math — signed vs. unsigned, fixed-point, and avoiding common math pitfalls. - **Ending (~75%–100%)**: Covers I/O techniques including SerDes for high-speed data, plus appendices on development board selection and career advice for aspiring FPGA engineers. ## 【Key Takeaways】 - **Parallel thinking is the fundamental skill** (Early): FPGAs execute everything simultaneously, unlike serial CPUs — this mental shift underpins all FPGA design and improves general problem-solving. - **LUTs and flip-flops are the atomic building blocks** (Early): Understanding how these map onto real FPGAs demystifies what your code actually becomes in hardware. - **Simulation before hardware saves hours** (Early): Writing testbenches to verify designs is non-negotiable; the book shows both manual and self-checking testbench approaches. - **Common modules solve recurring problems** (Middle): Multiplexers, shift registers, LFSRs, RAM, and FIFOs appear constantly — mastering these patterns accelerates all future designs. - **Crossing clock domains requires deliberate design** (Middle): Metastability and timing errors are avoidable with proper synchronization techniques like FIFOs between clock domains. - **State machines bring structure to complex logic** (Late): Using one or two always/process blocks, plus best practices, makes designs readable and maintainable. - **FPGA primitives are performance multipliers** (Late): Block RAM, DSP blocks, and PLLs are specialized hardware — knowing when to instantiate them beats reinventing with generic logic. - **Math on FPGAs has hidden traps** (Late): Signed vs. unsigned representation, signal sizing, and fixed-point arithmetic require careful attention to avoid subtle bugs. ## 【Reading Tips】 - **Skim Chapter 1's history section** (~42%–48%) if you're eager to code — the FPGA vs. microcontroller comparison is useful, but the 1980s timeline is skippable context. - **Deep-read the simulation chapter** (~6%–9%): Testbench writing is the single most transferable skill; the debouncing project ties together code, simulation, and hardware. - **Read both Verilog AND VHDL examples** even if you only plan to use one — comparing them clarifies language-agnostic concepts like always vs. process blocks. - **Don't skip the "Dangers of Latches" section** (Early): Accidental latches are a classic beginner mistake that causes mysterious hardware behavior. - **Use the projects as checkpoints**: Each project (LED blinking, memory game, etc.) consolidates prior concepts — actually building them on an iCE40 board is where learning sticks. ## 【Coverage Limits】 This guide synthesizes the table of contents, introduction, and early/middle chapter excerpts. Detailed code listings, specific project walkthroughs, and the career appendix content are not covered in depth here. ##