Skip to main content
The hardware catalog connects the hardware in your project with the references Embedder uses to work on it. Select your platform and peripherals so Embedder can look up the relevant documentation and use matching skills when planning, implementing, or debugging firmware. Browse Supported hardware for platforms and tool integrations, or the peripheral catalog for components by category. The project and peripheral pickers show the current catalog available to you.

​
Describe the hardware in your project

The catalog has two kinds of project entries:
  • Platforms: MCU families, individual devices, modules, and development boards that your firmware runs on.
  • Peripherals: sensors, displays, radios, converters, and other components your firmware communicates with or controls.
Selecting these entries establishes the project’s hardware context. Use the exact part number and manufacturer, and select the specific board when it is available. A board entry can provide more relevant context than its MCU family alone. Choose the platform during project setup and use /peripheral to add or manage peripherals. Keep the selections aligned with the fitted parts as your design changes.

​
Bring the right references into the work

Hardware documentation and skills serve different purposes: Documentation provides the device facts. Embedder can search the documentation associated with your project to answer questions about registers, interfaces, initialization, and operating limits. Selecting a catalog peripheral connects it to the project so its available datasheet information can inform the work. Skills provide instructions for using that hardware. Depending on the selected platform, matching skills can cover board pinouts, jumper settings, SDK workflows, building, flashing, and debugging. Embedder loads applicable skills automatically where configured, and you can also request an available skill by name. See Skills. Coverage varies by entry. A board-specific skill requires a matching platform selection; selecting the MCU family alone may not make it available. Check the slash-command picker for available skills and use the reference for your board revision.

​
Connect device knowledge to your design

The catalog identifies the parts. Your schematics describe how those parts are connected, and EMBEDDER.md records your project’s build commands, setup, and verification steps. Embedder can use these together with the source code. For example, after selecting an STM32 board and adding a BME280, ask:
Adding hardware supplies context. Driver implementation and hardware testing are tasks you request using that context.

​
Work with hardware beyond the catalog

For an unlisted part, add a custom peripheral with its datasheet. For a custom board, supply its manuals and schematics and use custom platform setup when available. These references let Embedder work from the details of your design; you can also write a project skill for procedures your team repeats. When you are ready to run on hardware, follow the relevant probe or instrument guide. Catalog references and skills help prepare the workflow; flashing, debugging, and measurements also require compatible hardware, connections, and installed tools.
Last modified on September 19, 2026