CraftVia
日本語GitHub ↗

AN OPEN HARDWARE PROJECT

One development path,
from prototype to product.

CraftVia is an open embedded development platform combining product-oriented MCU Cores with a Station for development and measurement. Build quickly, verify with real measurements, move the same Core into your device, and graduate to an integrated MCU design when the time is right.

Overview

Bridging development boards
and custom PCBs.

  1. 01

    Reduce the work of rebuilding a product-oriented MCU circuit for every project.

  2. 02

    Bring programming, power control, logging, voltage, and current measurement into one reusable Station.

  3. 03

    Carry circuits, firmware, and measured results from an early prototype into the next design.

System

Three clearly separated roles

01

Core

The common part that runs

A compact MCU module with the minimum circuitry required for stable operation. Develop it on a Station, then install it in the device.

02

Station

The place where you develop

A reusable environment for wiring, programming, power control, logging, voltage measurement, and current measurement.

03

Carrier

The place where the Core works

The application-specific circuit connecting the Core to sensors, communications, drivers, power, and the outside world.

The Core model

Move development features
off the MCU board.

A typical MCU development board combines the MCU with a debugger, USB interface, power supplies, switches, LEDs, and other development features. CraftVia moves reusable development functions to the Station and keeps only the circuitry necessary for reliable MCU operation on the Core.

Typical MCU development board
CraftVia Core
On-board functions
MCU and development features combined
MCU and sufficient operating circuitry
Programming and debug
On each board or externally attached
Centralized on a common Station
Power and measurement
Different for every board
Shared and measurable on the Station
Moving into a device
Carry development features or redesign
Move the developed Core directly

MULTI-MCU PLATFORM

Different MCUs. One development environment.

The same separation principle and Core interface can be applied across multiple MCU families. Choose the Core that fits the application, then use a common Station and a consistent workflow for programming, power, and measurement.

CORE-SG031
CORE-SESP32-C3
CORE-SRP2040
STATION-SCommon StationPROGRAM · POWER · MEASURE

Development path

The goal is not to use a Core forever.

Delay the need for a custom PCB, then use the published design assets to move to a directly integrated MCU when scale or requirements demand it.

1Station + Core↓
2Prototype / perfboard↓
3Core + custom Carrier↓
4Integrated MCU design

Development status

Hardware currently in development

Core-S G031 board rendering
Core

Core-S G031

v1 Rev0 · Frozen design · Unverified
Boards ordered

The first STM32G031-based Core-S implementation, providing the MCU and the circuitry required for its intended operating configuration.

GitHub ↗
Station-S board rendering
Station

Station-S

v1 Rev0 · Frozen design · Unverified
Boards ordered

A reusable Core-S development and measurement platform for programming, power control, UART logging, breakout access, and voltage/current measurement.

GitHub ↗
MakerCard-S board rendering
MakerCard

MakerCard-S

v1 Rev0 · Frozen design · Unverified
Boards ordered

A reference implementation combining the Core-S G031 circuit with breakout, breadboard-style strips, power rails, and a universal prototyping field.

GitHub ↗
Core

Core-S ESP32-C3

Specification in progress

A candidate next Core with wireless connectivity. Its application to the Core-S interface is under consideration.

GitHub ↗
Core

Core-S RP2040

Specification in progress

A candidate next Core based on RP2040. Power, programming, and pin allocation are under consideration.

GitHub ↗

Design principles

Open, measurable, reproducible.

01

Develop, measure, move, graduate

Develop and measure on the Station, move into the device, and graduate to direct MCU integration.

02

Measure from the beginning

Programming, logs, voltage, current, and test points are part of the design—not an afterthought.

03

Document the reasoning

Publish constraints, failures, measurement conditions, and decisions alongside design files.

04

Validate through real projects

Improve the platform using evidence from real prototypes, fixtures, and devices.

Project resources

Explore the project

This English version is the canonical source. The Japanese version is maintained as an official translation.