Supported hardware

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.
• 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.

For how your selections reach documentation and skills, see Hardware catalog.

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

Community

8-bit microcontrollers

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.

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: 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 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: 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. 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.

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.
2. Add the sensors, modules, and other parts fitted to your board with /peripheral. Upload your schematics with /upload-schematics so Embedder can check the connections.
3. Run /init to record the build, flash, and debug commands in EMBEDDER.md.
4. Connect your probe or instruments, open the Embedder Monitor, 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 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 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.

Connections to your board

• Serial, RTT, ITM, and xSCOPE: read firmware output and send commands over a supported connection.
• CAN: monitor and send frames through a supported USB adapter.
• Bluetooth Low Energy: discover devices and work with their services and characteristics.
• Remote bridges: use hardware connected to another machine.

Lab instruments

Open an instrument guide for setup steps, supported models, and measurement limits.