> ## Documentation Index > Fetch the complete documentation index at: https://docs.embedder.com/llms.txt > Use this file to discover all available pages before exploring further. # Supported hardware > Check whether your board, MCU, or part is listed, set up a project for it, and find the probes, connections, and lab instruments Embedder works with. Use this page to check whether your board, MCU, or peripheral is listed, set up an Embedder project for it, and find the guide for your probe or instrument. * **Platforms:** **590+** MCU families, devices, modules, and development boards from **14** chip and board manufacturers, listed on the vendor pages below. Ambiq has a separate board guide. * **Peripherals:** **5,860+** sensors, drivers, memories, radios, and other parts in 11 categories, listed under [Find a peripheral](#find-a-peripheral). * **Current availability:** the project setup picker always shows the catalog available to you. These pages are for browsing. * **Not listed:** you can still work from the hardware's documents. See [If your hardware isn't listed](#if-your-hardware-isn%E2%80%99t-listed). For how your selections reach documentation and skills, see [Hardware catalog](https://docs.embedder.com/core-concepts/hardware-catalog.md). > [!NOTE] > > A listed platform gives Embedder hardware context. Flashing, debugging, and measurements also depend on your board, probe, wiring, and installed tools. A catalog listing doesn't certify any of those combinations. ## Find your platform Open your vendor's page and search it for the exact part number or board name. When your development board is listed, choose it rather than its MCU family. ### General semiconductors > [card] [STMicroelectronics](https://docs.embedder.com/supported-hardware/st.md) > > 150+ STM32 platforms, CubeMX and ST-LINK workflows, and Nucleo pinout skills. > [card] [NXP](https://docs.embedder.com/supported-hardware/nxp.md) > > 80+ LPC, Kinetis, i.MX RT, MCX, and S32 platforms. > [card] [Nordic](https://docs.embedder.com/supported-hardware/nordic.md) > > 50+ nRF, nPM, and nRF70 platforms for nRF Connect SDK and Zephyr. > [card] [Espressif](https://docs.embedder.com/supported-hardware/espressif.md) > > 30+ ESP32, ESP32-S/C/H/P, and ESP8684 platforms. > [card] [Infineon](https://docs.embedder.com/supported-hardware/infineon.md) > > 10+ AURIX, TRAVEO T2G, and PSoC Edge kits, with board skills and AURIX tooling. > [card] [Renesas](https://docs.embedder.com/supported-hardware/renesas.md) > > 20+ RA and RH850 platforms, FSP workflows, and board skills for 50+ kits. > [card] [Silicon Labs](https://docs.embedder.com/supported-hardware/silicon-labs.md) > > 30+ EFR32 platforms, Simplicity SDK, and the SixG301 board skill. > [card] [Texas Instruments](https://docs.embedder.com/supported-hardware/ti.md) > > 50+ MSP430, C2000, and Sitara AM2x platforms. > [card] [Ambiq](https://docs.embedder.com/supported-hardware/ambiq.md) > > Apollo510 EVB bring-up, flashing, J-Link/SWD, RTT, and recovery. > [card] [XMOS](https://docs.embedder.com/supported-hardware/xmos.md) > > xcore.ai and XMOS evaluation boards with XTC Tools, `xrun`, `xflash`, `xgdb`, and xSCOPE. ### Community > [card] [Raspberry Pi](https://docs.embedder.com/supported-hardware/raspberry-pi.md) > > 30+ computers, Compute Modules, Pico boards, and RP2 MCUs. > [card] [Arduino](https://docs.embedder.com/supported-hardware/arduino.md) > > 30+ UNO, Nano, MKR, Portenta, Nicla, and classic boards. > [card] [Adafruit](https://docs.embedder.com/supported-hardware/adafruit.md) > > Feather 32u4, Gemma, Trinket, and other Adafruit AVR boards. > [card] [Teensy](https://docs.embedder.com/supported-hardware/pjrc.md) > > Teensy LC, 3.2, 3.6, 4.0, and 4.1. ### 8-bit microcontrollers > [card] [Microchip AVR](https://docs.embedder.com/supported-hardware/microchip-avr.md) > > 50+ ATtiny, ATmega, and AVR Dx/Ex platforms, including Curiosity Nano and Xplained kits. ## Find a peripheral The peripheral catalog lists the sensors, drivers, memories, radios, and other parts you can add to a project. Embedder then works from their datasheets when you ask about registers, initialization, or wiring. The catalog has **5,860+** entries across 11 categories. Open a category and search it for the part number. > [card] [Converter](https://docs.embedder.com/supported-hardware/peripherals/converter.md) > > 2,280+ entries. ADCs, DACs, amplifiers, logic, transceivers, isolators, and other signal-chain parts. > [card] [Power](https://docs.embedder.com/supported-hardware/peripherals/power.md) > > 1,730+ entries. Regulators, PMICs, MOSFETs, protection, and power-path parts. > [card] [Sensor](https://docs.embedder.com/supported-hardware/peripherals/sensor.md) > > 860+ entries. Temperature, motion, magnetic, optical, gas, and other sensors. > [card] [Driver](https://docs.embedder.com/supported-hardware/peripherals/driver.md) > > 490+ entries. Motor, gate, LED, and actuator drivers. > [card] [Wireless](https://docs.embedder.com/supported-hardware/peripherals/wireless.md) > > 270+ entries. Wi-Fi, Bluetooth, cellular, GNSS, NFC, and RF modules. > [card] [Memory](https://docs.embedder.com/supported-hardware/peripherals/memory.md) > > 90+ entries. Flash, EEPROM, FRAM, MRAM, SRAM, and related memories. > [card] [Display](https://docs.embedder.com/supported-hardware/peripherals/display.md) > > 60+ entries. Display drivers, TFT, OLED, LCD, and LED modules. > [card] [Connector](https://docs.embedder.com/supported-hardware/peripherals/connector.md) > > 50+ entries. Radio and evaluation boards, switches, relays, USB interface parts, and headers. > [card] [Interface](https://docs.embedder.com/supported-hardware/peripherals/interface.md) > > Bus expanders, isolators, and interface translators. > [card] [Development boards](https://docs.embedder.com/supported-hardware/peripherals/dev-board.md) > > Adapter and prototyping boards in the peripheral catalog. > [card] [Electromechanical](https://docs.embedder.com/supported-hardware/peripherals/electromechanical.md) > > Encoders, switches, and other electromechanical parts. ### Choose the right entry * Match the full part number and the manufacturer. Several entries can have similar names. * Some parts appear more than once, for example under both ON Semiconductor and onsemi. Each row is a separate catalog entry. Pick the one whose manufacturer and description match your part. * Confirm the specifications, package, voltage, and bus in the manufacturer's datasheet. The descriptions and tags here help you find a part; they don't replace the datasheet. * Sections titled **Entries needing identification** hold entries with incomplete or conflicting catalog labels. You can find them in the picker by the label shown. Establish the exact part before you rely on its specifications. ### Read the tables Larger category pages group their entries by primary tag in expandable sections. Each table has these columns: | Column | What it shows | | - | - | | Part | The catalog name. Search for it in the picker. | | Manufacturer | The manufacturer label in the catalog. | | Function | A short description of the part. | | Interface | The host connection, when the catalog specifies one. An em dash (—) means it isn't specified. Check the datasheet before wiring. | | Tags | The entry's subcategories, including other functions it serves. The VS Code picker shows the same tags. | Each entry is listed on one category page. A few entries are filed here under a corrected category, and the picker's category filter may still show them under their original one. If a category view in the picker doesn't show a part, search for its part number instead. ### Add a part to your project Select a project and run `/peripheral`, then search for the part number and add each entry whose part number and manufacturer match your board. The command appears only when a project is selected. * In VS Code, `/peripheral` or **Open project peripherals** in the chat header opens **Peripherals**. Choose **Add peripherals** there. * In the terminal UI, `/peripheral` opens the **Project Peripherals** picker directly. Press `Space` to select a row and `Enter` to add your selection. [Add and manage peripherals](https://docs.embedder.com/core-concepts/add-peripheral.md) has the full steps, including adding a part from chat, parts suggested from your schematics, and custom parts. Opening a part's datasheets and removing a part are available in VS Code, not in the terminal UI. Adding a part gives Embedder its documentation. It doesn't write a driver. When you ask for driver or configuration changes, include your wiring, bus address, and board constraints. ## If your hardware isn't listed Give Embedder the documents for your hardware instead of a catalog entry: | Situation | What to do | | - | - | | Custom or unlisted board | In VS Code, choose **New project** and upload your schematic, or select **Upload schematics** in the terminal UI's platform picker, to [start the project from your design](https://docs.embedder.com/core-concepts/schematics.md#start-a-project-from-a-schematic). Attach the board manual as well. | | Board with vendor documentation only | In the platform picker, select **Add a custom platform** in VS Code, or **+ Add a platform** in the terminal UI. Enter the platform name and select its PDF documentation. Custom platforms are available when they're enabled for your organization. Otherwise, ask your Embedder administrator. | | Unlisted sensor, module, or other part | [Add a custom peripheral](https://docs.embedder.com/core-concepts/add-peripheral.md#add-a-custom-peripheral) from its PDF datasheet, and name it with the exact part number. | Name the platform or part with its exact part number or board name, and give Embedder the board revision in chat. Then continue from step 2 of [Set up your hardware](#set-up-your-hardware). Documents help Embedder understand the hardware; you still need compatible tools and connections to program or debug it. A custom platform also doesn't load a vendor skill, such as `STM32` or `nxp`, and it loads a board skill only when its name matches that board. See [Use a board-specific skill](#use-a-board-specific-skill). ## Set up your hardware 1. Create a project and select your platform. In VS Code, search under **Pick your platform**; in the terminal UI, search under **Select Platform**. Check the exact part number before you select it. See the [Quickstart](https://docs.embedder.com/quickstart.md). 2. [Add the sensors, modules, and other parts](#add-a-part-to-your-project) fitted to your board with `/peripheral`. Upload your [schematics](https://docs.embedder.com/core-concepts/schematics.md) with `/upload-schematics` so Embedder can check the connections. 3. Run `/init` to record the build, flash, and debug commands in [EMBEDDER.md](https://docs.embedder.com/core-concepts/embedder-md.md). 4. Connect your probe or instruments, open the [Embedder Monitor](https://docs.embedder.com/debug-mode/overview.md), and ask Embedder to check the connected hardware. Finish any setup it reports. In chat, name the exact device, board revision, and SDK version when you ask for hardware work. ## Use a board-specific skill A board skill gives Embedder a reference for one board family, such as its connector pinouts, jumpers, switches, and debug routing. It loads automatically when your project's platform matches the board, and it appears in the `/` menu (under **Skills** in VS Code). Vendor skills, such as `STM32` or `nxp`, load for any platform from that manufacturer. A board skill needs the board itself as the project's platform. For example, the `NUCLEO_C5A3ZG` skill needs the `NUCLEO-C5A3ZG` platform; selecting `STM32C5A3` alone doesn't enable it. Naming the board in chat doesn't enable it either. Many boards that have a skill aren't separate entries in the platform listings. To check: 1. During project setup, search the platform picker for the board name shown in the vendor guide. 2. Select the board entry if it's listed. 3. Type `/` in chat and check that the board skill appears before you ask Embedder to use it. 4. If the board isn't listed, select its MCU instead. In that case, or if the skill doesn't appear, attach the board's user manual and schematic, and ask Embedder to use those documents. A board skill matches the platform's name, so it's also available in a [custom platform](#if-your-hardware-isn%E2%80%99t-listed) project when you name the platform exactly like the board, such as `NUCLEO-F446RE`. That project has only the documents you upload, and a custom platform doesn't load the vendor skill. Selecting the board's MCU from the picker instead keeps the catalog documentation and the vendor skill, without the board skill. Check that the board reference matches your board revision. See [Skills](https://docs.embedder.com/core-concepts/skills.md) for running a skill by name. ## Debug probes Open the guide for the probe or tool you use. Install the matching vendor tools, and give Embedder the MCU, probe, and firmware image for your board. Embedder chooses a debugger from the `Debug Interface` value in EMBEDDER.md and the probes it finds; see [How Embedder picks a debugger](https://docs.embedder.com/debug-mode/gdb.md#how-embedder-picks-a-debugger). | Probe or tool | Use it to | Guide | | - | - | - | | GDB | Set breakpoints, inspect variables, and investigate faults. | [GDB debugging](https://docs.embedder.com/debug-mode/gdb.md) | | SEGGER J-Link | Program and debug targets over a J-Link probe. | [J-Link](https://docs.embedder.com/debug-mode/jlink.md) | | OpenOCD | Debug with a compatible probe, such as ST-LINK or CMSIS-DAP. | [OpenOCD](https://docs.embedder.com/debug-mode/openocd.md) | | TI XDS110 or XDS100 with Code Composer Studio | Debug TI targets that have a `.ccxml` target configuration through your installed CCS. | [TI CCS and XDS](https://docs.embedder.com/debug-mode/ccs.md) | | XMOS xTAG with `xgdb` | Load and debug xcore applications. | [XMOS debugging](https://docs.embedder.com/debug-mode/xmos-debugging.md) | | Infineon DAS with an on-board DAP or miniWiggler | Debug AURIX TriCore targets from hardware scripts on Windows. | [AURIX](https://docs.embedder.com/debug-mode/aurix.md) | | SEGGER J-Trace | Capture instruction trace and coverage. Needs compatible trace hardware, target support, and wiring. | [J-Trace](https://docs.embedder.com/debug-mode/jtrace.md) | | probe-rs | Flash a board attached to a remote bridge. | [probe-rs](https://docs.embedder.com/debug-mode/probe-rs.md) | | `xsim` | Run XMOS applications in simulation. | [xsim](https://docs.embedder.com/debug-mode/xsim.md) | ## Connections to your board * [Serial, RTT, ITM, and xSCOPE](https://docs.embedder.com/debug-mode/serial-transports.md): read firmware output and send commands over a supported connection. * [CAN](https://docs.embedder.com/debug-mode/can.md): monitor and send frames through a supported USB adapter. * [Bluetooth Low Energy](https://docs.embedder.com/debug-mode/bluetooth.md): discover devices and work with their services and characteristics. * [Remote bridges](https://docs.embedder.com/integrations/remote-bridge.md): use hardware connected to another machine. ## Lab instruments Open an instrument guide for setup steps, supported models, and measurement limits. > [card] [Saleae Logic](https://docs.embedder.com/debug-mode/saleae.md) > > Capture and decode digital signals using Logic 2. > [card] [Digilent WaveForms](https://docs.embedder.com/debug-mode/digilent.md) > > Use supported logic, analog-input, waveform-generator, and supply functions. > [card] [DSLogic](https://docs.embedder.com/debug-mode/dslogic.md) > > Capture and decode digital signals without opening DSView. > [card] [Nordic PPK2](https://docs.embedder.com/debug-mode/ppk2.md) > > Measure current with source-meter or ampere-meter wiring. > [card] [Joulescope](https://docs.embedder.com/debug-mode/joulescope.md) > > Measure current, voltage, and energy with model-specific recording options. > [card] [Siglent oscilloscopes](https://docs.embedder.com/debug-mode/siglent.md) > > Capture analog waveforms from SDS800X HD, SDS1000X-E, SDS2000X Plus, and SDS1000X/2000X HD models. > [card] [SCPI oscilloscopes](https://docs.embedder.com/debug-mode/scpi-oscilloscopes.md) > > Capture from Rigol, Tektronix, Keysight, R\&S, LeCroy, and GW Instek scopes. > [card] [Siglent spectrum analyzer](https://docs.embedder.com/debug-mode/spectrum-analyzer.md) > > Run frequency sweeps on an SSA3015X Plus over LAN. > [card] [PicoScope](https://docs.embedder.com/debug-mode/picoscope.md) > > Capture analog signals and, on MSO models, digital signals. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.