{"docs":[{"id":125,"title":"Choosing a Microcontroller: Cores, Memory and Peripherals","heading":"Choosing a Microcontroller: Cores, Memory and Peripherals","subheading":null,"category":"Hardware Design","body":{"root":{"type":"root","children":[{"type":"heading","tag":"h3","version":1,"children":[{"type":"text","text":"Sizing memory and pins","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Estimate flash and RAM from the firmware components: stacks, libraries, buffers and application code. If over-the-air updates are planned, a dual-slot scheme needs roughly twice the application space. Leave generous headroom, because firmware grows over a product life and moving to a larger part late can mean a new package.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Use the vendor’s pin configuration tool to assign every peripheral, the debug pins and wake-up inputs in the intended package. This is the step that reveals conflicts, and it takes an hour compared with a board respin.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"tags":"Embedded Hardware, Microcontrollers, Arm Cortex-M","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"The microcontroller fixes the limits of the firmware, the power budget and much of the board. Choose it from peripheral and memory needs, not clock speed.","featuredImage":null,"type":"Blog","readTime":"3 min read","publishedAt":"2026-11-15T22:32:00.000Z","heroImage":null,"introText":"Microcontroller selection is often driven by familiarity or by the fastest core in the budget. Neither is a good guide. The part has to provide the right peripherals in the right numbers, enough memory with room to grow, the power modes the product needs and a supply that will last. The core matters, but usually less than these. This article sets out how to compare candidates systematically.","metrics":[{"id":"choosing-a-microcontroller-cores-memory-and-peri-metric-1","value":"Cortex-M0+","label":"Arm’s smallest mainstream core, with a two-stage pipeline built for low power and cost.","icon":null},{"id":"choosing-a-microcontroller-cores-memory-and-peri-metric-2","value":"Cortex-M4","label":"Adds DSP instructions and an optional single-precision floating-point unit.","icon":null},{"id":"choosing-a-microcontroller-cores-memory-and-peri-metric-3","value":"Cortex-M33","label":"An Armv8-M core with optional TrustZone security, DSP extension and FPU.","icon":null},{"id":"choosing-a-microcontroller-cores-memory-and-peri-metric-4","value":"RISC-V","label":"An open instruction set now offered in microcontrollers by several vendors.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"The most common late surprise is running out of something: flash for an update image, RAM for a communications stack, a second SPI port or a timer channel. Pin multiplexing makes this worse, because two peripherals that exist on the chip may share the same pins.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The second is power. A fast core with high run current can still suit a battery product if it sleeps well, while a slow one with poor sleep modes may not.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"Map every interface to a pin before choosing the part. The feature list does not tell you what fits at the same time.","author":"","role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"List the required peripherals with counts, the memory estimate with headroom, the power modes, the temperature range and any security needs.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Shortlist parts that meet them, then check pin assignments, errata sheets, tool support and lifecycle status for each.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Prototype the riskiest function on an evaluation board before committing the layout.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"choosing-a-microcontroller-cores-memory-and-peri-result-1","title":"Firmware Headroom","description":"Memory sized with margin leaves room for features and updates."},{"id":"choosing-a-microcontroller-cores-memory-and-peri-result-2","title":"No Pin Conflicts","description":"Every interface is assigned before the schematic is drawn."},{"id":"choosing-a-microcontroller-cores-memory-and-peri-result-3","title":"Right Power Profile","description":"Sleep and run currents suit the product’s duty cycle."},{"id":"choosing-a-microcontroller-cores-memory-and-peri-result-4","title":"Room to Grow","description":"A family with pin-compatible larger variants allows later upgrades."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Read the errata sheet before committing. Silicon bugs in a peripheral you depend on are better found on paper.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Check the toolchain, debug probe and middleware support. A capable chip with poor software support costs development time.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"choosing-a-microcontroller-cores-memory-and-peri-challenge-1","title":"Running out of flash for update images","description":null,"icon":null},{"id":"choosing-a-microcontroller-cores-memory-and-peri-challenge-2","title":"Peripherals that share the same pins","description":null,"icon":null},{"id":"choosing-a-microcontroller-cores-memory-and-peri-challenge-3","title":"Silicon errata found during integration","description":null,"icon":null},{"id":"choosing-a-microcontroller-cores-memory-and-peri-challenge-4","title":"A respin to move to a larger package","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-11-15T17:32:32.682Z","createdAt":"2026-11-15T17:32:32.682Z"}],"hasNextPage":false,"hasPrevPage":false,"limit":10,"nextPage":null,"page":1,"pagingCounter":1,"prevPage":null,"totalDocs":1,"totalPages":1}