[ 4 devices ]Adafruit hardware in Flashable spans four different interface patterns: the RP2040 MacroPad for USB hotkeys, PyPortal for Wi-Fi weather displays, CLUE for sensor-driven measurement and live plotting, and the Feather ESP32-S3 TFT for compact connected prototypes. MacroPad and CLUE projects lean on CircuitPython bundles, while the Feather also has an Arduino path; their files and libraries must match the board and runtime. Choose PyPortal when a built-in touchscreen and internet dashboard are central, CLUE when onboard motion and environmental sensing matter, or Feather when battery support and STEMMA QT expansion are more useful than an integrated input surface.
[ 4 devices ]M5Stack hardware in Flashable ranges from the keyboard-equipped Cardputer and touchscreen Core2 to the battery-powered M5StickC PLUS2 and tiny AtomS3 display controller. Projects span manufacturer hardware diagnostics, firmware launchers, MicroHydra’s Cardputer-specific MicroPython app runtime, animated faces, a servo-driven Stack-chan robot, and authorized security-lab firmware such as Bruce or NEMO. Pick Cardputer for text input and microSD workflows, Core2 for touch and stackable robotics, PLUS2 for a compact sensor controller, or AtomS3 for minimal embedded interfaces. Target-specific binaries, branches, partitions, filesystem images, and toolchain versions matter; Launcher replaces the active firmware, while libraries such as M5Stack-Avatar still need integration into a compatible application.
[ 4 devices ]Raspberry Pi has the broadest hardware range in Flashable: Pi 5 for higher-performance Linux and PCIe expansion, Zero 2 W for compact headless deployments, Pico 2 W for wireless microcontroller work, and Pi 400 for a keyboard-integrated desktop. Linux projects include DNS filtering, 3D-printer control, Home Assistant OS, smart displays, bird monitoring, remote KVM, retro gaming, camera management, and ADS-B decoding. Pico 2 W instead uses C/C++ UF2 builds or MicroPython scripts. Selection depends on workload and interfaces: PiKVM supports Zero 2 W but not Pi 5, Home Assistant OS targets Pi 5 specifically here, and older RP2040 MicroPython examples need validation before use on RP2350.
[ 3 devices ]Arduino hardware in Flashable covers three distinct jobs. UNO R4 WiFi pairs a Renesas main controller with an ESP32-S3 bridge and built-in 12×8 matrix, supporting matrix animations as well as advanced bridge-firmware maintenance. Nano ESP32 is the compact wireless option for either Arduino sketches or a replacement MicroPython runtime, and it can host Matter examples when core, partitions, pins, and commissioning setup match. Nicla Vision is the camera-and-sensor choice for OpenMV development and Edge Impulse image classification. These workflows are not interchangeable: MicroPython overwrites Nano firmware, OpenMV can be replaced by Arduino uploads, and Nicla models must fit internal flash.
[ 3 devices ]LILYGO hardware in Flashable includes the display-first T-Display-S3, keyboard-and-trackball T-Deck, and rotary-controlled T-Embed, all built around ESP32-S3. Manufacturer examples exercise each board’s screen, input, audio, power, and optional radios; Bruce and M5Stack Launcher add device-matched firmware workflows. The LoRa-equipped T-Deck also supports Meshtastic or MeshCore for off-grid messaging, but the installed radio band, antenna, regional settings, and exact T-Deck variant must agree. T-Embed’s optional CC1101 changes available hardware and disables its microphone. For the documented Arduino examples, core and display-library versions can be tightly coupled, and touch, Plus, or radio-specific binaries must not be treated as universal.
[ 3 devices ]Seeed Studio hardware in Flashable spans the camera-and-microphone XIAO ESP32S3 Sense, the self-contained SenseCAP Watcher edge-AI terminal, and the ATSAMD51-based Wio Terminal with screen, controls, sensors, wireless coprocessor, and Grove expansion. XIAO projects cover browser camera streaming and trained keyword spotting; a separate SSCMA-Micro sensor is required for the host-library project, which does not run inference on the bundled camera. Watcher supports ESP-IDF firmware examples and event delivery to supervised Home Assistant through a custom integration. Wio Terminal uses sketch-specific Arduino examples. Board packages, PSRAM, camera variant, ESP-IDF version, optional modules, credentials, and each example’s dependencies determine compatibility.
[ 2 devices ]Pimoroni hardware in Flashable covers two display-oriented RP2040 systems. Badger 2040 W is a wireless, battery-friendly e-paper badge with buttons, suited to persistent name, calendar, weather, QR, checklist, and information apps. PicoVision uses two RP2040 chips to generate digital video for graphics demos, larger dashboards, and a PC/XT emulator with microSD storage and USB input. Choose Badger for low-refresh portable information, not animation; choose PicoVision when an HDMI/DVI display is part of the build. Their firmware paths also differ: Badger’s full OS image can erase user files, while PicoVision’s normal and widescreen builds trade resolution and sprite capacity.
[ 1 device ]Arduboy is represented by the FX-C, a credit-card-sized ATmega32U4 handheld with a monochrome OLED, physical controls, audio, and flash storage for homebrew games. Flashable connects it to the Arduboy2 Arduino library, whose examples and APIs cover drawing, sprites, buttons, sound, collision helpers, and frame timing. This is a constrained 8-bit game-development target rather than a general display board: program and RAM budgets reward smaller library variants and selective features. Arduboy2 coexists with the older Arduboy library under a different class name, and saved data must stay above the library’s reserved EEPROM system area.
[ 1 device ]ClockworkPi is represented by the uConsole CM4 Lite Kit, a modular handheld Linux computer with a keyboard, 5-inch display, expansion access, and a Raspberry Pi Compute Module 4 core. Flashable projects focus on writing ClockworkPi’s variant-matched system images and adding the RP2040-based uPico expansion card for programmable I/O, switched power, USB, speaker support, and PMOD-style peripherals. Select images by compute core—CM4, A06, and R01 releases are not interchangeable—and expect storage flashing to erase the card. The uPico control software currently supports CM4 and R-01, not A04 or A06, with some behavior also dependent on the expansion PCB revision.
[ 1 device ]Espressif Systems is represented by the ESP32-S3-BOX-3, an AIoT development kit combining an ESP32-S3, touchscreen, microphone array, speaker, Wi-Fi, Bluetooth, and modular sensor accessories. Flashable links it to Espressif’s ESP-BOX framework for factory demos, offline speech interaction, display and audio experiments, sensor monitoring, and RainMaker-oriented prototypes, plus a cloud-backed ChatGPT voice terminal. Board and software versions matter: the main framework documents a specific ESP-IDF 5.1 baseline, while the ChatGPT demo uses ESP-IDF master and requires separate credential and application builds. Sensor Monitor needs the BOX-3-SENSOR accessory; the ChatGPT path additionally needs internet access and API credentials.
[ 1 device ]Flipper Devices is represented by Flipper Zero, a pocket multi-tool with Sub-GHz radio, NFC, 125 kHz RFID, infrared, iButton, USB, Bluetooth, and GPIO interfaces. Flashable covers building the official firmware, installing community Momentum or Unleashed firmware, browsing the official application catalog, and reviewing BadUSB scripts in an isolated authorized lab. Stock firmware is the appropriate baseline for platform development, while many extensions belong in external applications rather than core changes. Community firmware replaces the installed system and may require matching microSD assets. Radio, keyboard-injection, and data-collection features are capability- and jurisdiction-sensitive; exact app, payload, host OS, frequency, and authorization determine compatibility and safe use.
[ 1 device ]Great Scott Gadgets is represented by HackRF One, a USB software-defined radio that receives or transmits from 1 MHz to 6 GHz in half-duplex operation. Flashable connects it to three project patterns: PortaPack MAYHEM for a portable on-device radio interface, dump1090-fa for receive-only aircraft transponder decoding on a separate Linux host, and Universal Radio Hacker for desktop capture and protocol analysis. A PortaPack is an additional device and must match MAYHEM’s supported hardware; firmware and SD assets should share a release. Dump1090 and URH are host applications, not HackRF firmware, and require appropriate antennas, drivers, settings, and lawful, authorized RF operation.
[ 1 device ]Panic is represented by Playdate, an Arm Cortex-M7 handheld with a 1-bit 400×240 display, buttons, accelerometer, Wi-Fi, and a side-mounted analog crank. Flashable connects it to Lua SDK reference snippets, the C-based CrankBoy Game Boy emulator, and Playorama’s crank-controlled video playback. The SDK examples are small source fragments that must be placed in a valid Playdate project, not complete games. CrankBoy supports legally obtained ROMs but has game, peripheral, and stability limits; Playorama requires video and audio converted into Playdate-readable files with matching names. Simulator testing suits SDK code, while crank feel, sideloading, media, and emulator behavior warrant hardware verification.
[ 1 device ]PINE64 is represented by PineTime, an nRF52832 smartwatch with a color touchscreen, Bluetooth LE, heart-rate sensor, and accelerometer. Flashable presents two replacement-firmware directions: InfiniTime for a full smartwatch interface with companion notifications, apps, watch faces, and separately delivered resources, or wasp-os for a MicroPython-oriented watch environment and Bluetooth-accessible REPL. Both use over-the-air update workflows, but their bootloaders, packages, companions, and validation steps differ. InfiniTime updates must be validated on the watch to avoid rollback. wasp-os bootloader work carries higher brick risk, especially on sealed watches, and early Y7S Developer Edition hardware follows a separate installation route.