Embedded Processors, Development Boards & System Components

Embedded computing hardware, from processor ICs to complete development systems

This collection brings together processor chips, microcontrollers, programmable logic, embedded Linux boards, wireless modules and supporting components used in electronic prototypes and equipment. It is a mixed catalog, not a set of interchangeable processors: some products are standalone ICs, some are populated boards or finished computers, and others use “embedded” to describe a mounting style rather than computing hardware. Select by the actual part number and variant, not by the collection name alone.

Understand the main hardware groups

• Bare processors, MCUs and memories: listings include i.MX25 and i.MX RT1011 devices, STM32, 8051-family, PIC, AVR and nRF-based controllers, CH559 USB-oriented boards, a TMS320C6748 DSP, CPLDs and FPGA ICs, plus standalone NOR and NAND flash. A loose IC needs a suitable PCB, power supply, clock, boot storage, programming method and firmware as applicable; memory chips and programmable logic are not drop-in CPUs. Compare exact suffixes, package, pin count, temperature grade, memory organization and electrical limits before substitution.
• MCU learning and control boards: NUCLEO-F103RB and F446RE, STM32F103/F407/H750, RP2350, Mega 2560 Pro and XIAO ESP32-S3 offerings serve different firmware ecosystems. An onboard debugger advertised on a Nucleo listing must not be assumed on a minimum-system board. A development board exposes convenient connectors and support circuitry, whereas a chip-only listing does not. RP2350's Arm/RISC-V architecture options are not interchangeable with AVR or STM32 binaries.
• Linux-capable boards and industrial compute modules: i.MX6 boards, Raspberry Pi 4 configurations, BeagleBone Black/AM3358, STM32MP1/MP2, RK3576 and RK3562 modules, Zynq-based cores, and x86 boards, mini PCs or barebones systems vary widely in architecture and included hardware. Some require an external carrier, boot medium, display, supply, enclosure or thermal solution. Check RAM and storage by chosen option; a core module is not automatically a complete single-board computer.
• Programmable logic and signal processing: XC7K160T, XC7Z020, Cyclone-family and Spartan-7 listings may be individual FPGAs, FPGA SoCs or development boards. Zynq integrates an Arm processing subsystem with programmable logic; a conventional FPGA does not automatically contain a ready-to-run CPU. DSP and ADAU1452 audio development hardware has its own toolchain and signal path, not generic MCU pin compatibility.
• Wireless, interface and data-acquisition hardware: WT32-ETH01, cellular SIM7080G and EM06 modules, LoRa radios, GNSS/LTE antennas, RS-485/CAN interfaces, USB cameras, MEMS/I2S microphones, sensors, OLED/TFT displays and logic analyzers may accompany embedded systems. A radio or antenna does not automatically include a host processor, SIM subscription, network approval or matching connector. An analyzer is a diagnostic instrument, not the target processor.
• Other uses of “embedded”: recessed sockets and power connectors, SAE cables, heat-set insert tools, ceiling speakers and microphones, wireless phone chargers, lighting, motion switches and wall instruments are also present. These are not embedded processor ICs. Their dimensions, mains rating, wiring requirements or installation suitability must be checked independently on their product pages.

Engineering selection checklist

1. Define the execution platform: determine whether you need a bare MCU, an application processor with Linux, a DSP, an FPGA/SoC, an x86 computer or a peripheral. Confirm ISA, operating system, compiler/debugger support and the exact device family; similar-looking boards can require entirely different firmware images.
2. Match the hardware form: compare bare package versus module, core board, carrier, development kit, fully assembled SBC and mini PC. Check mounting holes, header pitch, package footprint, connector keying, display/camera FPC orientation and enclosure clearance. Never infer that a photographed screen, keyboard, antenna, power brick or programmer ships with a board.
3. Verify memory and interfaces: inspect RAM, flash, eMMC, boot medium, USB host/device capability, Ethernet physical layer, wireless radio, GPIO count, UART/I2C/SPI/CAN, camera/display interface and debug access on the exact model. A connector alone does not establish that its signal is populated or supported by the chosen variant.
4. Check electrical and deployment constraints: use the device and board documentation for input supply, logic level, I/O current, thermal design, antenna placement and environmental limits. A seller's “industrial,” “original,” “CE,” or performance claim is not a collection-wide certification or verified rating. Do not apply one product's voltage or power description to another.
5. Read every option as a separate purchase: fields called Color, Model Number or Ships From can encode processor suffix, RAM, carrier, screen size, antenna connector, radio band, mains voltage, wattage, pack count or accessory bundle. For example, recessed lighting has many combinations of protocol, color temperature, finish, driver voltage and power; those options do not describe processor performance. A multi-model headline does not mean all versions arrive together.

Frequently asked questions

Does everything listed contain a programmable processor? No. Flash memory, FPGAs without a configured CPU, antennas, sensors, cameras, tools and recessed home fixtures can appear alongside processors. Identify the specific product class before comparing specifications.

Can an i.MX6 or STM32MP Linux module replace an STM32 MCU board? Not directly. An application-processor system typically differs in boot media, power sequencing, software stack, pinout and carrier requirements. Even devices from the same brand are not necessarily pin- or binary-compatible.

Is a board the same as a bare IC or complete kit? No. A bare IC has no assembled support board; a core board can require a carrier; a development board may or may not include debugger, cabling, display or power accessories. Confirm the selected variant's contents.

Does a wireless module work in every country or with every host? No. Verify supported frequency bands, antenna connector, host interface, firmware, network/operator support and applicable local requirements for the exact module and deployment region.

What if the seller text conflicts with the part number or options? Prioritize the exact selected variant and manufacturer documentation. In particular, do not rely on generic supply-voltage text, unverified originality statements or a family-level title to specify a particular chip, board revision, storage amount or included kit.

For design-in, compare the individual product listing against the manufacturer's datasheet, board schematic and software documentation before placing an order. This guidance helps narrow a heterogeneous catalog; it does not establish universal compatibility or installation approval.