원클릭으로 Manus에서 모든 스킬 실행

firmware-bringup

스타40

포크16

업데이트2026년 5월 17일 06:06

Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jl-codes

jl-codes/platformio-mcp

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Firmware Bringup

Purpose

Use this skill when the user wants to bring up a new embedded board or create a minimal working firmware project.

Safety Rules

Do not flash firmware without explicit user approval.
Do not erase flash unless the user explicitly asks.
Do not assume the serial port. Discover connected devices first.
Preserve logs and task IDs for debugging.

Workflow

List connected devices.
Search for the likely PlatformIO board ID.
Initialize or inspect the project.
Add a minimal boot marker, such as BOOT_OK, to serial output.
Build the project.
If build succeeds, ask the user before flashing.
Flash the firmware after approval.
Start serial monitoring.
Verify expected boot output.
Summarize result and next steps.

Preferred Commands

Use available repo tools or CLI commands equivalent to:

pio-mcp devices
pio-mcp boards search esp32
pio-mcp init --board esp32dev --framework arduino
pio-mcp build
pio-mcp flash --port auto
pio-mcp monitor --timeout 30

이 저장소의 다른 Skills

같은 저장소

esp32-flash-monitor

jl-codes/platformio-mcp

Run the common ESP32 workflow in PlatformIO: build, flash, monitor, diagnose, patch, and retry. Use for ESP32/ESP8266/ESP32-S3/ESP32-C3 projects using Arduino or ESP-IDF.

2026-05-1740

hardware-in-the-loop-test

jl-codes/platformio-mcp

Validate firmware behavior on real hardware rather than compilation-only checks. Use when running physical acceptance tests, confirming boot markers, validating sensor output, or checking runtime timing/telemetry.

2026-05-1740

platformio-debug

jl-codes/platformio-mcp

Diagnose and fix PlatformIO build, upload, and configuration failures. Use when resolving compiler errors, missing libraries, platformio.ini issues, memory overflows, port conflicts, permission errors, or failed uploads.

2026-05-1740

sbc-deploy

jl-codes/platformio-mcp

Deploy and validate services on single-board computers such as Raspberry Pi, Jetson, Orange Pi, BeagleBone, and Coral. Use when checking SSH connectivity, runtime dependencies, logs, service health, Docker workloads, or systemd deployment.

2026-05-1740

serial-diagnostics

jl-codes/platformio-mcp

Diagnose embedded runtime behavior through serial logs after build/upload. Use when investigating boot loops, crashes, watchdog resets, panic output, missing boot markers, peripheral initialization issues, or silent serial sessions.

2026-05-1740

embedded-systems

jl-codes/platformio-mcp

Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption. Invoke for STM32, ESP32, FreeRTOS, bare-metal, power optimization, real-time systems.

2026-05-0440

name	firmware-bringup
description	Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.

Firmware Bringup

Purpose

Use this skill when the user wants to bring up a new embedded board or create a minimal working firmware project.

Safety Rules

Do not flash firmware without explicit user approval.
Do not erase flash unless the user explicitly asks.
Do not assume the serial port. Discover connected devices first.
Preserve logs and task IDs for debugging.

Workflow

List connected devices.
Search for the likely PlatformIO board ID.
Initialize or inspect the project.
Add a minimal boot marker, such as BOOT_OK, to serial output.
Build the project.
If build succeeds, ask the user before flashing.
Flash the firmware after approval.
Start serial monitoring.
Verify expected boot output.
Summarize result and next steps.

Preferred Commands

Use available repo tools or CLI commands equivalent to:

pio-mcp devices
pio-mcp boards search esp32
pio-mcp init --board esp32dev --framework arduino
pio-mcp build
pio-mcp flash --port auto
pio-mcp monitor --timeout 30