> ## 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.
# Ecosystems
> Find the silicon vendors, boards, debug probes, serial transports, and lab instruments that Embedder supports for embedded firmware work.
Last Updated: 21 August 2026
Embedder combines a runtime platform catalog, board-specific reference skills, and hardware providers that detect the equipment connected to your machine. Select your platform during project setup, then enter Debug mode and use `hardware_status` to confirm which probes, transports, and instruments are ready.
Use the sidebar to open an ecosystem. Each ecosystem page lists every catalog platform. The [peripheral catalog](/supported-hardware/peripherals) lists every catalog part.
A board-specific skill gives the agent verified pinout, boot, connector, and tooling context. It does not mean every debugger or flasher works with that board. Your installed vendor tools, probe, target metadata, operating system, and licenses still determine which actions are available.
## Platform ecosystems
The selectable platform catalog comes from the Embedder service and can change without a client release. The project setup picker is the source of truth for the catalog available to your team.
The catalog contains **590+** platforms across **13** manufacturers. Open an ecosystem in the sidebar, or start from one of these pages:
150+ ST platforms, CubeMX and ST-LINK workflows, and Nucleo pinout skills.
80+ LPC, Kinetis, i.MX RT, MCX, and S32 platforms.
60+ nRF, nPM, and nRF70 platforms for nRF Connect SDK and Zephyr.
30+ ESP32, ESP32-S/C/H/P, and ESP8684 platforms.
AURIX, TRAVEO T2G, and PSoC Edge catalog kits plus board skills.
20+ RA and RH850 platforms, FSP, and EK-RA8P1.
30+ EFR32 platforms, Simplicity SDK, and SixG301 board skills.
50+ MSP430, C2000, and Sitara AM2x platforms.
30+ computers, Compute Modules, Pico boards, and RP2 MCUs.
30+ UNO, Nano, MKR, Portenta, Nicla, and classic boards.
60+ ATtiny, ATmega, AVR Dx/Ex, and Adafruit AVR platforms.
Teensy LC, 3.2, 3.6, 4.0, and 4.1.
xcore.ai with XTC Tools, `xrun`, `xflash`, `xgdb`, and xSCOPE.
Apollo510 EVB bring-up, flashing, J-Link/SWD, RTT, and recovery.
## Debug probes and backends
| Probe or backend | Supported path | Boundary |
| ---------------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| SEGGER J-Link | GDB server, SWD or JTAG, RTT, and ITM/SWO | Requires the SEGGER J-Link Software and Documentation Pack and a valid device name |
| OpenOCD | Managed or system OpenOCD with GDB | Known bridge mappings cover ST-Link, CMSIS-DAP, and J-Link adapters; the target configuration must match your MCU |
| probe-rs | Flash, reset, and bridge RTT when an MCU name is known | This is a bridge execution path, not a replacement for every vendor flasher |
| SEGGER J-Trace | ETM instruction trace, streaming trace, coverage, RTT, SWO/ITM, and target control | A J-Trace is required for streaming instruction trace; a plain J-Link is not sufficient |
Embedder also recognizes hardware-driving commands from common vendor tools so concurrent sessions do not fight over a probe. Recognition for hardware arbitration does not mean Embedder installs or supports every function of those tools.
## Target transports
| Transport | How you use it |
| -------------------- | ---------------------------------------------------------------------------------------- |
| UART and USB serial | Connect to native serial ports, USB-to-UART adapters, or a board's virtual COM port |
| SEGGER RTT | Read and write RTT channels through J-Link or a configured bridge target |
| Arm ITM/SWO | Capture trace output through a compatible debug probe |
| XMOS xSCOPE | Monitor an XMOS `.xe` application through an XMOS board or xTAG adapter |
| Bluetooth Low Energy | Scan, connect, read, write, and subscribe through the host BLE adapter and Bleak |
| SWD and JTAG | Carry GDB, flash, and target-control traffic through J-Link or OpenOCD-compatible probes |
| ETM | Stream instruction trace through J-Trace hardware |
## Logic, scope, and power instruments
Instrument support is provider-based. `hardware_status` reports missing drivers, SDKs, applications, licenses, and connected devices before a script runs.
| Provider | Supported hardware | Important limits |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Saleae Logic 2 | Recognized USB identities include Original Logic, Logic16, Logic 4, Logic 8, Logic Pro 8, Logic Pro 16, and Logic MSO | Logic 2 must be running with its Automation API enabled. Capture support depends on the device that Logic 2 reports |
| Digilent WaveForms | WaveForms devices that expose the requested instrument; the shipped skill documents Analog Discovery 3 logic, analog-input, waveform-generator, and supply capabilities | Capabilities are detected per device. Analog capture and supply monitoring publish to Power; digital capture publishes to Logic |
| Nordic Power Profiler Kit II | PPK2 in source-meter or ampere-meter mode | You must confirm wiring and mode before measurement. Source-meter output is 800 to 5000 mV |
| Jetperch Joulescope | JS110, JS220, and JS320 | The units are pass-through analyzers and need an external supply. JS320 requires Python 3.12 or newer and `pyjoulescope_driver` 2.3.4 or newer |
| Siglent oscilloscope | SDS802X HD, SDS804X HD, SDS812X HD, SDS814X HD, SDS822X HD, and SDS824X HD | LAN only. Other Siglent generations and other vendors are rejected because their waveform formats differ |
| PicoScope | Driver families `ps2000`, `ps3000`, `ps2000a`, `ps3000a`, `ps4000`, `ps4000a`, `ps5000`, `ps5000a`, `ps6000`, `ps6000a`, and `psospa` | The 2205A MSO is the hardware-verified path. Logic capture requires an MSO model, and capabilities vary by driver family |
Hardware providers publish captures into the Logic, Plot, Power, Trace, or Coverage views when the selected provider supports that output.
See [Digilent WaveForms](/debug-mode/digilent) for its shared `la_*` script surface and per-instrument limits.
## Custom platforms and peripherals
You can add hardware that is absent from the service catalog:
1. Name the custom platform or peripheral.
2. Upload its documentation. The VS Code custom-platform flow accepts PDF references.
3. Upload EDA source through the schematic uploader when you need parsed schematics rather than a document attachment.
4. Add the target metadata needed by your debug path, such as the MCU name, serial port, J-Link device, or OpenOCD target and adapter.
Custom peripherals are available through the project component flow. Custom platforms require the `custom_platforms` team feature, an evaluation plan, or an administrator account.
A custom catalog entry gives the agent hardware context. It does not create a new probe driver, flasher backend, or instrument provider. Use an existing J-Link, OpenOCD, probe-rs, serial, or instrument path, or add provider support in the client.